VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306058 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-74440 | suse_vex | SUSE CVE CVE-2026-74440 | known affected: 110 known not affected: 286 | 2026-10-08T17:02:59+00:00 | Vulnerability · Source |
| CVE-2026-74449 | suse_vex | SUSE CVE CVE-2026-74449 | known affected: 65 known not affected: 362 | 2026-10-08T17:02:57+00:00 | Vulnerability · Source |
| CVE-2026-74450 | suse_vex | SUSE CVE CVE-2026-74450 | known affected: 211 known not affected: 185 | 2026-10-08T17:02:55+00:00 | Vulnerability · Source |
| CVE-2026-74465 | suse_vex | SUSE CVE CVE-2026-74465 | known affected: 253 known not affected: 143 | 2026-10-08T17:02:52+00:00 | Vulnerability · Source |
| CVE-2026-74467 | suse_vex | SUSE CVE CVE-2026-74467 | known affected: 211 known not affected: 185 | 2026-10-08T17:02:50+00:00 | Vulnerability · Source |
| CVE-2026-74469 | suse_vex | SUSE CVE CVE-2026-74469 | known affected: 392 known not affected: 6 recommended: 13 | 2026-10-08T17:02:48+00:00 | Vulnerability · Source |
| CVE-2026-74471 | suse_vex | SUSE CVE CVE-2026-74471 | known affected: 394 known not affected: 4 | 2026-10-08T17:02:46+00:00 | Vulnerability · Source |
| CVE-2026-74473 | suse_vex | SUSE CVE CVE-2026-74473 | known affected: 394 known not affected: 4 | 2026-10-08T17:02:44+00:00 | Vulnerability · Source |
| CVE-2026-74480 | suse_vex | SUSE CVE CVE-2026-74480 | known affected: 392 known not affected: 6 recommended: 116 | 2026-10-08T17:02:42+00:00 | Vulnerability · Source |
| CVE-2026-74485 | suse_vex | SUSE CVE CVE-2026-74485 | known affected: 394 known not affected: 4 | 2026-10-08T17:02:40+00:00 | Vulnerability · Source |
| CVE-2026-74487 | suse_vex | SUSE CVE CVE-2026-74487 | known affected: 390 known not affected: 6 | 2026-10-08T17:02:38+00:00 | Vulnerability · Source |
| CVE-2026-74490 | suse_vex | SUSE CVE CVE-2026-74490 | known affected: 303 known not affected: 93 | 2026-10-08T17:02:33+00:00 | Vulnerability · Source |
| CVE-2026-74492 | suse_vex | SUSE CVE CVE-2026-74492 | known affected: 279 known not affected: 117 | 2026-10-08T17:02:30+00:00 | Vulnerability · Source |
| CVE-2026-74493 | suse_vex | SUSE CVE CVE-2026-74493 | known affected: 303 known not affected: 93 | 2026-10-08T17:02:28+00:00 | Vulnerability · Source |
| CVE-2026-74496 | suse_vex | SUSE CVE CVE-2026-74496 | known affected: 523 known not affected: 4 recommended: 447 | 2026-10-08T17:02:26+00:00 | Vulnerability · Source |
| CVE-2026-74515 | suse_vex | SUSE CVE CVE-2026-74515 | known affected: 211 known not affected: 185 | 2026-10-08T17:02:24+00:00 | Vulnerability · Source |
| CVE-2026-74518 | suse_vex | SUSE CVE CVE-2026-74518 | known affected: 440 known not affected: 143 recommended: 504 | 2026-10-08T17:02:22+00:00 | Vulnerability · Source |
| CVE-2026-74537 | suse_vex | SUSE CVE CVE-2026-74537 | known affected: 525 known not affected: 4 recommended: 447 | 2026-10-08T17:02:19+00:00 | Vulnerability · Source |
| CVE-2026-74538 | suse_vex | SUSE CVE CVE-2026-74538 | known affected: 110 known not affected: 286 | 2026-10-08T17:02:17+00:00 | Vulnerability · Source |
| CVE-2026-74564 | suse_vex | SUSE CVE CVE-2026-74564 | known affected: 303 known not affected: 93 | 2026-10-08T17:02:15+00:00 | Vulnerability · Source |
| CVE-2026-74579 | suse_vex | SUSE CVE CVE-2026-74579 | known affected: 253 known not affected: 143 | 2026-10-08T17:02:13+00:00 | Vulnerability · Source |
| CVE-2026-74580 | suse_vex | SUSE CVE CVE-2026-74580 | known affected: 388 known not affected: 6 | 2026-10-08T17:02:11+00:00 | Vulnerability · Source |
| CVE-2026-74581 | suse_vex | SUSE CVE CVE-2026-74581 | known affected: 440 known not affected: 185 recommended: 454 | 2026-10-08T17:02:09+00:00 | Vulnerability · Source |
| CVE-2026-74582 | suse_vex | SUSE CVE CVE-2026-74582 | known affected: 537 known not affected: 4 recommended: 447 | 2026-10-08T17:02:08+00:00 | Vulnerability · Source |
| CVE-2026-74586 | suse_vex | SUSE CVE CVE-2026-74586 | known affected: 392 known not affected: 4 | 2026-10-08T17:02:06+00:00 | Vulnerability · Source |
| CVE-2026-74588 | suse_vex | SUSE CVE CVE-2026-74588 | known affected: 392 known not affected: 4 | 2026-10-08T17:02:04+00:00 | Vulnerability · Source |
| CVE-2026-74589 | suse_vex | SUSE CVE CVE-2026-74589 | known affected: 390 known not affected: 6 | 2026-10-08T17:02:02+00:00 | Vulnerability · Source |
| CVE-2026-74592 | suse_vex | SUSE CVE CVE-2026-74592 | known affected: 396 | 2026-10-08T17:02:00+00:00 | Vulnerability · Source |
| CVE-2026-74594 | suse_vex | SUSE CVE CVE-2026-74594 | known affected: 251 known not affected: 143 | 2026-10-08T17:01:58+00:00 | Vulnerability · Source |
| CVE-2026-74595 | suse_vex | SUSE CVE CVE-2026-74595 | known affected: 251 known not affected: 143 | 2026-10-08T17:01:56+00:00 | Vulnerability · Source |