VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-47695 | suse_vex | SUSE CVE CVE-2022-47695 | known affected: 394 known not affected: 69 recommended: 327 | 2026-10-17T01:21:34+00:00 | Vulnerability · Source |
| CVE-2022-47943 | suse_vex | SUSE CVE CVE-2022-47943 | known affected: 0 known not affected: 392 | 2026-10-17T01:21:32+00:00 | Vulnerability · Source |
| CVE-2022-48065 | suse_vex | SUSE CVE CVE-2022-48065 | known affected: 442 recommended: 327 | 2026-10-17T01:21:31+00:00 | Vulnerability · Source |
| CVE-2022-48468 | suse_vex | SUSE CVE CVE-2022-48468 | known affected: 15 recommended: 103 | 2026-10-17T01:21:30+00:00 | Vulnerability · Source |
| CVE-2022-48503 | suse_vex | SUSE CVE CVE-2022-48503 | known affected: 138 recommended: 761 | 2026-10-17T01:21:28+00:00 | Vulnerability · Source |
| CVE-2022-48566 | suse_vex | SUSE CVE CVE-2022-48566 | known affected: 570 known not affected: 304 recommended: 478 | 2026-10-17T01:21:27+00:00 | Vulnerability · Source |
| CVE-2022-48649 | suse_vex | SUSE CVE CVE-2022-48649 | known not affected: 343 | 2026-10-17T01:21:23+00:00 | Vulnerability · Source |
| CVE-2022-48686 | suse_vex | SUSE CVE CVE-2022-48686 | known affected: 297 known not affected: 186 recommended: 670 | 2026-10-17T01:21:19+00:00 | Vulnerability · Source |
| CVE-2022-48709 | suse_vex | SUSE CVE CVE-2022-48709 | known affected: 275 known not affected: 266 recommended: 452 | 2026-10-17T01:21:17+00:00 | Vulnerability · Source |
| CVE-2022-48737 | suse_vex | SUSE CVE CVE-2022-48737 | known affected: 324 known not affected: 59 recommended: 482 | 2026-10-17T01:21:11+00:00 | Vulnerability · Source |
| CVE-2022-48739 | suse_vex | SUSE CVE CVE-2022-48739 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-17T01:21:10+00:00 | Vulnerability · Source |
| CVE-2022-48765 | suse_vex | SUSE CVE CVE-2022-48765 | known affected: 330 known not affected: 254 recommended: 433 | 2026-10-17T01:21:08+00:00 | Vulnerability · Source |
| CVE-2022-48801 | suse_vex | SUSE CVE CVE-2022-48801 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-17T01:21:06+00:00 | Vulnerability · Source |
| CVE-2022-48819 | suse_vex | SUSE CVE CVE-2022-48819 | known not affected: 373 | 2026-10-17T01:21:05+00:00 | Vulnerability · Source |
| CVE-2022-48889 | suse_vex | SUSE CVE CVE-2022-48889 | known affected: 340 known not affected: 309 recommended: 288 | 2026-10-17T01:21:00+00:00 | Vulnerability · Source |
| CVE-2022-48901 | suse_vex | SUSE CVE CVE-2022-48901 | known affected: 410 known not affected: 289 recommended: 417 | 2026-10-17T01:20:58+00:00 | Vulnerability · Source |
| CVE-2022-48917 | suse_vex | SUSE CVE CVE-2022-48917 | known affected: 310 known not affected: 246 recommended: 496 | 2026-10-17T01:20:55+00:00 | Vulnerability · Source |
| CVE-2022-48923 | suse_vex | SUSE CVE CVE-2022-48923 | known affected: 314 known not affected: 271 recommended: 445 | 2026-10-17T01:20:53+00:00 | Vulnerability · Source |
| CVE-2022-48981 | suse_vex | SUSE CVE CVE-2022-48981 | known affected: 367 known not affected: 371 recommended: 394 | 2026-10-17T01:20:50+00:00 | Vulnerability · Source |
| CVE-2022-49021 | suse_vex | SUSE CVE CVE-2022-49021 | known affected: 520 known not affected: 110 recommended: 518 | 2026-10-17T01:20:48+00:00 | Vulnerability · Source |
| CVE-2022-49061 | suse_vex | SUSE CVE CVE-2022-49061 | known affected: 377 known not affected: 351 recommended: 223 | 2026-10-17T01:20:46+00:00 | Vulnerability · Source |
| CVE-2022-49076 | suse_vex | SUSE CVE CVE-2022-49076 | known affected: 465 known not affected: 179 recommended: 333 | 2026-10-17T01:20:45+00:00 | Vulnerability · Source |
| CVE-2022-49077 | suse_vex | SUSE CVE CVE-2022-49077 | known affected: 0 known not affected: 104 | 2026-10-17T01:20:43+00:00 | Vulnerability · Source |
| CVE-2022-49104 | suse_vex | SUSE CVE CVE-2022-49104 | known affected: 334 known not affected: 442 recommended: 223 | 2026-10-17T01:20:41+00:00 | Vulnerability · Source |
| CVE-2022-49127 | suse_vex | SUSE CVE CVE-2022-49127 | known affected: 67 known not affected: 395 | 2026-10-17T01:20:40+00:00 | Vulnerability · Source |
| CVE-2022-49148 | suse_vex | SUSE CVE CVE-2022-49148 | known affected: 334 known not affected: 397 recommended: 223 | 2026-10-17T01:20:38+00:00 | Vulnerability · Source |
| CVE-2022-49188 | suse_vex | SUSE CVE CVE-2022-49188 | known affected: 505 known not affected: 206 recommended: 271 | 2026-10-17T01:20:36+00:00 | Vulnerability · Source |
| CVE-2022-49197 | suse_vex | SUSE CVE CVE-2022-49197 | known affected: 724 known not affected: 109 recommended: 40 | 2026-10-17T01:20:34+00:00 | Vulnerability · Source |
| CVE-2022-49201 | suse_vex | SUSE CVE CVE-2022-49201 | known affected: 461 known not affected: 124 recommended: 319 | 2026-10-17T01:20:33+00:00 | Vulnerability · Source |
| CVE-2022-49212 | suse_vex | SUSE CVE CVE-2022-49212 | known affected: 465 known not affected: 215 recommended: 316 | 2026-10-17T01:20:30+00:00 | Vulnerability · Source |
| CVE-2022-49256 | suse_vex | SUSE CVE CVE-2022-49256 | known affected: 0 known not affected: 394 recommended: 221 | 2026-10-17T01:20:27+00:00 | Vulnerability · Source |
| CVE-2022-49267 | suse_vex | SUSE CVE CVE-2022-49267 | known affected: 339 known not affected: 110 | 2026-10-17T01:20:26+00:00 | Vulnerability · Source |
| CVE-2022-49279 | suse_vex | SUSE CVE CVE-2022-49279 | known affected: 360 known not affected: 334 recommended: 293 | 2026-10-17T01:20:24+00:00 | Vulnerability · Source |
| CVE-2022-49286 | suse_vex | SUSE CVE CVE-2022-49286 | known affected: 496 known not affected: 182 recommended: 249 | 2026-10-17T01:20:22+00:00 | Vulnerability · Source |
| CVE-2022-49308 | suse_vex | SUSE CVE CVE-2022-49308 | known affected: 501 known not affected: 172 recommended: 263 | 2026-10-17T01:20:20+00:00 | Vulnerability · Source |
| CVE-2022-49326 | suse_vex | SUSE CVE CVE-2022-49326 | known affected: 489 known not affected: 151 recommended: 330 | 2026-10-17T01:20:19+00:00 | Vulnerability · Source |
| CVE-2022-49354 | suse_vex | SUSE CVE CVE-2022-49354 | known affected: 334 known not affected: 393 recommended: 223 | 2026-10-17T01:20:17+00:00 | Vulnerability · Source |
| CVE-2022-49382 | suse_vex | SUSE CVE CVE-2022-49382 | known affected: 465 known not affected: 266 recommended: 316 | 2026-10-17T01:20:14+00:00 | Vulnerability · Source |
| CVE-2022-49383 | suse_vex | SUSE CVE CVE-2022-49383 | known affected: 0 known not affected: 462 | 2026-10-17T01:20:13+00:00 | Vulnerability · Source |
| CVE-2022-49385 | suse_vex | SUSE CVE CVE-2022-49385 | known affected: 493 known not affected: 183 recommended: 333 | 2026-10-17T01:20:11+00:00 | Vulnerability · Source |
| CVE-2022-49429 | suse_vex | SUSE CVE CVE-2022-49429 | known affected: 524 known not affected: 203 recommended: 337 | 2026-10-17T01:20:09+00:00 | Vulnerability · Source |
| CVE-2022-49436 | suse_vex | SUSE CVE CVE-2022-49436 | known affected: 364 known not affected: 402 recommended: 100 | 2026-10-17T01:20:08+00:00 | Vulnerability · Source |
| CVE-2022-49439 | suse_vex | SUSE CVE CVE-2022-49439 | known affected: 255 known not affected: 241 | 2026-10-17T01:20:07+00:00 | Vulnerability · Source |
| CVE-2022-49444 | suse_vex | SUSE CVE CVE-2022-49444 | known affected: 400 known not affected: 279 recommended: 249 | 2026-10-17T01:20:05+00:00 | Vulnerability · Source |
| CVE-2022-49454 | suse_vex | SUSE CVE CVE-2022-49454 | known affected: 0 known not affected: 462 | 2026-10-17T01:20:04+00:00 | Vulnerability · Source |
| CVE-2022-49461 | suse_vex | SUSE CVE CVE-2022-49461 | known affected: 0 known not affected: 462 | 2026-10-17T01:20:02+00:00 | Vulnerability · Source |
| CVE-2022-49477 | suse_vex | SUSE CVE CVE-2022-49477 | known affected: 377 known not affected: 351 recommended: 223 | 2026-10-17T01:20:01+00:00 | Vulnerability · Source |
| CVE-2022-49480 | suse_vex | SUSE CVE CVE-2022-49480 | known affected: 334 known not affected: 398 recommended: 223 | 2026-10-17T01:19:59+00:00 | Vulnerability · Source |
| CVE-2022-49491 | suse_vex | SUSE CVE CVE-2022-49491 | known affected: 493 known not affected: 213 recommended: 316 | 2026-10-17T01:19:57+00:00 | Vulnerability · Source |
| CVE-2022-49505 | suse_vex | SUSE CVE CVE-2022-49505 | known affected: 493 known not affected: 151 recommended: 333 | 2026-10-17T01:19:55+00:00 | Vulnerability · Source |