VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292286 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-12026 | suse_vex | SUSE CVE CVE-2026-12026 | recommended: 6 | 2026-07-03T03:26:36+00:00 | Vulnerability · Source |
| CVE-2026-13006 | suse_vex | SUSE CVE CVE-2026-13006 | recommended: 4 | 2026-07-03T03:26:26+00:00 | Vulnerability · Source |
| CVE-2026-13769 | suse_vex | SUSE CVE CVE-2026-13769 | known affected: 31 | 2026-07-03T03:26:16+00:00 | Vulnerability · Source |
| CVE-2026-14324 | suse_vex | SUSE CVE CVE-2026-14324 | known affected: 98 known not affected: 98 | 2026-07-03T03:26:11+00:00 | Vulnerability · Source |
| CVE-2026-14330 | suse_vex | SUSE CVE CVE-2026-14330 | known affected: 175 known not affected: 21 | 2026-07-03T03:26:09+00:00 | Vulnerability · Source |
| CVE-2026-31451 | suse_vex | SUSE CVE CVE-2026-31451 | known affected: 47 known not affected: 184 | 2026-07-03T03:20:39+00:00 | Vulnerability · Source |
| CVE-2026-31622 | suse_vex | SUSE CVE CVE-2026-31622 | known affected: 458 known not affected: 19 recommended: 158 | 2026-07-03T03:19:22+00:00 | Vulnerability · Source |
| CVE-2026-32762 | suse_vex | SUSE CVE CVE-2026-32762 | known not affected: 89 | 2026-07-03T03:18:19+00:00 | Vulnerability · Source |
| CVE-2026-34835 | suse_vex | SUSE CVE CVE-2026-34835 | known not affected: 89 | 2026-07-03T03:17:43+00:00 | Vulnerability · Source |
| CVE-2026-35505 | suse_vex | SUSE CVE CVE-2026-35505 | No product status | 2026-07-03T03:17:25+00:00 | Vulnerability · Source |
| CVE-2026-40354 | suse_vex | SUSE CVE CVE-2026-40354 | known affected: 56 recommended: 18 | 2026-07-03T03:16:53+00:00 | Vulnerability · Source |
| CVE-2026-40917 | suse_vex | SUSE CVE CVE-2026-40917 | recommended: 9 | 2026-07-03T03:16:44+00:00 | Vulnerability · Source |
| CVE-2026-42487 | suse_vex | SUSE CVE CVE-2026-42487 | known affected: 434 recommended: 133 | 2026-07-03T03:15:59+00:00 | Vulnerability · Source |
| CVE-2026-42488 | suse_vex | SUSE CVE CVE-2026-42488 | known affected: 388 known not affected: 46 recommended: 133 | 2026-07-03T03:15:57+00:00 | Vulnerability · Source |
| CVE-2026-42489 | suse_vex | SUSE CVE CVE-2026-42489 | known affected: 434 recommended: 133 | 2026-07-03T03:15:55+00:00 | Vulnerability · Source |
| CVE-2026-44488 | suse_vex | SUSE CVE CVE-2026-44488 | known affected: 3 known not affected: 83 | 2026-07-03T03:11:25+00:00 | Vulnerability · Source |
| CVE-2026-44492 | suse_vex | SUSE CVE CVE-2026-44492 | known affected: 3 known not affected: 83 | 2026-07-03T03:11:23+00:00 | Vulnerability · Source |
| CVE-2026-44494 | suse_vex | SUSE CVE CVE-2026-44494 | known affected: 3 known not affected: 83 | 2026-07-03T03:11:21+00:00 | Vulnerability · Source |
| CVE-2026-44495 | suse_vex | SUSE CVE CVE-2026-44495 | known affected: 3 known not affected: 83 | 2026-07-03T03:11:19+00:00 | Vulnerability · Source |
| CVE-2026-44496 | suse_vex | SUSE CVE CVE-2026-44496 | known affected: 3 known not affected: 83 | 2026-07-03T03:11:17+00:00 | Vulnerability · Source |
| CVE-2026-44628 | suse_vex | SUSE CVE CVE-2026-44628 | No product status | 2026-07-03T03:11:14+00:00 | Vulnerability · Source |
| CVE-2026-44932 | suse_vex | SUSE CVE CVE-2026-44932 | known affected: 409 recommended: 71 | 2026-07-03T03:11:00+00:00 | Vulnerability · Source |
| CVE-2026-44946 | suse_vex | SUSE CVE CVE-2026-44946 | No product status | 2026-07-03T03:10:49+00:00 | Vulnerability · Source |
| CVE-2026-45372 | suse_vex | SUSE CVE CVE-2026-45372 | known affected: 5 recommended: 2 | 2026-07-03T03:10:40+00:00 | Vulnerability · Source |
| CVE-2026-45822 | suse_vex | SUSE CVE CVE-2026-45822 | known affected: 195 known not affected: 227 | 2026-07-03T03:10:25+00:00 | Vulnerability · Source |
| CVE-2026-45864 | suse_vex | SUSE CVE CVE-2026-45864 | known affected: 4 known not affected: 287 | 2026-07-03T03:10:05+00:00 | Vulnerability · Source |
| CVE-2026-46527 | suse_vex | SUSE CVE CVE-2026-46527 | known affected: 5 recommended: 2 | 2026-07-03T03:07:43+00:00 | Vulnerability · Source |
| CVE-2026-50003 | suse_vex | SUSE CVE CVE-2026-50003 | No product status | 2026-07-03T03:05:51+00:00 | Vulnerability · Source |
| CVE-2026-50052 | suse_vex | SUSE CVE CVE-2026-50052 | recommended: 3 | 2026-07-03T03:05:48+00:00 | Vulnerability · Source |
| CVE-2026-50254 | suse_vex | SUSE CVE CVE-2026-50254 | No product status | 2026-07-03T03:05:44+00:00 | Vulnerability · Source |
| CVE-2026-52868 | suse_vex | SUSE CVE CVE-2026-52868 | No product status | 2026-07-03T03:05:40+00:00 | Vulnerability · Source |
| CVE-2026-53114 | suse_vex | SUSE CVE CVE-2026-53114 | known affected: 15 known not affected: 276 | 2026-07-03T03:05:04+00:00 | Vulnerability · Source |
| CVE-2026-53118 | suse_vex | SUSE CVE CVE-2026-53118 | known affected: 160 known not affected: 131 | 2026-07-03T03:05:02+00:00 | Vulnerability · Source |
| CVE-2026-53326 | suse_vex | SUSE CVE CVE-2026-53326 | known not affected: 277 | 2026-07-03T03:04:36+00:00 | Vulnerability · Source |
| CVE-2026-53327 | suse_vex | SUSE CVE CVE-2026-53327 | known affected: 200 known not affected: 77 | 2026-07-03T03:04:34+00:00 | Vulnerability · Source |
| CVE-2026-53328 | suse_vex | SUSE CVE CVE-2026-53328 | known not affected: 277 | 2026-07-03T03:04:32+00:00 | Vulnerability · Source |
| CVE-2026-53333 | suse_vex | SUSE CVE CVE-2026-53333 | known not affected: 277 | 2026-07-03T03:04:23+00:00 | Vulnerability · Source |
| CVE-2026-53334 | suse_vex | SUSE CVE CVE-2026-53334 | known not affected: 277 | 2026-07-03T03:04:20+00:00 | Vulnerability · Source |
| CVE-2026-53336 | suse_vex | SUSE CVE CVE-2026-53336 | known affected: 112 known not affected: 165 | 2026-07-03T03:04:17+00:00 | Vulnerability · Source |
| CVE-2026-53340 | suse_vex | SUSE CVE CVE-2026-53340 | known not affected: 277 | 2026-07-03T03:04:11+00:00 | Vulnerability · Source |
| CVE-2026-53343 | suse_vex | SUSE CVE CVE-2026-53343 | known not affected: 277 | 2026-07-03T03:04:06+00:00 | Vulnerability · Source |
| CVE-2026-53344 | suse_vex | SUSE CVE CVE-2026-53344 | known affected: 200 known not affected: 77 | 2026-07-03T03:04:04+00:00 | Vulnerability · Source |
| CVE-2026-53346 | suse_vex | SUSE CVE CVE-2026-53346 | known affected: 15 known not affected: 262 | 2026-07-03T03:04:00+00:00 | Vulnerability · Source |
| CVE-2026-53349 | suse_vex | SUSE CVE CVE-2026-53349 | known affected: 277 | 2026-07-03T03:03:54+00:00 | Vulnerability · Source |
| CVE-2026-53353 | suse_vex | SUSE CVE CVE-2026-53353 | known affected: 273 known not affected: 4 | 2026-07-03T03:03:45+00:00 | Vulnerability · Source |
| CVE-2026-53606 | suse_vex | SUSE CVE CVE-2026-53606 | known affected: 6 known not affected: 306 | 2026-07-03T03:02:59+00:00 | Vulnerability · Source |
| CVE-2026-54399 | suse_vex | SUSE CVE CVE-2026-54399 | known not affected: 26 | 2026-07-03T03:02:46+00:00 | Vulnerability · Source |
| CVE-2026-54428 | suse_vex | SUSE CVE CVE-2026-54428 | known not affected: 26 | 2026-07-03T03:02:44+00:00 | Vulnerability · Source |
| CVE-2026-54672 | suse_vex | SUSE CVE CVE-2026-54672 | No product status | 2026-07-03T03:02:39+00:00 | Vulnerability · Source |
| CVE-2026-54673 | suse_vex | SUSE CVE CVE-2026-54673 | No product status | 2026-07-03T03:02:37+00:00 | Vulnerability · Source |