VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305869 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-72436 | suse_vex | SUSE CVE CVE-2026-72436 | known affected: 302 known not affected: 117 | 2026-10-08T17:04:12+00:00 | Vulnerability · Source |
| CVE-2026-72444 | suse_vex | SUSE CVE CVE-2026-72444 | known affected: 394 known not affected: 4 | 2026-10-08T17:04:10+00:00 | Vulnerability · Source |
| CVE-2026-72447 | suse_vex | SUSE CVE CVE-2026-72447 | known affected: 392 known not affected: 6 | 2026-10-08T17:04:09+00:00 | Vulnerability · Source |
| CVE-2026-72491 | suse_vex | SUSE CVE CVE-2026-72491 | known affected: 390 known not affected: 6 | 2026-10-08T17:04:07+00:00 | Vulnerability · Source |
| CVE-2026-72522 | suse_vex | SUSE CVE CVE-2026-72522 | known affected: 596 known not affected: 7297 recommended: 44 | 2026-10-08T17:04:04+00:00 | Vulnerability · Source |
| CVE-2026-72568 | suse_vex | SUSE CVE CVE-2026-72568 | recommended: 6 | 2026-10-08T17:04:02+00:00 | Vulnerability · Source |
| CVE-2026-73066 | suse_vex | SUSE CVE CVE-2026-73066 | recommended: 8 | 2026-10-08T17:04:00+00:00 | Vulnerability · Source |
| CVE-2026-73283 | suse_vex | SUSE CVE CVE-2026-73283 | known affected: 298 known not affected: 20 recommended: 12 | 2026-10-08T17:03:58+00:00 | Vulnerability · Source |
| CVE-2026-73433 | suse_vex | SUSE CVE CVE-2026-73433 | known affected: 96 recommended: 8 | 2026-10-08T17:03:57+00:00 | Vulnerability · Source |
| CVE-2026-73434 | suse_vex | SUSE CVE CVE-2026-73434 | known affected: 96 recommended: 8 | 2026-10-08T17:03:55+00:00 | Vulnerability · Source |
| CVE-2026-74256 | suse_vex | SUSE CVE CVE-2026-74256 | known affected: 303 known not affected: 93 | 2026-10-08T17:03:53+00:00 | Vulnerability · Source |
| CVE-2026-74257 | suse_vex | SUSE CVE CVE-2026-74257 | known affected: 253 known not affected: 143 | 2026-10-08T17:03:51+00:00 | Vulnerability · Source |
| CVE-2026-74258 | suse_vex | SUSE CVE CVE-2026-74258 | known affected: 157 known not affected: 239 | 2026-10-08T17:03:50+00:00 | Vulnerability · Source |
| CVE-2026-74267 | suse_vex | SUSE CVE CVE-2026-74267 | known affected: 361 known not affected: 37 | 2026-10-08T17:03:48+00:00 | Vulnerability · Source |
| CVE-2026-74268 | suse_vex | SUSE CVE CVE-2026-74268 | known affected: 392 known not affected: 6 | 2026-10-08T17:03:45+00:00 | Vulnerability · Source |
| CVE-2026-74281 | suse_vex | SUSE CVE CVE-2026-74281 | known affected: 303 known not affected: 93 | 2026-10-08T17:03:43+00:00 | Vulnerability · Source |
| CVE-2026-74283 | suse_vex | SUSE CVE CVE-2026-74283 | known affected: 394 known not affected: 4 | 2026-10-08T17:03:41+00:00 | Vulnerability · Source |
| CVE-2026-74288 | suse_vex | SUSE CVE CVE-2026-74288 | known affected: 392 known not affected: 6 | 2026-10-08T17:03:39+00:00 | Vulnerability · Source |
| CVE-2026-74289 | suse_vex | SUSE CVE CVE-2026-74289 | known affected: 392 known not affected: 6 | 2026-10-08T17:03:37+00:00 | Vulnerability · Source |
| CVE-2026-74290 | suse_vex | SUSE CVE CVE-2026-74290 | known affected: 398 | 2026-10-08T17:03:35+00:00 | Vulnerability · Source |
| CVE-2026-74330 | suse_vex | SUSE CVE CVE-2026-74330 | known affected: 398 | 2026-10-08T17:03:34+00:00 | Vulnerability · Source |
| CVE-2026-74345 | suse_vex | SUSE CVE CVE-2026-74345 | known affected: 452 known not affected: 143 recommended: 424 | 2026-10-08T17:03:32+00:00 | Vulnerability · Source |
| CVE-2026-74356 | suse_vex | SUSE CVE CVE-2026-74356 | known affected: 107 known not affected: 289 | 2026-10-08T17:03:30+00:00 | Vulnerability · Source |
| CVE-2026-74359 | suse_vex | SUSE CVE CVE-2026-74359 | known affected: 357 known not affected: 41 | 2026-10-08T17:03:28+00:00 | Vulnerability · Source |
| CVE-2026-74365 | suse_vex | SUSE CVE CVE-2026-74365 | known affected: 199 known not affected: 197 | 2026-10-08T17:03:26+00:00 | Vulnerability · Source |
| CVE-2026-74376 | suse_vex | SUSE CVE CVE-2026-74376 | known affected: 279 known not affected: 117 | 2026-10-08T17:03:24+00:00 | Vulnerability · Source |
| CVE-2026-74377 | suse_vex | SUSE CVE CVE-2026-74377 | known affected: 608 known not affected: 4 recommended: 340 | 2026-10-08T17:03:22+00:00 | Vulnerability · Source |
| CVE-2026-74378 | suse_vex | SUSE CVE CVE-2026-74378 | known affected: 608 known not affected: 4 recommended: 340 | 2026-10-08T17:03:20+00:00 | Vulnerability · Source |
| CVE-2026-74384 | suse_vex | SUSE CVE CVE-2026-74384 | known affected: 392 known not affected: 6 | 2026-10-08T17:03:18+00:00 | Vulnerability · Source |
| CVE-2026-74385 | suse_vex | SUSE CVE CVE-2026-74385 | known affected: 157 known not affected: 239 | 2026-10-08T17:03:16+00:00 | Vulnerability · Source |
| CVE-2026-74386 | suse_vex | SUSE CVE CVE-2026-74386 | known affected: 392 known not affected: 6 | 2026-10-08T17:03:14+00:00 | Vulnerability · Source |
| CVE-2026-74389 | suse_vex | SUSE CVE CVE-2026-74389 | known affected: 338 known not affected: 58 | 2026-10-08T17:03:11+00:00 | Vulnerability · Source |
| CVE-2026-74390 | suse_vex | SUSE CVE CVE-2026-74390 | known affected: 461 known not affected: 236 recommended: 317 | 2026-10-08T17:03:08+00:00 | Vulnerability · Source |
| CVE-2026-74391 | suse_vex | SUSE CVE CVE-2026-74391 | known affected: 257 known not affected: 139 | 2026-10-08T17:03:06+00:00 | Vulnerability · Source |
| CVE-2026-74398 | suse_vex | SUSE CVE CVE-2026-74398 | known affected: 326 known not affected: 93 | 2026-10-08T17:03:01+00:00 | Vulnerability · Source |