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-1965 | suse_vex | SUSE CVE CVE-2026-1965 | known affected: 448 recommended: 206 | 2026-10-16T00:50:12+00:00 | Vulnerability · Source |
| CVE-2026-2003 | suse_vex | SUSE CVE CVE-2026-2003 | known affected: 457 recommended: 1233 | 2026-10-16T00:50:10+00:00 | Vulnerability · Source |
| CVE-2026-2004 | suse_vex | SUSE CVE CVE-2026-2004 | known affected: 108 recommended: 1233 | 2026-10-16T00:50:07+00:00 | Vulnerability · Source |
| CVE-2026-2005 | suse_vex | SUSE CVE CVE-2026-2005 | known affected: 108 recommended: 1233 | 2026-10-16T00:50:05+00:00 | Vulnerability · Source |
| CVE-2026-2006 | suse_vex | SUSE CVE CVE-2026-2006 | known affected: 108 recommended: 1233 | 2026-10-16T00:50:03+00:00 | Vulnerability · Source |
| CVE-2026-2007 | suse_vex | SUSE CVE CVE-2026-2007 | known affected: 0 known not affected: 1363 recommended: 215 | 2026-10-16T00:50:01+00:00 | Vulnerability · Source |
| CVE-2026-2243 | suse_vex | SUSE CVE CVE-2026-2243 | known affected: 1286 recommended: 632 | 2026-10-16T00:49:58+00:00 | Vulnerability · Source |
| CVE-2026-2297 | suse_vex | SUSE CVE CVE-2026-2297 | known affected: 394 known not affected: 369 recommended: 513 | 2026-10-16T00:49:55+00:00 | Vulnerability · Source |
| CVE-2026-2303 | suse_vex | SUSE CVE CVE-2026-2303 | known affected: 56 known not affected: 599 recommended: 47 | 2026-10-16T00:49:53+00:00 | Vulnerability · Source |
| CVE-2026-2340 | suse_vex | SUSE CVE CVE-2026-2340 | known affected: 1390 recommended: 879 | 2026-10-16T00:49:51+00:00 | Vulnerability · Source |
| CVE-2026-2447 | suse_vex | SUSE CVE CVE-2026-2447 | known affected: 204 recommended: 142 | 2026-10-16T00:49:49+00:00 | Vulnerability · Source |
| CVE-2026-2673 | suse_vex | SUSE CVE CVE-2026-2673 | known not affected: 696 recommended: 42 | 2026-10-16T00:49:43+00:00 | Vulnerability · Source |
| CVE-2026-2920 | suse_vex | SUSE CVE CVE-2026-2920 | recommended: 41 | 2026-10-16T00:49:41+00:00 | Vulnerability · Source |
| CVE-2026-2922 | suse_vex | SUSE CVE CVE-2026-2922 | recommended: 35 | 2026-10-16T00:49:39+00:00 | Vulnerability · Source |
| CVE-2026-3012 | suse_vex | SUSE CVE CVE-2026-3012 | known affected: 388 known not affected: 1256 recommended: 531 | 2026-10-16T00:49:36+00:00 | Vulnerability · Source |
| CVE-2026-3184 | suse_vex | SUSE CVE CVE-2026-3184 | known affected: 922 recommended: 395 | 2026-10-16T00:49:33+00:00 | Vulnerability · Source |
| CVE-2026-3195 | suse_vex | SUSE CVE CVE-2026-3195 | known not affected: 1032 recommended: 505 | 2026-10-16T00:49:31+00:00 | Vulnerability · Source |
| CVE-2026-3196 | suse_vex | SUSE CVE CVE-2026-3196 | known affected: 394 known not affected: 1032 recommended: 561 | 2026-10-16T00:49:29+00:00 | Vulnerability · Source |
| CVE-2026-3201 | suse_vex | SUSE CVE CVE-2026-3201 | known affected: 170 known not affected: 84 recommended: 175 | 2026-10-16T00:49:27+00:00 | Vulnerability · Source |
| CVE-2026-3203 | suse_vex | SUSE CVE CVE-2026-3203 | known not affected: 261 recommended: 163 | 2026-10-16T00:49:25+00:00 | Vulnerability · Source |
| CVE-2026-3505 | suse_vex | SUSE CVE CVE-2026-3505 | known affected: 40 recommended: 100 | 2026-10-16T00:49:14+00:00 | Vulnerability · Source |
| CVE-2026-3608 | suse_vex | SUSE CVE CVE-2026-3608 | recommended: 294 | 2026-10-16T00:49:12+00:00 | Vulnerability · Source |
| CVE-2026-3644 | suse_vex | SUSE CVE CVE-2026-3644 | known affected: 546 recommended: 876 | 2026-10-16T00:49:09+00:00 | Vulnerability · Source |
| CVE-2026-3783 | suse_vex | SUSE CVE CVE-2026-3783 | first fixed: 13 known affected: 398 known not affected: 42 recommended: 193 | 2026-10-16T00:49:07+00:00 | Vulnerability · Source |
| CVE-2026-3784 | suse_vex | SUSE CVE CVE-2026-3784 | first fixed: 13 known affected: 440 recommended: 188 | 2026-10-16T00:49:04+00:00 | Vulnerability · Source |
| CVE-2026-3805 | suse_vex | SUSE CVE CVE-2026-3805 | first fixed: 13 known affected: 398 known not affected: 62 recommended: 176 | 2026-10-16T00:49:02+00:00 | Vulnerability · Source |
| CVE-2026-4105 | suse_vex | SUSE CVE CVE-2026-4105 | known affected: 607 recommended: 472 | 2026-10-16T00:48:59+00:00 | Vulnerability · Source |
| CVE-2026-4519 | suse_vex | SUSE CVE CVE-2026-4519 | known affected: 546 recommended: 920 | 2026-10-16T00:48:51+00:00 | Vulnerability · Source |
| CVE-2026-4786 | suse_vex | SUSE CVE CVE-2026-4786 | known affected: 529 known not affected: 40 recommended: 950 | 2026-10-16T00:48:49+00:00 | Vulnerability · Source |
| CVE-2026-4802 | suse_vex | SUSE CVE CVE-2026-4802 | known affected: 394 recommended: 169 | 2026-10-16T00:48:47+00:00 | Vulnerability · Source |
| CVE-2026-4873 | suse_vex | SUSE CVE CVE-2026-4873 | first fixed: 13 known affected: 445 recommended: 172 | 2026-10-16T00:48:45+00:00 | Vulnerability · Source |
| CVE-2026-4897 | suse_vex | SUSE CVE CVE-2026-4897 | known affected: 550 recommended: 106 | 2026-10-16T00:48:43+00:00 | Vulnerability · Source |
| CVE-2026-5107 | suse_vex | SUSE CVE CVE-2026-5107 | known not affected: 393 recommended: 168 | 2026-10-16T00:48:39+00:00 | Vulnerability · Source |
| CVE-2026-5299 | suse_vex | SUSE CVE CVE-2026-5299 | known not affected: 237 recommended: 54 | 2026-10-16T00:48:37+00:00 | Vulnerability · Source |
| CVE-2026-5342 | suse_vex | SUSE CVE CVE-2026-5342 | known not affected: 9 recommended: 38 | 2026-10-16T00:48:35+00:00 | Vulnerability · Source |
| CVE-2026-5358 | suse_vex | SUSE CVE CVE-2026-5358 | No product status | 2026-10-16T00:48:33+00:00 | Vulnerability · Source |
| CVE-2026-5401 | suse_vex | SUSE CVE CVE-2026-5401 | known affected: 148 recommended: 139 | 2026-10-16T00:48:31+00:00 | Vulnerability · Source |
| CVE-2026-5403 | suse_vex | SUSE CVE CVE-2026-5403 | known affected: 148 recommended: 139 | 2026-10-16T00:48:29+00:00 | Vulnerability · Source |
| CVE-2026-5404 | suse_vex | SUSE CVE CVE-2026-5404 | known affected: 148 recommended: 139 | 2026-10-16T00:48:26+00:00 | Vulnerability · Source |
| CVE-2026-5405 | suse_vex | SUSE CVE CVE-2026-5405 | known affected: 72 known not affected: 60 recommended: 135 | 2026-10-16T00:48:24+00:00 | Vulnerability · Source |
| CVE-2026-5406 | suse_vex | SUSE CVE CVE-2026-5406 | known affected: 148 recommended: 139 | 2026-10-16T00:48:22+00:00 | Vulnerability · Source |
| CVE-2026-5407 | suse_vex | SUSE CVE CVE-2026-5407 | known affected: 148 recommended: 139 | 2026-10-16T00:48:20+00:00 | Vulnerability · Source |
| CVE-2026-5408 | suse_vex | SUSE CVE CVE-2026-5408 | known affected: 148 recommended: 139 | 2026-10-16T00:48:19+00:00 | Vulnerability · Source |
| CVE-2026-5409 | suse_vex | SUSE CVE CVE-2026-5409 | known not affected: 237 recommended: 54 | 2026-10-16T00:48:16+00:00 | Vulnerability · Source |
| CVE-2026-5545 | suse_vex | SUSE CVE CVE-2026-5545 | first fixed: 13 known affected: 445 recommended: 172 | 2026-10-16T00:48:13+00:00 | Vulnerability · Source |
| CVE-2026-5588 | suse_vex | SUSE CVE CVE-2026-5588 | known affected: 40 recommended: 100 | 2026-10-16T00:48:11+00:00 | Vulnerability · Source |
| CVE-2026-5598 | suse_vex | SUSE CVE CVE-2026-5598 | known affected: 40 recommended: 100 | 2026-10-16T00:48:09+00:00 | Vulnerability · Source |
| CVE-2026-5653 | suse_vex | SUSE CVE CVE-2026-5653 | known affected: 148 recommended: 139 | 2026-10-16T00:48:07+00:00 | Vulnerability · Source |
| CVE-2026-5654 | suse_vex | SUSE CVE CVE-2026-5654 | known affected: 24 known not affected: 213 recommended: 54 | 2026-10-16T00:48:04+00:00 | Vulnerability · Source |
| CVE-2026-5656 | suse_vex | SUSE CVE CVE-2026-5656 | known affected: 72 known not affected: 60 recommended: 135 | 2026-10-16T00:48:02+00:00 | Vulnerability · Source |