VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283445 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49101 | suse_vex | SUSE CVE CVE-2022-49101 | known not affected: 352 | 2026-07-25T17:16:35+00:00 | Vulnerability · Source |
| CVE-2022-49103 | suse_vex | SUSE CVE CVE-2022-49103 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:33+00:00 | Vulnerability · Source |
| CVE-2022-49105 | suse_vex | SUSE CVE CVE-2022-49105 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:31+00:00 | Vulnerability · Source |
| CVE-2022-49108 | suse_vex | SUSE CVE CVE-2022-49108 | known not affected: 352 | 2026-07-25T17:16:29+00:00 | Vulnerability · Source |
| CVE-2022-49109 | suse_vex | SUSE CVE CVE-2022-49109 | known affected: 470 known not affected: 230 recommended: 271 | 2026-07-25T17:16:26+00:00 | Vulnerability · Source |
| CVE-2022-49110 | suse_vex | SUSE CVE CVE-2022-49110 | known affected: 373 known not affected: 189 recommended: 296 | 2026-07-25T17:16:25+00:00 | Vulnerability · Source |
| CVE-2022-49113 | suse_vex | SUSE CVE CVE-2022-49113 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:23+00:00 | Vulnerability · Source |
| CVE-2022-49118 | suse_vex | SUSE CVE CVE-2022-49118 | known affected: 414 known not affected: 230 recommended: 249 | 2026-07-25T17:16:22+00:00 | Vulnerability · Source |
| CVE-2022-49125 | suse_vex | SUSE CVE CVE-2022-49125 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:16:20+00:00 | Vulnerability · Source |
| CVE-2022-49129 | suse_vex | SUSE CVE CVE-2022-49129 | known affected: 385 known not affected: 247 recommended: 265 | 2026-07-25T17:16:19+00:00 | Vulnerability · Source |
| CVE-2022-49135 | suse_vex | SUSE CVE CVE-2022-49135 | known affected: 346 known not affected: 260 recommended: 249 | 2026-07-25T17:16:17+00:00 | Vulnerability · Source |
| CVE-2022-49138 | suse_vex | SUSE CVE CVE-2022-49138 | known affected: 490 known not affected: 126 recommended: 251 | 2026-07-25T17:16:16+00:00 | Vulnerability · Source |
| CVE-2022-49144 | suse_vex | SUSE CVE CVE-2022-49144 | known affected: 419 known not affected: 247 recommended: 100 | 2026-07-25T17:16:14+00:00 | Vulnerability · Source |
| CVE-2022-49150 | suse_vex | SUSE CVE CVE-2022-49150 | known not affected: 352 | 2026-07-25T17:16:13+00:00 | Vulnerability · Source |
| CVE-2022-49152 | suse_vex | SUSE CVE CVE-2022-49152 | known not affected: 352 recommended: 22 | 2026-07-25T17:16:11+00:00 | Vulnerability · Source |
| CVE-2022-49154 | suse_vex | SUSE CVE CVE-2022-49154 | known affected: 444 known not affected: 213 recommended: 260 | 2026-07-25T17:16:10+00:00 | Vulnerability · Source |
| CVE-2022-49156 | suse_vex | SUSE CVE CVE-2022-49156 | known affected: 415 known not affected: 163 recommended: 375 | 2026-07-25T17:16:08+00:00 | Vulnerability · Source |
| CVE-2022-49158 | suse_vex | SUSE CVE CVE-2022-49158 | known affected: 395 known not affected: 181 recommended: 375 | 2026-07-25T17:16:07+00:00 | Vulnerability · Source |
| CVE-2022-49160 | suse_vex | SUSE CVE CVE-2022-49160 | known affected: 379 known not affected: 199 recommended: 361 | 2026-07-25T17:16:05+00:00 | Vulnerability · Source |
| CVE-2022-49162 | suse_vex | SUSE CVE CVE-2022-49162 | known affected: 401 known not affected: 199 recommended: 293 | 2026-07-25T17:16:04+00:00 | Vulnerability · Source |
| CVE-2022-49165 | suse_vex | SUSE CVE CVE-2022-49165 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:02+00:00 | Vulnerability · Source |
| CVE-2022-49166 | suse_vex | SUSE CVE CVE-2022-49166 | known not affected: 348 | 2026-07-25T17:16:01+00:00 | Vulnerability · Source |
| CVE-2022-49170 | suse_vex | SUSE CVE CVE-2022-49170 | known not affected: 352 | 2026-07-25T17:16:00+00:00 | Vulnerability · Source |
| CVE-2022-49171 | suse_vex | SUSE CVE CVE-2022-49171 | known affected: 475 known not affected: 241 recommended: 40 | 2026-07-25T17:15:58+00:00 | Vulnerability · Source |
| CVE-2022-49173 | suse_vex | SUSE CVE CVE-2022-49173 | known not affected: 348 | 2026-07-25T17:15:57+00:00 | Vulnerability · Source |
| CVE-2022-49174 | suse_vex | SUSE CVE CVE-2022-49174 | known affected: 334 known not affected: 294 recommended: 223 | 2026-07-25T17:15:55+00:00 | Vulnerability · Source |
| CVE-2022-49176 | suse_vex | SUSE CVE CVE-2022-49176 | known affected: 410 known not affected: 230 recommended: 249 | 2026-07-25T17:15:54+00:00 | Vulnerability · Source |
| CVE-2022-49181 | suse_vex | SUSE CVE CVE-2022-49181 | known not affected: 352 | 2026-07-25T17:15:52+00:00 | Vulnerability · Source |
| CVE-2022-49182 | suse_vex | SUSE CVE CVE-2022-49182 | known affected: 414 known not affected: 192 recommended: 249 | 2026-07-25T17:15:51+00:00 | Vulnerability · Source |
| CVE-2022-49183 | suse_vex | SUSE CVE CVE-2022-49183 | known affected: 401 known not affected: 265 recommended: 100 | 2026-07-25T17:15:50+00:00 | Vulnerability · Source |
| CVE-2022-49184 | suse_vex | SUSE CVE CVE-2022-49184 | known not affected: 352 | 2026-07-25T17:15:48+00:00 | Vulnerability · Source |
| CVE-2022-49186 | suse_vex | SUSE CVE CVE-2022-49186 | known not affected: 352 | 2026-07-25T17:15:47+00:00 | Vulnerability · Source |
| CVE-2022-49187 | suse_vex | SUSE CVE CVE-2022-49187 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:46+00:00 | Vulnerability · Source |
| CVE-2022-49190 | suse_vex | SUSE CVE CVE-2022-49190 | known affected: 573 known not affected: 183 recommended: 37 | 2026-07-25T17:15:44+00:00 | Vulnerability · Source |
| CVE-2022-49191 | suse_vex | SUSE CVE CVE-2022-49191 | known affected: 567 known not affected: 153 recommended: 40 | 2026-07-25T17:15:43+00:00 | Vulnerability · Source |
| CVE-2022-49193 | suse_vex | SUSE CVE CVE-2022-49193 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:41+00:00 | Vulnerability · Source |
| CVE-2022-49194 | suse_vex | SUSE CVE CVE-2022-49194 | known affected: 406 known not affected: 192 recommended: 223 | 2026-07-25T17:15:40+00:00 | Vulnerability · Source |
| CVE-2022-49195 | suse_vex | SUSE CVE CVE-2022-49195 | known not affected: 403 | 2026-07-25T17:15:39+00:00 | Vulnerability · Source |
| CVE-2022-49196 | suse_vex | SUSE CVE CVE-2022-49196 | known affected: 350 known not affected: 294 recommended: 331 | 2026-07-25T17:15:37+00:00 | Vulnerability · Source |
| CVE-2022-49205 | suse_vex | SUSE CVE CVE-2022-49205 | known affected: 499 known not affected: 179 recommended: 153 | 2026-07-25T17:15:35+00:00 | Vulnerability · Source |
| CVE-2022-49206 | suse_vex | SUSE CVE CVE-2022-49206 | known affected: 348 known not affected: 256 recommended: 293 | 2026-07-25T17:15:34+00:00 | Vulnerability · Source |
| CVE-2022-49213 | suse_vex | SUSE CVE CVE-2022-49213 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:15:33+00:00 | Vulnerability · Source |
| CVE-2022-49216 | suse_vex | SUSE CVE CVE-2022-49216 | known affected: 421 known not affected: 225 recommended: 316 | 2026-07-25T17:15:31+00:00 | Vulnerability · Source |
| CVE-2022-49218 | suse_vex | SUSE CVE CVE-2022-49218 | known affected: 371 known not affected: 261 recommended: 223 | 2026-07-25T17:15:30+00:00 | Vulnerability · Source |
| CVE-2022-49221 | suse_vex | SUSE CVE CVE-2022-49221 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:28+00:00 | Vulnerability · Source |
| CVE-2022-49222 | suse_vex | SUSE CVE CVE-2022-49222 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:27+00:00 | Vulnerability · Source |
| CVE-2022-49224 | suse_vex | SUSE CVE CVE-2022-49224 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:15:25+00:00 | Vulnerability · Source |
| CVE-2022-49229 | suse_vex | SUSE CVE CVE-2022-49229 | known affected: 112 known not affected: 240 recommended: 22 | 2026-07-25T17:15:24+00:00 | Vulnerability · Source |
| CVE-2022-49230 | suse_vex | SUSE CVE CVE-2022-49230 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:15:22+00:00 | Vulnerability · Source |
| CVE-2022-49232 | suse_vex | SUSE CVE CVE-2022-49232 | known affected: 377 known not affected: 239 recommended: 319 | 2026-07-25T17:15:21+00:00 | Vulnerability · Source |