VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305807 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-68398 | suse_vex | SUSE CVE CVE-2026-68398 | known affected: 587 known not affected: 6 recommended: 447 | 2026-10-08T17:06:19+00:00 | Vulnerability · Source |
| CVE-2026-68426 | suse_vex | SUSE CVE CVE-2026-68426 | known affected: 535 known not affected: 6 recommended: 550 | 2026-10-08T17:06:14+00:00 | Vulnerability · Source |
| CVE-2026-68441 | suse_vex | SUSE CVE CVE-2026-68441 | known affected: 404 known not affected: 4 | 2026-10-08T17:06:11+00:00 | Vulnerability · Source |
| CVE-2026-68451 | suse_vex | SUSE CVE CVE-2026-68451 | known affected: 253 known not affected: 143 | 2026-10-08T17:06:08+00:00 | Vulnerability · Source |
| CVE-2026-68452 | suse_vex | SUSE CVE CVE-2026-68452 | known affected: 303 known not affected: 93 | 2026-10-08T17:06:05+00:00 | Vulnerability · Source |
| CVE-2026-68454 | suse_vex | SUSE CVE CVE-2026-68454 | known affected: 211 known not affected: 185 | 2026-10-08T17:06:02+00:00 | Vulnerability · Source |
| CVE-2026-68471 | suse_vex | SUSE CVE CVE-2026-68471 | known affected: 65 known not affected: 362 | 2026-10-08T17:05:59+00:00 | Vulnerability · Source |
| CVE-2026-68477 | suse_vex | SUSE CVE CVE-2026-68477 | known affected: 398 | 2026-10-08T17:05:56+00:00 | Vulnerability · Source |
| CVE-2026-68580 | suse_vex | SUSE CVE CVE-2026-68580 | known affected: 167 recommended: 21 | 2026-10-08T17:05:50+00:00 | Vulnerability · Source |
| CVE-2026-70907 | suse_vex | SUSE CVE CVE-2026-70907 | known affected: 538 recommended: 803 | 2026-10-08T17:05:47+00:00 | Vulnerability · Source |
| CVE-2026-72012 | suse_vex | SUSE CVE CVE-2026-72012 | known affected: 157 known not affected: 239 | 2026-10-08T17:05:41+00:00 | Vulnerability · Source |
| CVE-2026-72018 | suse_vex | SUSE CVE CVE-2026-72018 | known affected: 77 known not affected: 350 | 2026-10-08T17:05:38+00:00 | Vulnerability · Source |
| CVE-2026-72020 | suse_vex | SUSE CVE CVE-2026-72020 | known affected: 525 known not affected: 4 recommended: 447 | 2026-10-08T17:05:36+00:00 | Vulnerability · Source |
| CVE-2026-72025 | suse_vex | SUSE CVE CVE-2026-72025 | known affected: 398 | 2026-10-08T17:05:32+00:00 | Vulnerability · Source |
| CVE-2026-72066 | suse_vex | SUSE CVE CVE-2026-72066 | known affected: 351 known not affected: 47 | 2026-10-08T17:05:29+00:00 | Vulnerability · Source |
| CVE-2026-72069 | suse_vex | SUSE CVE CVE-2026-72069 | known affected: 440 known not affected: 143 recommended: 507 | 2026-10-08T17:05:27+00:00 | Vulnerability · Source |
| CVE-2026-72070 | suse_vex | SUSE CVE CVE-2026-72070 | known affected: 355 known not affected: 41 | 2026-10-08T17:05:24+00:00 | Vulnerability · Source |
| CVE-2026-72072 | suse_vex | SUSE CVE CVE-2026-72072 | known affected: 423 known not affected: 202 recommended: 392 | 2026-10-08T17:05:21+00:00 | Vulnerability · Source |
| CVE-2026-72098 | suse_vex | SUSE CVE CVE-2026-72098 | known affected: 394 known not affected: 4 recommended: 103 | 2026-10-08T17:05:19+00:00 | Vulnerability · Source |
| CVE-2026-72102 | suse_vex | SUSE CVE CVE-2026-72102 | known affected: 303 known not affected: 93 recommended: 83 | 2026-10-08T17:05:16+00:00 | Vulnerability · Source |
| CVE-2026-72129 | suse_vex | SUSE CVE CVE-2026-72129 | known affected: 392 known not affected: 6 recommended: 103 | 2026-10-08T17:05:11+00:00 | Vulnerability · Source |
| CVE-2026-72130 | suse_vex | SUSE CVE CVE-2026-72130 | known affected: 94 known not affected: 333 recommended: 83 | 2026-10-08T17:05:09+00:00 | Vulnerability · Source |
| CVE-2026-72135 | suse_vex | SUSE CVE CVE-2026-72135 | known affected: 542 known not affected: 99 recommended: 195 | 2026-10-08T17:05:07+00:00 | Vulnerability · Source |
| CVE-2026-72147 | suse_vex | SUSE CVE CVE-2026-72147 | known affected: 75 known not affected: 352 | 2026-10-08T17:05:05+00:00 | Vulnerability · Source |
| CVE-2026-72166 | suse_vex | SUSE CVE CVE-2026-72166 | known affected: 357 known not affected: 41 | 2026-10-08T17:05:03+00:00 | Vulnerability · Source |
| CVE-2026-72218 | suse_vex | SUSE CVE CVE-2026-72218 | known affected: 157 known not affected: 239 | 2026-10-08T17:05:00+00:00 | Vulnerability · Source |
| CVE-2026-72219 | suse_vex | SUSE CVE CVE-2026-72219 | known affected: 157 known not affected: 239 | 2026-10-08T17:04:58+00:00 | Vulnerability · Source |
| CVE-2026-72224 | suse_vex | SUSE CVE CVE-2026-72224 | known affected: 382 known not affected: 16 | 2026-10-08T17:04:56+00:00 | Vulnerability · Source |
| CVE-2026-72237 | suse_vex | SUSE CVE CVE-2026-72237 | known affected: 116 known not affected: 280 | 2026-10-08T17:04:55+00:00 | Vulnerability · Source |
| CVE-2026-72247 | suse_vex | SUSE CVE CVE-2026-72247 | known affected: 262 known not affected: 134 | 2026-10-08T17:04:53+00:00 | Vulnerability · Source |
| CVE-2026-72251 | suse_vex | SUSE CVE CVE-2026-72251 | known affected: 529 recommended: 447 | 2026-10-08T17:04:51+00:00 | Vulnerability · Source |
| CVE-2026-72256 | suse_vex | SUSE CVE CVE-2026-72256 | known affected: 357 known not affected: 41 | 2026-10-08T17:04:49+00:00 | Vulnerability · Source |
| CVE-2026-72288 | suse_vex | SUSE CVE CVE-2026-72288 | known affected: 490 known not affected: 93 recommended: 424 | 2026-10-08T17:04:45+00:00 | Vulnerability · Source |
| CVE-2026-72289 | suse_vex | SUSE CVE CVE-2026-72289 | known affected: 579 known not affected: 4 recommended: 424 | 2026-10-08T17:04:43+00:00 | Vulnerability · Source |
| CVE-2026-72299 | suse_vex | SUSE CVE CVE-2026-72299 | known affected: 303 known not affected: 93 | 2026-10-08T17:04:41+00:00 | Vulnerability · Source |
| CVE-2026-72321 | suse_vex | SUSE CVE CVE-2026-72321 | known affected: 398 | 2026-10-08T17:04:39+00:00 | Vulnerability · Source |
| CVE-2026-72322 | suse_vex | SUSE CVE CVE-2026-72322 | known affected: 326 known not affected: 93 | 2026-10-08T17:04:37+00:00 | Vulnerability · Source |
| CVE-2026-72348 | suse_vex | SUSE CVE CVE-2026-72348 | known affected: 398 | 2026-10-08T17:04:35+00:00 | Vulnerability · Source |
| CVE-2026-72349 | suse_vex | SUSE CVE CVE-2026-72349 | known affected: 351 known not affected: 47 | 2026-10-08T17:04:34+00:00 | Vulnerability · Source |
| CVE-2026-72351 | suse_vex | SUSE CVE CVE-2026-72351 | known affected: 394 known not affected: 4 | 2026-10-08T17:04:32+00:00 | Vulnerability · Source |
| CVE-2026-72352 | suse_vex | SUSE CVE CVE-2026-72352 | known affected: 157 known not affected: 239 | 2026-10-08T17:04:30+00:00 | Vulnerability · Source |
| CVE-2026-72383 | suse_vex | SUSE CVE CVE-2026-72383 | known affected: 394 known not affected: 4 | 2026-10-08T17:04:28+00:00 | Vulnerability · Source |
| CVE-2026-72389 | suse_vex | SUSE CVE CVE-2026-72389 | known affected: 549 recommended: 462 | 2026-10-08T17:04:26+00:00 | Vulnerability · Source |
| CVE-2026-72392 | suse_vex | SUSE CVE CVE-2026-72392 | known affected: 398 | 2026-10-08T17:04:25+00:00 | Vulnerability · Source |
| CVE-2026-72404 | suse_vex | SUSE CVE CVE-2026-72404 | known affected: 303 known not affected: 93 | 2026-10-08T17:04:23+00:00 | Vulnerability · Source |
| CVE-2026-72406 | suse_vex | SUSE CVE CVE-2026-72406 | known affected: 352 known not affected: 46 | 2026-10-08T17:04:21+00:00 | Vulnerability · Source |
| CVE-2026-72413 | suse_vex | SUSE CVE CVE-2026-72413 | known affected: 180 known not affected: 239 | 2026-10-08T17:04:20+00:00 | Vulnerability · Source |
| CVE-2026-72433 | suse_vex | SUSE CVE CVE-2026-72433 | known affected: 238 known not affected: 158 | 2026-10-08T17:04:18+00:00 | Vulnerability · Source |
| CVE-2026-72434 | suse_vex | SUSE CVE CVE-2026-72434 | known affected: 165 known not affected: 262 | 2026-10-08T17:04:16+00:00 | Vulnerability · Source |
| CVE-2026-72435 | suse_vex | SUSE CVE CVE-2026-72435 | known affected: 351 known not affected: 47 | 2026-10-08T17:04:14+00:00 | Vulnerability · Source |