VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306040 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-55957 | suse_vex | SUSE CVE CVE-2026-55957 | known affected: 92 known not affected: 374 recommended: 16 | 2026-10-08T17:12:32+00:00 | Vulnerability · Source |
| CVE-2026-55995 | suse_vex | SUSE CVE CVE-2026-55995 | known affected: 75 recommended: 11 | 2026-10-08T17:12:29+00:00 | Vulnerability · Source |
| CVE-2026-55999 | suse_vex | SUSE CVE CVE-2026-55999 | known affected: 430 recommended: 124 | 2026-10-08T17:12:26+00:00 | Vulnerability · Source |
| CVE-2026-56000 | suse_vex | SUSE CVE CVE-2026-56000 | known affected: 441 recommended: 91 | 2026-10-08T17:12:24+00:00 | Vulnerability · Source |
| CVE-2026-56001 | suse_vex | SUSE CVE CVE-2026-56001 | known affected: 438 recommended: 56 | 2026-10-08T17:12:23+00:00 | Vulnerability · Source |
| CVE-2026-56002 | suse_vex | SUSE CVE CVE-2026-56002 | known affected: 438 recommended: 56 | 2026-10-08T17:12:21+00:00 | Vulnerability · Source |
| CVE-2026-56003 | suse_vex | SUSE CVE CVE-2026-56003 | known affected: 438 recommended: 52 | 2026-10-08T17:12:19+00:00 | Vulnerability · Source |
| CVE-2026-56170 | suse_vex | SUSE CVE CVE-2026-56170 | recommended: 148 | 2026-10-08T17:12:17+00:00 | Vulnerability · Source |
| CVE-2026-56208 | suse_vex | SUSE CVE CVE-2026-56208 | known not affected: 16 recommended: 124 | 2026-10-08T17:12:15+00:00 | Vulnerability · Source |
| CVE-2026-56853 | suse_vex | SUSE CVE CVE-2026-56853 | known affected: 12 known not affected: 139 recommended: 390 | 2026-10-08T17:11:43+00:00 | Vulnerability · Source |
| CVE-2026-56858 | suse_vex | SUSE CVE CVE-2026-56858 | known affected: 24 known not affected: 99 recommended: 382 | 2026-10-08T17:11:40+00:00 | Vulnerability · Source |
| CVE-2026-56859 | suse_vex | SUSE CVE CVE-2026-56859 | known affected: 12 known not affected: 139 recommended: 370 | 2026-10-08T17:11:37+00:00 | Vulnerability · Source |
| CVE-2026-56860 | suse_vex | SUSE CVE CVE-2026-56860 | known affected: 12 known not affected: 153 recommended: 393 | 2026-10-08T17:11:34+00:00 | Vulnerability · Source |
| CVE-2026-56862 | suse_vex | SUSE CVE CVE-2026-56862 | known affected: 12 known not affected: 139 recommended: 393 | 2026-10-08T17:11:31+00:00 | Vulnerability · Source |
| CVE-2026-57108 | suse_vex | SUSE CVE CVE-2026-57108 | recommended: 148 | 2026-10-08T17:11:28+00:00 | Vulnerability · Source |
| CVE-2026-58010 | suse_vex | SUSE CVE CVE-2026-58010 | known affected: 550 recommended: 383 | 2026-10-08T17:11:25+00:00 | Vulnerability · Source |
| CVE-2026-58011 | suse_vex | SUSE CVE CVE-2026-58011 | known affected: 550 recommended: 383 | 2026-10-08T17:11:22+00:00 | Vulnerability · Source |
| CVE-2026-58012 | suse_vex | SUSE CVE CVE-2026-58012 | known affected: 550 recommended: 383 | 2026-10-08T17:11:18+00:00 | Vulnerability · Source |
| CVE-2026-58013 | suse_vex | SUSE CVE CVE-2026-58013 | known affected: 550 recommended: 383 | 2026-10-08T17:11:15+00:00 | Vulnerability · Source |
| CVE-2026-58014 | suse_vex | SUSE CVE CVE-2026-58014 | known affected: 550 recommended: 383 | 2026-10-08T17:11:12+00:00 | Vulnerability · Source |
| CVE-2026-58015 | suse_vex | SUSE CVE CVE-2026-58015 | known not affected: 530 recommended: 27 | 2026-10-08T17:11:10+00:00 | Vulnerability · Source |
| CVE-2026-58016 | suse_vex | SUSE CVE CVE-2026-58016 | known affected: 550 recommended: 383 | 2026-10-08T17:11:07+00:00 | Vulnerability · Source |
| CVE-2026-58264 | suse_vex | SUSE CVE CVE-2026-58264 | recommended: 4 | 2026-10-08T17:11:04+00:00 | Vulnerability · Source |
| CVE-2026-59083 | suse_vex | SUSE CVE CVE-2026-59083 | known affected: 84 known not affected: 1 recommended: 385 | 2026-10-08T17:11:01+00:00 | Vulnerability · Source |
| CVE-2026-59084 | suse_vex | SUSE CVE CVE-2026-59084 | known affected: 85 recommended: 385 | 2026-10-08T17:10:58+00:00 | Vulnerability · Source |
| CVE-2026-59679 | suse_vex | SUSE CVE CVE-2026-59679 | known affected: 436 recommended: 56 | 2026-10-08T17:10:55+00:00 | Vulnerability · Source |
| CVE-2026-59691 | suse_vex | SUSE CVE CVE-2026-59691 | recommended: 11 | 2026-10-08T17:10:52+00:00 | Vulnerability · Source |
| CVE-2026-59692 | suse_vex | SUSE CVE CVE-2026-59692 | known affected: 256 recommended: 711 | 2026-10-08T17:10:50+00:00 | Vulnerability · Source |
| CVE-2026-59873 | suse_vex | SUSE CVE CVE-2026-59873 | recommended: 44 | 2026-10-08T17:10:46+00:00 | Vulnerability · Source |
| CVE-2026-59874 | suse_vex | SUSE CVE CVE-2026-59874 | recommended: 44 | 2026-10-08T17:10:44+00:00 | Vulnerability · Source |
| CVE-2026-59886 | suse_vex | SUSE CVE CVE-2026-59886 | known affected: 452 recommended: 151 | 2026-10-08T17:10:41+00:00 | Vulnerability · Source |
| CVE-2026-59939 | suse_vex | SUSE CVE CVE-2026-59939 | known affected: 75 recommended: 225 | 2026-10-08T17:10:38+00:00 | Vulnerability · Source |
| CVE-2026-59946 | suse_vex | SUSE CVE CVE-2026-59946 | recommended: 18 | 2026-10-08T17:10:36+00:00 | Vulnerability · Source |
| CVE-2026-59947 | suse_vex | SUSE CVE CVE-2026-59947 | recommended: 18 | 2026-10-08T17:10:33+00:00 | Vulnerability · Source |
| CVE-2026-59948 | suse_vex | SUSE CVE CVE-2026-59948 | recommended: 18 | 2026-10-08T17:10:30+00:00 | Vulnerability · Source |
| CVE-2026-59980 | suse_vex | SUSE CVE CVE-2026-59980 | known affected: 74 recommended: 6 | 2026-10-08T17:10:28+00:00 | Vulnerability · Source |
| CVE-2026-60002 | suse_vex | SUSE CVE CVE-2026-60002 | known affected: 580 recommended: 95 | 2026-10-08T17:10:25+00:00 | Vulnerability · Source |
| CVE-2026-60147 | suse_vex | SUSE CVE CVE-2026-60147 | known affected: 538 recommended: 794 | 2026-10-08T17:10:23+00:00 | Vulnerability · Source |
| CVE-2026-60589 | suse_vex | SUSE CVE CVE-2026-60589 | known affected: 538 recommended: 768 | 2026-10-08T17:10:21+00:00 | Vulnerability · Source |
| CVE-2026-61308 | suse_vex | SUSE CVE CVE-2026-61308 | known affected: 538 recommended: 768 | 2026-10-08T17:10:18+00:00 | Vulnerability · Source |
| CVE-2026-62899 | suse_vex | SUSE CVE CVE-2026-62899 | recommended: 148 | 2026-10-08T17:10:14+00:00 | Vulnerability · Source |
| CVE-2026-62900 | suse_vex | SUSE CVE CVE-2026-62900 | recommended: 148 | 2026-10-08T17:10:12+00:00 | Vulnerability · Source |
| CVE-2026-62901 | suse_vex | SUSE CVE CVE-2026-62901 | recommended: 148 | 2026-10-08T17:10:09+00:00 | Vulnerability · Source |
| CVE-2026-62909 | suse_vex | SUSE CVE CVE-2026-62909 | recommended: 148 | 2026-10-08T17:10:06+00:00 | Vulnerability · Source |
| CVE-2026-63209 | suse_vex | SUSE CVE CVE-2026-63209 | known affected: 971 known not affected: 9 recommended: 36 | 2026-10-08T17:10:03+00:00 | Vulnerability · Source |
| CVE-2026-63622 | suse_vex | SUSE CVE CVE-2026-63622 | known affected: 782 known not affected: 1 recommended: 946 | 2026-10-08T17:09:59+00:00 | Vulnerability · Source |
| CVE-2026-63801 | suse_vex | SUSE CVE CVE-2026-63801 | known affected: 462 known not affected: 147 recommended: 489 | 2026-10-08T17:09:56+00:00 | Vulnerability · Source |
| CVE-2026-63887 | suse_vex | SUSE CVE CVE-2026-63887 | known affected: 551 recommended: 565 | 2026-10-08T17:09:46+00:00 | Vulnerability · Source |
| CVE-2026-63913 | suse_vex | SUSE CVE CVE-2026-63913 | known affected: 408 known not affected: 4 recommended: 61 | 2026-10-08T17:09:40+00:00 | Vulnerability · Source |
| CVE-2026-63956 | suse_vex | SUSE CVE CVE-2026-63956 | known affected: 410 | 2026-10-08T17:09:34+00:00 | Vulnerability · Source |