VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
309534 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-74733 | suse_vex | SUSE CVE CVE-2026-74733 | known affected: 227 known not affected: 131 | 2026-10-17T16:27:53+00:00 | Vulnerability · Source |
| CVE-2026-74736 | suse_vex | SUSE CVE CVE-2026-74736 | known affected: 115 known not affected: 239 | 2026-10-17T16:27:52+00:00 | Vulnerability · Source |
| CVE-2026-74745 | suse_vex | SUSE CVE CVE-2026-74745 | known affected: 478 known not affected: 324 | 2026-10-17T16:27:49+00:00 | Vulnerability · Source |
| CVE-2026-74746 | suse_vex | SUSE CVE CVE-2026-74746 | known affected: 261 known not affected: 93 recommended: 20 | 2026-10-17T16:27:48+00:00 | Vulnerability · Source |
| CVE-2026-74747 | suse_vex | SUSE CVE CVE-2026-74747 | known affected: 354 | 2026-10-17T16:27:46+00:00 | Vulnerability · Source |
| CVE-2026-74748 | suse_vex | SUSE CVE CVE-2026-74748 | known affected: 350 known not affected: 4 | 2026-10-17T16:27:45+00:00 | Vulnerability · Source |
| CVE-2026-74753 | suse_vex | SUSE CVE CVE-2026-74753 | known affected: 13 known not affected: 341 recommended: 102 | 2026-10-17T16:27:43+00:00 | Vulnerability · Source |
| CVE-2026-80522 | suse_vex | SUSE CVE CVE-2026-80522 | known affected: 0 known not affected: 353 recommended: 83 | 2026-10-17T16:27:40+00:00 | Vulnerability · Source |
| CVE-2026-80527 | suse_vex | SUSE CVE CVE-2026-80527 | known affected: 261 known not affected: 93 | 2026-10-17T16:27:38+00:00 | Vulnerability · Source |
| CVE-2026-80528 | suse_vex | SUSE CVE CVE-2026-80528 | known affected: 348 known not affected: 6 | 2026-10-17T16:27:37+00:00 | Vulnerability · Source |
| CVE-2026-80530 | suse_vex | SUSE CVE CVE-2026-80530 | known affected: 32 known not affected: 324 recommended: 203 | 2026-10-17T16:27:35+00:00 | Vulnerability · Source |
| CVE-2026-80536 | suse_vex | SUSE CVE CVE-2026-80536 | known affected: 354 | 2026-10-17T16:27:34+00:00 | Vulnerability · Source |
| CVE-2026-80544 | suse_vex | SUSE CVE CVE-2026-80544 | known affected: 0 known not affected: 353 | 2026-10-17T16:27:32+00:00 | Vulnerability · Source |
| CVE-2026-80547 | suse_vex | SUSE CVE CVE-2026-80547 | known affected: 237 known not affected: 117 | 2026-10-17T16:27:31+00:00 | Vulnerability · Source |
| CVE-2026-80548 | suse_vex | SUSE CVE CVE-2026-80548 | known affected: 261 known not affected: 93 | 2026-10-17T16:27:29+00:00 | Vulnerability · Source |
| CVE-2026-80549 | suse_vex | SUSE CVE CVE-2026-80549 | known affected: 169 known not affected: 185 | 2026-10-17T16:27:28+00:00 | Vulnerability · Source |
| CVE-2026-80550 | suse_vex | SUSE CVE CVE-2026-80550 | known affected: 348 known not affected: 6 | 2026-10-17T16:27:26+00:00 | Vulnerability · Source |
| CVE-2026-80551 | suse_vex | SUSE CVE CVE-2026-80551 | known affected: 261 known not affected: 93 | 2026-10-17T16:27:25+00:00 | Vulnerability · Source |
| CVE-2026-80552 | suse_vex | SUSE CVE CVE-2026-80552 | known affected: 261 known not affected: 93 | 2026-10-17T16:27:23+00:00 | Vulnerability · Source |
| CVE-2026-80553 | suse_vex | SUSE CVE CVE-2026-80553 | known affected: 348 known not affected: 6 | 2026-10-17T16:27:21+00:00 | Vulnerability · Source |
| CVE-2026-80554 | suse_vex | SUSE CVE CVE-2026-80554 | known affected: 348 known not affected: 6 | 2026-10-17T16:27:19+00:00 | Vulnerability · Source |
| CVE-2026-80572 | suse_vex | SUSE CVE CVE-2026-80572 | known affected: 348 known not affected: 6 | 2026-10-17T16:27:12+00:00 | Vulnerability · Source |
| CVE-2026-80574 | suse_vex | SUSE CVE CVE-2026-80574 | known affected: 605 known not affected: 89 recommended: 23 | 2026-10-17T16:27:11+00:00 | Vulnerability · Source |
| CVE-2026-80576 | suse_vex | SUSE CVE CVE-2026-80576 | known affected: 282 known not affected: 72 | 2026-10-17T16:27:09+00:00 | Vulnerability · Source |
| CVE-2026-80579 | suse_vex | SUSE CVE CVE-2026-80579 | known affected: 261 known not affected: 93 | 2026-10-17T16:27:08+00:00 | Vulnerability · Source |
| CVE-2026-80584 | suse_vex | SUSE CVE CVE-2026-80584 | known affected: 354 | 2026-10-17T16:27:06+00:00 | Vulnerability · Source |
| CVE-2026-80585 | suse_vex | SUSE CVE CVE-2026-80585 | known affected: 543 known not affected: 239 recommended: 83 | 2026-10-17T16:27:04+00:00 | Vulnerability · Source |
| CVE-2026-80587 | suse_vex | SUSE CVE CVE-2026-80587 | known affected: 164 known not affected: 190 | 2026-10-17T16:27:02+00:00 | Vulnerability · Source |
| CVE-2026-80588 | suse_vex | SUSE CVE CVE-2026-80588 | known affected: 0 known not affected: 353 | 2026-10-17T16:27:01+00:00 | Vulnerability · Source |
| CVE-2026-80593 | suse_vex | SUSE CVE CVE-2026-80593 | known affected: 213 known not affected: 141 | 2026-10-17T16:26:57+00:00 | Vulnerability · Source |
| CVE-2026-80598 | suse_vex | SUSE CVE CVE-2026-80598 | known affected: 115 known not affected: 239 | 2026-10-17T16:26:56+00:00 | Vulnerability · Source |
| CVE-2026-80599 | suse_vex | SUSE CVE CVE-2026-80599 | known affected: 265 known not affected: 89 | 2026-10-17T16:26:54+00:00 | Vulnerability · Source |
| CVE-2026-80601 | suse_vex | SUSE CVE CVE-2026-80601 | known affected: 0 known not affected: 354 | 2026-10-17T16:26:53+00:00 | Vulnerability · Source |
| CVE-2026-80604 | suse_vex | SUSE CVE CVE-2026-80604 | known affected: 0 known not affected: 353 | 2026-10-17T16:26:51+00:00 | Vulnerability · Source |
| CVE-2026-80606 | suse_vex | SUSE CVE CVE-2026-80606 | known affected: 0 known not affected: 353 | 2026-10-17T16:26:49+00:00 | Vulnerability · Source |
| CVE-2026-80609 | suse_vex | SUSE CVE CVE-2026-80609 | known affected: 483 known not affected: 213 recommended: 168 | 2026-10-17T16:26:48+00:00 | Vulnerability · Source |
| CVE-2026-80615 | suse_vex | SUSE CVE CVE-2026-80615 | known affected: 0 known not affected: 353 | 2026-10-17T16:26:46+00:00 | Vulnerability · Source |
| CVE-2026-80622 | suse_vex | SUSE CVE CVE-2026-80622 | known affected: 269 known not affected: 85 | 2026-10-17T16:26:44+00:00 | Vulnerability · Source |
| CVE-2026-80628 | suse_vex | SUSE CVE CVE-2026-80628 | known affected: 213 known not affected: 13 | 2026-10-17T16:26:43+00:00 | Vulnerability · Source |
| CVE-2026-80630 | suse_vex | SUSE CVE CVE-2026-80630 | known affected: 317 known not affected: 37 | 2026-10-17T16:26:42+00:00 | Vulnerability · Source |
| CVE-2026-80634 | suse_vex | SUSE CVE CVE-2026-80634 | known affected: 0 known not affected: 354 | 2026-10-17T16:26:40+00:00 | Vulnerability · Source |
| CVE-2026-80637 | suse_vex | SUSE CVE CVE-2026-80637 | known affected: 350 known not affected: 4 | 2026-10-17T16:26:39+00:00 | Vulnerability · Source |
| CVE-2026-80653 | suse_vex | SUSE CVE CVE-2026-80653 | known affected: 211 known not affected: 143 | 2026-10-17T16:26:37+00:00 | Vulnerability · Source |
| CVE-2026-80668 | suse_vex | SUSE CVE CVE-2026-80668 | known affected: 141 known not affected: 213 | 2026-10-17T16:26:34+00:00 | Vulnerability · Source |
| CVE-2026-80683 | suse_vex | SUSE CVE CVE-2026-80683 | known affected: 0 known not affected: 353 | 2026-10-17T16:26:31+00:00 | Vulnerability · Source |
| CVE-2026-80684 | suse_vex | SUSE CVE CVE-2026-80684 | known affected: 169 known not affected: 185 | 2026-10-17T16:26:29+00:00 | Vulnerability · Source |
| CVE-2026-80691 | suse_vex | SUSE CVE CVE-2026-80691 | known affected: 115 known not affected: 239 | 2026-10-17T16:26:28+00:00 | Vulnerability · Source |
| CVE-2026-80692 | suse_vex | SUSE CVE CVE-2026-80692 | known affected: 30 known not affected: 323 | 2026-10-17T16:26:26+00:00 | Vulnerability · Source |
| CVE-2026-80706 | suse_vex | SUSE CVE CVE-2026-80706 | known affected: 269 known not affected: 85 | 2026-10-17T16:26:24+00:00 | Vulnerability · Source |
| CVE-2026-80709 | suse_vex | SUSE CVE CVE-2026-80709 | known affected: 169 known not affected: 185 | 2026-10-17T16:26:22+00:00 | Vulnerability · Source |