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-2026-58469 | suse_vex | SUSE CVE CVE-2026-58469 | known affected: 409 known not affected: 6 recommended: 29 | 2026-10-16T00:16:19+00:00 | Vulnerability · Source |
| CVE-2026-58470 | suse_vex | SUSE CVE CVE-2026-58470 | known affected: 413 recommended: 31 | 2026-10-16T00:16:17+00:00 | Vulnerability · Source |
| CVE-2026-58471 | suse_vex | SUSE CVE CVE-2026-58471 | known affected: 409 known not affected: 6 recommended: 31 | 2026-10-16T00:16:15+00:00 | Vulnerability · Source |
| CVE-2026-58472 | suse_vex | SUSE CVE CVE-2026-58472 | known affected: 413 recommended: 34 | 2026-10-16T00:16:13+00:00 | Vulnerability · Source |
| CVE-2026-59676 | suse_vex | SUSE CVE CVE-2026-59676 | known affected: 213 | 2026-10-16T00:16:11+00:00 | Vulnerability · Source |
| CVE-2026-59677 | suse_vex | SUSE CVE CVE-2026-59677 | known affected: 213 | 2026-10-16T00:16:09+00:00 | Vulnerability · Source |
| CVE-2026-59869 | suse_vex | SUSE CVE CVE-2026-59869 | known affected: 221 known not affected: 318 | 2026-10-16T00:16:02+00:00 | Vulnerability · Source |
| CVE-2026-59873 | suse_vex | SUSE CVE CVE-2026-59873 | recommended: 44 | 2026-10-16T00:16:01+00:00 | Vulnerability · Source |
| CVE-2026-59874 | suse_vex | SUSE CVE CVE-2026-59874 | recommended: 44 | 2026-10-16T00:15:59+00:00 | Vulnerability · Source |
| CVE-2026-59879 | suse_vex | SUSE CVE CVE-2026-59879 | known affected: 60 known not affected: 493 | 2026-10-16T00:15:57+00:00 | Vulnerability · Source |
| CVE-2026-60062 | suse_vex | SUSE CVE CVE-2026-60062 | known affected: 61 | 2026-10-16T00:15:50+00:00 | Vulnerability · Source |
| CVE-2026-60065 | suse_vex | SUSE CVE CVE-2026-60065 | known affected: 61 | 2026-10-16T00:15:48+00:00 | Vulnerability · Source |
| CVE-2026-63072 | suse_vex | SUSE CVE CVE-2026-63072 | known affected: 478 known not affected: 270 recommended: 266 | 2026-10-16T00:15:38+00:00 | Vulnerability · Source |
| CVE-2026-63073 | suse_vex | SUSE CVE CVE-2026-63073 | known affected: 394 known not affected: 560 recommended: 67 | 2026-10-16T00:15:36+00:00 | Vulnerability · Source |
| CVE-2026-63075 | suse_vex | SUSE CVE CVE-2026-63075 | known affected: 394 known not affected: 560 recommended: 67 | 2026-10-16T00:15:34+00:00 | Vulnerability · Source |
| CVE-2026-63802 | suse_vex | SUSE CVE CVE-2026-63802 | known affected: 455 known not affected: 251 recommended: 525 | 2026-10-16T00:15:23+00:00 | Vulnerability · Source |
| CVE-2026-63888 | suse_vex | SUSE CVE CVE-2026-63888 | known affected: 554 recommended: 743 | 2026-10-16T00:15:12+00:00 | Vulnerability · Source |
| CVE-2026-63912 | suse_vex | SUSE CVE CVE-2026-63912 | known affected: 585 known not affected: 121 recommended: 421 | 2026-10-16T00:14:58+00:00 | Vulnerability · Source |
| CVE-2026-63917 | suse_vex | SUSE CVE CVE-2026-63917 | known affected: 623 known not affected: 6 recommended: 715 | 2026-10-16T00:14:54+00:00 | Vulnerability · Source |
| CVE-2026-63921 | suse_vex | SUSE CVE CVE-2026-63921 | known affected: 608 known not affected: 21 recommended: 715 | 2026-10-16T00:14:49+00:00 | Vulnerability · Source |
| CVE-2026-63944 | suse_vex | SUSE CVE CVE-2026-63944 | known affected: 422 known not affected: 309 recommended: 496 | 2026-10-16T00:14:41+00:00 | Vulnerability · Source |
| CVE-2026-63994 | suse_vex | SUSE CVE CVE-2026-63994 | known affected: 505 known not affected: 121 recommended: 630 | 2026-10-16T00:14:20+00:00 | Vulnerability · Source |
| CVE-2026-64000 | suse_vex | SUSE CVE CVE-2026-64000 | known affected: 486 known not affected: 251 recommended: 432 | 2026-10-16T00:14:18+00:00 | Vulnerability · Source |
| CVE-2026-64011 | suse_vex | SUSE CVE CVE-2026-64011 | known affected: 539 known not affected: 63 recommended: 616 | 2026-10-16T00:14:12+00:00 | Vulnerability · Source |
| CVE-2026-64054 | suse_vex | SUSE CVE CVE-2026-64054 | known affected: 19 known not affected: 345 recommended: 145 | 2026-10-16T00:14:02+00:00 | Vulnerability · Source |
| CVE-2026-64079 | suse_vex | SUSE CVE CVE-2026-64079 | known affected: 217 known not affected: 79 | 2026-10-16T00:14:00+00:00 | Vulnerability · Source |
| CVE-2026-64114 | suse_vex | SUSE CVE CVE-2026-64114 | known affected: 571 recommended: 655 | 2026-10-16T00:13:51+00:00 | Vulnerability · Source |
| CVE-2026-64121 | suse_vex | SUSE CVE CVE-2026-64121 | known affected: 474 known not affected: 251 recommended: 432 | 2026-10-16T00:13:48+00:00 | Vulnerability · Source |
| CVE-2026-64189 | suse_vex | SUSE CVE CVE-2026-64189 | known affected: 513 known not affected: 97 recommended: 717 | 2026-10-16T00:13:44+00:00 | Vulnerability · Source |
| CVE-2026-64385 | suse_vex | SUSE CVE CVE-2026-64385 | known affected: 425 known not affected: 280 recommended: 287 | 2026-10-16T00:13:06+00:00 | Vulnerability · Source |
| CVE-2026-64508 | suse_vex | SUSE CVE CVE-2026-64508 | known affected: 183 known not affected: 193 recommended: 4 | 2026-10-16T00:12:45+00:00 | Vulnerability · Source |
| CVE-2026-67213 | suse_vex | SUSE CVE CVE-2026-67213 | known not affected: 599 | 2026-10-16T00:11:53+00:00 | Vulnerability · Source |
| CVE-2026-67214 | suse_vex | SUSE CVE CVE-2026-67214 | known not affected: 599 | 2026-10-16T00:11:51+00:00 | Vulnerability · Source |
| CVE-2026-68006 | suse_vex | SUSE CVE CVE-2026-68006 | known affected: 93 known not affected: 13 | 2026-10-16T00:11:49+00:00 | Vulnerability · Source |
| CVE-2026-68121 | suse_vex | SUSE CVE CVE-2026-68121 | known affected: 569 recommended: 768 | 2026-10-16T00:11:45+00:00 | Vulnerability · Source |
| CVE-2026-68155 | suse_vex | SUSE CVE CVE-2026-68155 | known affected: 440 known not affected: 155 recommended: 478 | 2026-10-16T00:11:35+00:00 | Vulnerability · Source |
| CVE-2026-68159 | suse_vex | SUSE CVE CVE-2026-68159 | known affected: 591 known not affected: 4 recommended: 478 | 2026-10-16T00:11:31+00:00 | Vulnerability · Source |
| CVE-2026-68202 | suse_vex | SUSE CVE CVE-2026-68202 | known affected: 454 known not affected: 125 recommended: 647 | 2026-10-16T00:11:26+00:00 | Vulnerability · Source |
| CVE-2026-68494 | suse_vex | SUSE CVE CVE-2026-68494 | known not affected: 17 recommended: 77 | 2026-10-16T00:10:52+00:00 | Vulnerability · Source |
| CVE-2026-68497 | suse_vex | SUSE CVE CVE-2026-68497 | known affected: 64 recommended: 91 | 2026-10-16T00:10:50+00:00 | Vulnerability · Source |
| CVE-2026-69153 | suse_vex | SUSE CVE CVE-2026-69153 | known affected: 262 known not affected: 326 recommended: 1 | 2026-10-16T00:10:45+00:00 | Vulnerability · Source |
| CVE-2026-71217 | suse_vex | SUSE CVE CVE-2026-71217 | known affected: 22 recommended: 6 | 2026-10-16T00:10:36+00:00 | Vulnerability · Source |
| CVE-2026-71218 | suse_vex | SUSE CVE CVE-2026-71218 | known not affected: 22 recommended: 3 | 2026-10-16T00:10:34+00:00 | Vulnerability · Source |
| CVE-2026-71556 | suse_vex | SUSE CVE CVE-2026-71556 | known affected: 529 known not affected: 103 recommended: 160 | 2026-10-16T00:10:30+00:00 | Vulnerability · Source |
| CVE-2026-71557 | suse_vex | SUSE CVE CVE-2026-71557 | known affected: 135 known not affected: 103 recommended: 159 | 2026-10-16T00:10:28+00:00 | Vulnerability · Source |
| CVE-2026-71847 | suse_vex | SUSE CVE CVE-2026-71847 | known affected: 58 known not affected: 333 | 2026-10-16T00:10:26+00:00 | Vulnerability · Source |
| CVE-2026-71884 | suse_vex | SUSE CVE CVE-2026-71884 | known affected: 134 | 2026-10-16T00:10:24+00:00 | Vulnerability · Source |
| CVE-2026-72083 | suse_vex | SUSE CVE CVE-2026-72083 | known affected: 583 recommended: 379 | 2026-10-16T00:09:59+00:00 | Vulnerability · Source |
| CVE-2026-72217 | suse_vex | SUSE CVE CVE-2026-72217 | known affected: 67 known not affected: 333 recommended: 165 | 2026-10-16T00:09:31+00:00 | Vulnerability · Source |
| CVE-2026-72289 | suse_vex | SUSE CVE CVE-2026-72289 | known affected: 579 known not affected: 4 recommended: 424 | 2026-10-16T00:09:10+00:00 | Vulnerability · Source |