VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287177 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-12299 | suse_vex | SUSE CVE CVE-2026-12299 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:48+00:00 | Vulnerability · Source |
| CVE-2026-12302 | suse_vex | SUSE CVE CVE-2026-12302 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:47+00:00 | Vulnerability · Source |
| CVE-2026-12304 | suse_vex | SUSE CVE CVE-2026-12304 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:45+00:00 | Vulnerability · Source |
| CVE-2026-12305 | suse_vex | SUSE CVE CVE-2026-12305 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:43+00:00 | Vulnerability · Source |
| CVE-2026-12306 | suse_vex | SUSE CVE CVE-2026-12306 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:41+00:00 | Vulnerability · Source |
| CVE-2026-12307 | suse_vex | SUSE CVE CVE-2026-12307 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:40+00:00 | Vulnerability · Source |
| CVE-2026-12308 | suse_vex | SUSE CVE CVE-2026-12308 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:38+00:00 | Vulnerability · Source |
| CVE-2026-12309 | suse_vex | SUSE CVE CVE-2026-12309 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:36+00:00 | Vulnerability · Source |
| CVE-2026-12310 | suse_vex | SUSE CVE CVE-2026-12310 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:34+00:00 | Vulnerability · Source |
| CVE-2026-12311 | suse_vex | SUSE CVE CVE-2026-12311 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:33+00:00 | Vulnerability · Source |
| CVE-2026-12312 | suse_vex | SUSE CVE CVE-2026-12312 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:31+00:00 | Vulnerability · Source |
| CVE-2026-12313 | suse_vex | SUSE CVE CVE-2026-12313 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:29+00:00 | Vulnerability · Source |
| CVE-2026-12314 | suse_vex | SUSE CVE CVE-2026-12314 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:27+00:00 | Vulnerability · Source |
| CVE-2026-12315 | suse_vex | SUSE CVE CVE-2026-12315 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:26+00:00 | Vulnerability · Source |
| CVE-2026-12324 | suse_vex | SUSE CVE CVE-2026-12324 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:24+00:00 | Vulnerability · Source |
| CVE-2026-12325 | suse_vex | SUSE CVE CVE-2026-12325 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:23+00:00 | Vulnerability · Source |
| CVE-2026-12327 | suse_vex | SUSE CVE CVE-2026-12327 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:21+00:00 | Vulnerability · Source |
| CVE-2026-12328 | suse_vex | SUSE CVE CVE-2026-12328 | first fixed: 8 known affected: 30 recommended: 128 | 2026-08-03T23:53:20+00:00 | Vulnerability · Source |
| CVE-2026-12329 | suse_vex | SUSE CVE CVE-2026-12329 | first fixed: 8 known affected: 30 recommended: 123 | 2026-08-03T23:53:18+00:00 | Vulnerability · Source |
| CVE-2026-12330 | suse_vex | SUSE CVE CVE-2026-12330 | first fixed: 8 known affected: 30 recommended: 123 | 2026-08-03T23:53:16+00:00 | Vulnerability · Source |
| CVE-2026-12932 | suse_vex | SUSE CVE CVE-2026-12932 | known affected: 66 known not affected: 25 | 2026-08-03T23:53:00+00:00 | Vulnerability · Source |
| CVE-2026-12996 | suse_vex | SUSE CVE CVE-2026-12996 | known affected: 41 known not affected: 50 | 2026-08-03T23:52:59+00:00 | Vulnerability · Source |
| CVE-2026-13117 | suse_vex | SUSE CVE CVE-2026-13117 | known affected: 41 known not affected: 50 | 2026-08-03T23:52:57+00:00 | Vulnerability · Source |
| CVE-2026-13379 | suse_vex | SUSE CVE CVE-2026-13379 | known not affected: 91 | 2026-08-03T23:52:51+00:00 | Vulnerability · Source |
| CVE-2026-13595 | suse_vex | SUSE CVE CVE-2026-13595 | known affected: 457 recommended: 27 | 2026-08-03T23:52:47+00:00 | Vulnerability · Source |
| CVE-2026-13601 | suse_vex | SUSE CVE CVE-2026-13601 | known affected: 30 recommended: 94 | 2026-08-03T23:52:45+00:00 | Vulnerability · Source |
| CVE-2026-15043 | suse_vex | SUSE CVE CVE-2026-15043 | known affected: 10 recommended: 28 | 2026-08-03T23:52:36+00:00 | Vulnerability · Source |
| CVE-2026-15392 | suse_vex | SUSE CVE CVE-2026-15392 | known affected: 10 recommended: 28 | 2026-08-03T23:52:32+00:00 | Vulnerability · Source |
| CVE-2026-17346 | suse_vex | SUSE CVE CVE-2026-17346 | known affected: 75 | 2026-08-03T23:50:53+00:00 | Vulnerability · Source |
| CVE-2026-17347 | suse_vex | SUSE CVE CVE-2026-17347 | known not affected: 75 | 2026-08-03T23:50:51+00:00 | Vulnerability · Source |
| CVE-2026-17348 | suse_vex | SUSE CVE CVE-2026-17348 | known affected: 75 | 2026-08-03T23:50:49+00:00 | Vulnerability · Source |
| CVE-2026-17349 | suse_vex | SUSE CVE CVE-2026-17349 | known not affected: 75 | 2026-08-03T23:50:47+00:00 | Vulnerability · Source |
| CVE-2026-17350 | suse_vex | SUSE CVE CVE-2026-17350 | known not affected: 75 | 2026-08-03T23:50:44+00:00 | Vulnerability · Source |
| CVE-2026-17351 | suse_vex | SUSE CVE CVE-2026-17351 | known not affected: 75 | 2026-08-03T23:50:41+00:00 | Vulnerability · Source |
| CVE-2026-17566 | suse_vex | SUSE CVE CVE-2026-17566 | known not affected: 75 | 2026-08-03T23:50:39+00:00 | Vulnerability · Source |
| CVE-2026-17572 | suse_vex | SUSE CVE CVE-2026-17572 | known affected: 707 | 2026-08-03T23:50:37+00:00 | Vulnerability · Source |
| CVE-2026-17573 | suse_vex | SUSE CVE CVE-2026-17573 | known affected: 707 | 2026-08-03T23:50:34+00:00 | Vulnerability · Source |
| CVE-2026-17574 | suse_vex | SUSE CVE CVE-2026-17574 | known affected: 707 | 2026-08-03T23:50:32+00:00 | Vulnerability · Source |
| CVE-2026-18321 | suse_vex | SUSE CVE CVE-2026-18321 | recommended: 6 | 2026-08-03T23:50:29+00:00 | Vulnerability · Source |
| CVE-2026-18358 | suse_vex | SUSE CVE CVE-2026-18358 | known not affected: 19 | 2026-08-03T23:50:27+00:00 | Vulnerability · Source |
| CVE-2026-18446 | suse_vex | SUSE CVE CVE-2026-18446 | known affected: 115 known not affected: 41 | 2026-08-03T23:50:25+00:00 | Vulnerability · Source |
| CVE-2026-18581 | suse_vex | SUSE CVE CVE-2026-18581 | No product status | 2026-08-03T23:50:24+00:00 | Vulnerability · Source |
| CVE-2026-18651 | suse_vex | SUSE CVE CVE-2026-18651 | known affected: 108 | 2026-08-03T23:50:22+00:00 | Vulnerability · Source |
| CVE-2026-23385 | suse_vex | SUSE CVE CVE-2026-23385 | known affected: 22 known not affected: 318 | 2026-08-03T23:49:46+00:00 | Vulnerability · Source |
| CVE-2026-25800 | suse_vex | SUSE CVE CVE-2026-25800 | known affected: 112 known not affected: 643 | 2026-08-03T23:49:29+00:00 | Vulnerability · Source |
| CVE-2026-27456 | suse_vex | SUSE CVE CVE-2026-27456 | known affected: 729 recommended: 357 | 2026-08-03T23:49:24+00:00 | Vulnerability · Source |
| CVE-2026-28390 | suse_vex | SUSE CVE CVE-2026-28390 | first fixed: 45 known affected: 476 known not affected: 92 recommended: 401 | 2026-08-03T23:49:22+00:00 | Vulnerability · Source |
| CVE-2026-30922 | suse_vex | SUSE CVE CVE-2026-30922 | known affected: 394 recommended: 246 | 2026-08-03T23:49:17+00:00 | Vulnerability · Source |
| CVE-2026-31442 | suse_vex | SUSE CVE CVE-2026-31442 | known not affected: 324 | 2026-08-03T23:49:07+00:00 | Vulnerability · Source |
| CVE-2026-31443 | suse_vex | SUSE CVE CVE-2026-31443 | known affected: 17 known not affected: 300 | 2026-08-03T23:49:06+00:00 | Vulnerability · Source |