VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306076 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-74597 | suse_vex | SUSE CVE CVE-2026-74597 | known affected: 396 | 2026-10-08T17:01:55+00:00 | Vulnerability · Source |
| CVE-2026-74600 | suse_vex | SUSE CVE CVE-2026-74600 | known affected: 155 known not affected: 239 | 2026-10-08T17:01:53+00:00 | Vulnerability · Source |
| CVE-2026-74601 | suse_vex | SUSE CVE CVE-2026-74601 | known affected: 390 known not affected: 6 | 2026-10-08T17:01:51+00:00 | Vulnerability · Source |
| CVE-2026-74603 | suse_vex | SUSE CVE CVE-2026-74603 | known affected: 155 known not affected: 239 | 2026-10-08T17:01:49+00:00 | Vulnerability · Source |
| CVE-2026-74609 | suse_vex | SUSE CVE CVE-2026-74609 | known affected: 392 known not affected: 4 | 2026-10-08T17:01:46+00:00 | Vulnerability · Source |
| CVE-2026-74625 | suse_vex | SUSE CVE CVE-2026-74625 | known affected: 301 known not affected: 93 | 2026-10-08T17:01:44+00:00 | Vulnerability · Source |
| CVE-2026-74630 | suse_vex | SUSE CVE CVE-2026-74630 | known affected: 355 known not affected: 41 | 2026-10-08T17:01:42+00:00 | Vulnerability · Source |
| CVE-2026-74631 | suse_vex | SUSE CVE CVE-2026-74631 | known affected: 293 known not affected: 101 | 2026-10-08T17:01:40+00:00 | Vulnerability · Source |
| CVE-2026-74632 | suse_vex | SUSE CVE CVE-2026-74632 | known affected: 205 known not affected: 189 | 2026-10-08T17:01:38+00:00 | Vulnerability · Source |
| CVE-2026-74636 | suse_vex | SUSE CVE CVE-2026-74636 | known affected: 251 known not affected: 143 | 2026-10-08T17:01:36+00:00 | Vulnerability · Source |
| CVE-2026-74637 | suse_vex | SUSE CVE CVE-2026-74637 | known affected: 394 | 2026-10-08T17:01:34+00:00 | Vulnerability · Source |
| CVE-2026-74638 | suse_vex | SUSE CVE CVE-2026-74638 | known affected: 155 known not affected: 239 | 2026-10-08T17:01:31+00:00 | Vulnerability · Source |
| CVE-2026-74659 | suse_vex | SUSE CVE CVE-2026-74659 | known affected: 251 known not affected: 143 | 2026-10-08T17:01:29+00:00 | Vulnerability · Source |
| CVE-2026-74660 | suse_vex | SUSE CVE CVE-2026-74660 | known affected: 390 known not affected: 6 | 2026-10-08T17:01:27+00:00 | Vulnerability · Source |
| CVE-2026-74663 | suse_vex | SUSE CVE CVE-2026-74663 | known affected: 396 | 2026-10-08T17:01:24+00:00 | Vulnerability · Source |
| CVE-2026-74666 | suse_vex | SUSE CVE CVE-2026-74666 | known affected: 390 known not affected: 4 | 2026-10-08T17:01:21+00:00 | Vulnerability · Source |
| CVE-2026-74667 | suse_vex | SUSE CVE CVE-2026-74667 | known affected: 390 known not affected: 6 | 2026-10-08T17:01:20+00:00 | Vulnerability · Source |
| CVE-2026-74669 | suse_vex | SUSE CVE CVE-2026-74669 | known affected: 532 known not affected: 4 recommended: 467 | 2026-10-08T17:01:18+00:00 | Vulnerability · Source |
| CVE-2026-74671 | suse_vex | SUSE CVE CVE-2026-74671 | known affected: 392 known not affected: 4 | 2026-10-08T17:01:16+00:00 | Vulnerability · Source |
| CVE-2026-74684 | suse_vex | SUSE CVE CVE-2026-74684 | known affected: 68 known not affected: 89 | 2026-10-08T17:01:15+00:00 | Vulnerability · Source |
| CVE-2026-74688 | suse_vex | SUSE CVE CVE-2026-74688 | known affected: 274 known not affected: 143 | 2026-10-08T17:01:13+00:00 | Vulnerability · Source |
| CVE-2026-74689 | suse_vex | SUSE CVE CVE-2026-74689 | known affected: 396 | 2026-10-08T17:01:11+00:00 | Vulnerability · Source |
| CVE-2026-74692 | suse_vex | SUSE CVE CVE-2026-74692 | known affected: 710 known not affected: 6 recommended: 107 | 2026-10-08T17:01:09+00:00 | Vulnerability · Source |
| CVE-2026-74695 | suse_vex | SUSE CVE CVE-2026-74695 | known affected: 485 known not affected: 93 recommended: 424 | 2026-10-08T17:01:07+00:00 | Vulnerability · Source |
| CVE-2026-74696 | suse_vex | SUSE CVE CVE-2026-74696 | known affected: 251 known not affected: 143 | 2026-10-08T17:01:05+00:00 | Vulnerability · Source |
| CVE-2026-74697 | suse_vex | SUSE CVE CVE-2026-74697 | known affected: 301 known not affected: 93 | 2026-10-08T17:01:03+00:00 | Vulnerability · Source |
| CVE-2026-74700 | suse_vex | SUSE CVE CVE-2026-74700 | known affected: 301 known not affected: 93 | 2026-10-08T17:01:01+00:00 | Vulnerability · Source |
| CVE-2026-74701 | suse_vex | SUSE CVE CVE-2026-74701 | known affected: 390 known not affected: 6 | 2026-10-08T17:01:00+00:00 | Vulnerability · Source |
| CVE-2026-74710 | suse_vex | SUSE CVE CVE-2026-74710 | known affected: 155 known not affected: 239 | 2026-10-08T17:00:58+00:00 | Vulnerability · Source |
| CVE-2026-74713 | suse_vex | SUSE CVE CVE-2026-74713 | known affected: 251 known not affected: 143 | 2026-10-08T17:00:56+00:00 | Vulnerability · Source |
| CVE-2026-74718 | suse_vex | SUSE CVE CVE-2026-74718 | known affected: 155 known not affected: 239 | 2026-10-08T17:00:54+00:00 | Vulnerability · Source |
| CVE-2026-74725 | suse_vex | SUSE CVE CVE-2026-74725 | known affected: 390 known not affected: 4 | 2026-10-08T17:00:53+00:00 | Vulnerability · Source |