VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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 |
| CVE-2026-31467 | suse_vex | SUSE CVE CVE-2026-31467 | known affected: 185 known not affected: 115 recommended: 42 | 2026-08-03T23:49:02+00:00 | Vulnerability · Source |
| CVE-2026-31474 | suse_vex | SUSE CVE CVE-2026-31474 | known affected: 533 known not affected: 126 recommended: 181 | 2026-08-03T23:48:59+00:00 | Vulnerability · Source |
| CVE-2026-31475 | suse_vex | SUSE CVE CVE-2026-31475 | known not affected: 315 | 2026-08-03T23:48:58+00:00 | Vulnerability · Source |
| CVE-2026-31487 | suse_vex | SUSE CVE CVE-2026-31487 | known affected: 250 known not affected: 67 | 2026-08-03T23:48:54+00:00 | Vulnerability · Source |
| CVE-2026-31489 | suse_vex | SUSE CVE CVE-2026-31489 | known not affected: 298 | 2026-08-03T23:48:52+00:00 | Vulnerability · Source |
| CVE-2026-31491 | suse_vex | SUSE CVE CVE-2026-31491 | known affected: 202 known not affected: 93 | 2026-08-03T23:48:51+00:00 | Vulnerability · Source |
| CVE-2026-31527 | suse_vex | SUSE CVE CVE-2026-31527 | known affected: 313 known not affected: 4 | 2026-08-03T23:48:39+00:00 | Vulnerability · Source |
| CVE-2026-31529 | suse_vex | SUSE CVE CVE-2026-31529 | known not affected: 320 | 2026-08-03T23:48:37+00:00 | Vulnerability · Source |
| CVE-2026-31532 | suse_vex | SUSE CVE CVE-2026-31532 | known affected: 597 known not affected: 27 recommended: 243 | 2026-08-03T23:48:35+00:00 | Vulnerability · Source |
| CVE-2026-31557 | suse_vex | SUSE CVE CVE-2026-31557 | known affected: 202 known not affected: 115 | 2026-08-03T23:48:29+00:00 | Vulnerability · Source |
| CVE-2026-31581 | suse_vex | SUSE CVE CVE-2026-31581 | known affected: 641 recommended: 205 | 2026-08-03T23:48:24+00:00 | Vulnerability · Source |
| CVE-2026-31582 | suse_vex | SUSE CVE CVE-2026-31582 | known affected: 29 known not affected: 292 recommended: 4 | 2026-08-03T23:48:22+00:00 | Vulnerability · Source |
| CVE-2026-31591 | suse_vex | SUSE CVE CVE-2026-31591 | known affected: 394 known not affected: 260 recommended: 102 | 2026-08-03T23:48:18+00:00 | Vulnerability · Source |
| CVE-2026-31595 | suse_vex | SUSE CVE CVE-2026-31595 | known affected: 114 known not affected: 203 recommended: 4 | 2026-08-03T23:48:15+00:00 | Vulnerability · Source |
| CVE-2026-31600 | suse_vex | SUSE CVE CVE-2026-31600 | known affected: 321 recommended: 4 | 2026-08-03T23:48:10+00:00 | Vulnerability · Source |
| CVE-2026-31606 | suse_vex | SUSE CVE CVE-2026-31606 | known affected: 296 known not affected: 21 recommended: 4 | 2026-08-03T23:48:05+00:00 | Vulnerability · Source |
| CVE-2026-31607 | suse_vex | SUSE CVE CVE-2026-31607 | known affected: 456 known not affected: 15 recommended: 467 | 2026-08-03T23:48:04+00:00 | Vulnerability · Source |
| CVE-2026-31620 | suse_vex | SUSE CVE CVE-2026-31620 | known not affected: 315 recommended: 4 | 2026-08-03T23:48:00+00:00 | Vulnerability · Source |
| CVE-2026-31721 | suse_vex | SUSE CVE CVE-2026-31721 | known affected: 30 known not affected: 263 | 2026-08-03T23:47:41+00:00 | Vulnerability · Source |
| CVE-2026-31739 | suse_vex | SUSE CVE CVE-2026-31739 | known not affected: 291 | 2026-08-03T23:47:36+00:00 | Vulnerability · Source |
| CVE-2026-31740 | suse_vex | SUSE CVE CVE-2026-31740 | known not affected: 293 | 2026-08-03T23:47:35+00:00 | Vulnerability · Source |
| CVE-2026-31741 | suse_vex | SUSE CVE CVE-2026-31741 | known not affected: 291 | 2026-08-03T23:47:33+00:00 | Vulnerability · Source |
| CVE-2026-31772 | suse_vex | SUSE CVE CVE-2026-31772 | known not affected: 291 recommended: 83 | 2026-08-03T23:47:26+00:00 | Vulnerability · Source |
| CVE-2026-31775 | suse_vex | SUSE CVE CVE-2026-31775 | known not affected: 291 | 2026-08-03T23:47:24+00:00 | Vulnerability · Source |
| CVE-2026-34933 | suse_vex | SUSE CVE CVE-2026-34933 | known affected: 716 recommended: 306 | 2026-08-03T23:47:07+00:00 | Vulnerability · Source |
| CVE-2026-38974 | suse_vex | SUSE CVE CVE-2026-38974 | recommended: 29 | 2026-08-03T23:46:57+00:00 | Vulnerability · Source |
| CVE-2026-42006 | suse_vex | SUSE CVE CVE-2026-42006 | known affected: 198 known not affected: 32 recommended: 70 | 2026-08-03T23:46:16+00:00 | Vulnerability · Source |
| CVE-2026-42492 | suse_vex | SUSE CVE CVE-2026-42492 | known not affected: 151 recommended: 7 | 2026-08-03T23:46:09+00:00 | Vulnerability · Source |