VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49445 | suse_vex | SUSE CVE CVE-2022-49445 | known affected: 533 known not affected: 176 recommended: 260 | 2026-10-16T14:22:47+00:00 | Vulnerability · Source |
| CVE-2022-49446 | suse_vex | SUSE CVE CVE-2022-49446 | known affected: 425 known not affected: 305 recommended: 170 | 2026-10-16T14:22:45+00:00 | Vulnerability · Source |
| CVE-2022-49448 | suse_vex | SUSE CVE CVE-2022-49448 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:22:42+00:00 | Vulnerability · Source |
| CVE-2022-49450 | suse_vex | SUSE CVE CVE-2022-49450 | known affected: 195 known not affected: 297 | 2026-10-16T14:22:40+00:00 | Vulnerability · Source |
| CVE-2022-49453 | suse_vex | SUSE CVE CVE-2022-49453 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:22:37+00:00 | Vulnerability · Source |
| CVE-2022-49455 | suse_vex | SUSE CVE CVE-2022-49455 | known affected: 360 known not affected: 336 recommended: 293 | 2026-10-16T14:22:35+00:00 | Vulnerability · Source |
| CVE-2022-49459 | suse_vex | SUSE CVE CVE-2022-49459 | known affected: 360 known not affected: 338 recommended: 293 | 2026-10-16T14:22:32+00:00 | Vulnerability · Source |
| CVE-2022-49463 | suse_vex | SUSE CVE CVE-2022-49463 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:22:30+00:00 | Vulnerability · Source |
| CVE-2022-49467 | suse_vex | SUSE CVE CVE-2022-49467 | known affected: 490 known not affected: 185 recommended: 330 | 2026-10-16T14:22:25+00:00 | Vulnerability · Source |
| CVE-2022-49469 | suse_vex | SUSE CVE CVE-2022-49469 | known affected: 130 known not affected: 362 | 2026-10-16T14:22:23+00:00 | Vulnerability · Source |
| CVE-2022-49470 | suse_vex | SUSE CVE CVE-2022-49470 | known affected: 494 known not affected: 268 recommended: 100 | 2026-10-16T14:22:20+00:00 | Vulnerability · Source |
| CVE-2022-49471 | suse_vex | SUSE CVE CVE-2022-49471 | known affected: 128 known not affected: 330 recommended: 74 | 2026-10-16T14:22:18+00:00 | Vulnerability · Source |
| CVE-2022-49472 | suse_vex | SUSE CVE CVE-2022-49472 | known affected: 529 known not affected: 144 recommended: 263 | 2026-10-16T14:22:16+00:00 | Vulnerability · Source |
| CVE-2022-49473 | suse_vex | SUSE CVE CVE-2022-49473 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:22:13+00:00 | Vulnerability · Source |
| CVE-2022-49476 | suse_vex | SUSE CVE CVE-2022-49476 | known affected: 425 known not affected: 341 recommended: 100 | 2026-10-16T14:22:11+00:00 | Vulnerability · Source |
| CVE-2022-49478 | suse_vex | SUSE CVE CVE-2022-49478 | known affected: 499 known not affected: 179 recommended: 333 | 2026-10-16T14:22:08+00:00 | Vulnerability · Source |
| CVE-2022-49484 | suse_vex | SUSE CVE CVE-2022-49484 | known affected: 425 known not affected: 341 recommended: 100 | 2026-10-16T14:22:06+00:00 | Vulnerability · Source |
| CVE-2022-49486 | suse_vex | SUSE CVE CVE-2022-49486 | known affected: 500 known not affected: 266 recommended: 223 | 2026-10-16T14:22:03+00:00 | Vulnerability · Source |
| CVE-2022-49488 | suse_vex | SUSE CVE CVE-2022-49488 | known affected: 405 known not affected: 242 recommended: 319 | 2026-10-16T14:22:01+00:00 | Vulnerability · Source |
| CVE-2022-49490 | suse_vex | SUSE CVE CVE-2022-49490 | known affected: 405 known not affected: 240 recommended: 319 | 2026-10-16T14:21:59+00:00 | Vulnerability · Source |
| CVE-2022-49494 | suse_vex | SUSE CVE CVE-2022-49494 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:57+00:00 | Vulnerability · Source |
| CVE-2022-49502 | suse_vex | SUSE CVE CVE-2022-49502 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:54+00:00 | Vulnerability · Source |
| CVE-2022-49506 | suse_vex | SUSE CVE CVE-2022-49506 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:51+00:00 | Vulnerability · Source |
| CVE-2022-49507 | suse_vex | SUSE CVE CVE-2022-49507 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:49+00:00 | Vulnerability · Source |
| CVE-2022-49512 | suse_vex | SUSE CVE CVE-2022-49512 | known affected: 403 known not affected: 329 recommended: 223 | 2026-10-16T14:21:47+00:00 | Vulnerability · Source |
| CVE-2022-49513 | suse_vex | SUSE CVE CVE-2022-49513 | known affected: 626 known not affected: 177 recommended: 100 | 2026-10-16T14:21:44+00:00 | Vulnerability · Source |
| CVE-2022-49514 | suse_vex | SUSE CVE CVE-2022-49514 | known affected: 457 known not affected: 275 recommended: 293 | 2026-10-16T14:21:42+00:00 | Vulnerability · Source |
| CVE-2022-49515 | suse_vex | SUSE CVE CVE-2022-49515 | known affected: 334 known not affected: 394 recommended: 265 | 2026-10-16T14:21:40+00:00 | Vulnerability · Source |
| CVE-2022-49516 | suse_vex | SUSE CVE CVE-2022-49516 | known affected: 468 known not affected: 242 recommended: 126 | 2026-10-16T14:21:37+00:00 | Vulnerability · Source |
| CVE-2022-49518 | suse_vex | SUSE CVE CVE-2022-49518 | known affected: 364 known not affected: 397 recommended: 100 | 2026-10-16T14:21:35+00:00 | Vulnerability · Source |
| CVE-2022-49522 | suse_vex | SUSE CVE CVE-2022-49522 | known affected: 393 known not affected: 299 recommended: 293 | 2026-10-16T14:21:33+00:00 | Vulnerability · Source |
| CVE-2022-49525 | suse_vex | SUSE CVE CVE-2022-49525 | known affected: 499 known not affected: 179 recommended: 333 | 2026-10-16T14:21:28+00:00 | Vulnerability · Source |
| CVE-2022-49526 | suse_vex | SUSE CVE CVE-2022-49526 | known affected: 422 known not affected: 220 recommended: 345 | 2026-10-16T14:21:26+00:00 | Vulnerability · Source |
| CVE-2022-49528 | suse_vex | SUSE CVE CVE-2022-49528 | known affected: 197 known not affected: 265 | 2026-10-16T14:21:23+00:00 | Vulnerability · Source |
| CVE-2022-49529 | suse_vex | SUSE CVE CVE-2022-49529 | known affected: 364 known not affected: 400 recommended: 100 | 2026-10-16T14:21:21+00:00 | Vulnerability · Source |
| CVE-2022-49530 | suse_vex | SUSE CVE CVE-2022-49530 | known affected: 592 known not affected: 117 recommended: 126 | 2026-10-16T14:21:18+00:00 | Vulnerability · Source |
| CVE-2022-49532 | suse_vex | SUSE CVE CVE-2022-49532 | known affected: 481 known not affected: 210 recommended: 333 | 2026-10-16T14:21:16+00:00 | Vulnerability · Source |
| CVE-2022-49533 | suse_vex | SUSE CVE CVE-2022-49533 | known affected: 425 known not affected: 341 recommended: 100 | 2026-10-16T14:21:14+00:00 | Vulnerability · Source |
| CVE-2022-49535 | suse_vex | SUSE CVE CVE-2022-49535 | known affected: 495 known not affected: 179 recommended: 319 | 2026-10-16T14:21:11+00:00 | Vulnerability · Source |
| CVE-2022-49545 | suse_vex | SUSE CVE CVE-2022-49545 | known affected: 496 known not affected: 138 recommended: 424 | 2026-10-16T14:21:05+00:00 | Vulnerability · Source |
| CVE-2022-49546 | suse_vex | SUSE CVE CVE-2022-49546 | known affected: 489 known not affected: 153 recommended: 333 | 2026-10-16T14:21:02+00:00 | Vulnerability · Source |
| CVE-2022-49548 | suse_vex | SUSE CVE CVE-2022-49548 | known affected: 468 known not affected: 294 recommended: 154 | 2026-10-16T14:21:00+00:00 | Vulnerability · Source |
| CVE-2022-49549 | suse_vex | SUSE CVE CVE-2022-49549 | known affected: 334 known not affected: 397 recommended: 223 | 2026-10-16T14:20:57+00:00 | Vulnerability · Source |
| CVE-2022-49552 | suse_vex | SUSE CVE CVE-2022-49552 | known affected: 425 known not affected: 341 recommended: 154 | 2026-10-16T14:20:54+00:00 | Vulnerability · Source |
| CVE-2022-49553 | suse_vex | SUSE CVE CVE-2022-49553 | known affected: 0 known not affected: 462 | 2026-10-16T14:20:52+00:00 | Vulnerability · Source |
| CVE-2022-49554 | suse_vex | SUSE CVE CVE-2022-49554 | known affected: 130 known not affected: 332 | 2026-10-16T14:20:50+00:00 | Vulnerability · Source |
| CVE-2022-49557 | suse_vex | SUSE CVE CVE-2022-49557 | known affected: 0 known not affected: 462 recommended: 42 | 2026-10-16T14:20:47+00:00 | Vulnerability · Source |
| CVE-2022-49558 | suse_vex | SUSE CVE CVE-2022-49558 | known affected: 61 known not affected: 401 | 2026-10-16T14:20:45+00:00 | Vulnerability · Source |
| CVE-2022-49559 | suse_vex | SUSE CVE CVE-2022-49559 | known affected: 334 known not affected: 394 recommended: 265 | 2026-10-16T14:20:42+00:00 | Vulnerability · Source |
| CVE-2022-49561 | suse_vex | SUSE CVE CVE-2022-49561 | known affected: 621 known not affected: 209 recommended: 68 | 2026-10-16T14:20:39+00:00 | Vulnerability · Source |