VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
81558 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-80679 | suse_vex | SUSE CVE CVE-2026-80679 | known affected: 260 known not affected: 93 | 2026-10-08T16:59:30+00:00 | Vulnerability · Source |
| CVE-2026-80686 | suse_vex | SUSE CVE CVE-2026-80686 | known affected: 114 known not affected: 239 | 2026-10-08T16:59:28+00:00 | Vulnerability · Source |
| CVE-2026-80715 | suse_vex | SUSE CVE CVE-2026-80715 | known affected: 210 known not affected: 143 | 2026-10-08T16:59:25+00:00 | Vulnerability · Source |
| CVE-2026-80722 | suse_vex | SUSE CVE CVE-2026-80722 | first fixed: 96 known affected: 84 known not affected: 269 recommended: 3 | 2026-10-08T16:59:24+00:00 | Vulnerability · Source |
| CVE-2026-80725 | suse_vex | SUSE CVE CVE-2026-80725 | known affected: 114 known not affected: 239 | 2026-10-08T16:59:22+00:00 | Vulnerability · Source |
| CVE-2026-80747 | suse_vex | SUSE CVE CVE-2026-80747 | known affected: 349 known not affected: 4 | 2026-10-08T16:59:20+00:00 | Vulnerability · Source |
| CVE-2026-80756 | suse_vex | SUSE CVE CVE-2026-80756 | known affected: 210 known not affected: 143 | 2026-10-08T16:59:18+00:00 | Vulnerability · Source |
| CVE-2026-80789 | suse_vex | SUSE CVE CVE-2026-80789 | known affected: 347 known not affected: 6 recommended: 4 | 2026-10-08T16:59:16+00:00 | Vulnerability · Source |
| CVE-2026-80793 | suse_vex | SUSE CVE CVE-2026-80793 | known affected: 353 recommended: 4 | 2026-10-08T16:59:14+00:00 | Vulnerability · Source |
| CVE-2026-80836 | suse_vex | SUSE CVE CVE-2026-80836 | known affected: 46 known not affected: 307 recommended: 4 | 2026-10-08T16:59:12+00:00 | Vulnerability · Source |
| CVE-2026-80840 | suse_vex | SUSE CVE CVE-2026-80840 | known affected: 260 known not affected: 93 recommended: 4 | 2026-10-08T16:59:10+00:00 | Vulnerability · Source |
| CVE-2026-80841 | suse_vex | SUSE CVE CVE-2026-80841 | known affected: 349 known not affected: 4 recommended: 4 | 2026-10-08T16:59:09+00:00 | Vulnerability · Source |
| CVE-2026-80842 | suse_vex | SUSE CVE CVE-2026-80842 | known affected: 114 known not affected: 239 recommended: 4 | 2026-10-08T16:59:07+00:00 | Vulnerability · Source |
| CVE-2026-80844 | suse_vex | SUSE CVE CVE-2026-80844 | known affected: 353 recommended: 78 | 2026-10-08T16:59:05+00:00 | Vulnerability · Source |
| CVE-2026-80846 | suse_vex | SUSE CVE CVE-2026-80846 | known affected: 236 known not affected: 117 recommended: 4 | 2026-10-08T16:59:03+00:00 | Vulnerability · Source |
| CVE-2026-80847 | suse_vex | SUSE CVE CVE-2026-80847 | known affected: 353 recommended: 4 | 2026-10-08T16:59:01+00:00 | Vulnerability · Source |
| CVE-2026-80848 | suse_vex | SUSE CVE CVE-2026-80848 | known affected: 236 known not affected: 117 recommended: 4 | 2026-10-08T16:58:59+00:00 | Vulnerability · Source |
| CVE-2026-80852 | suse_vex | SUSE CVE CVE-2026-80852 | known affected: 309 known not affected: 44 recommended: 4 | 2026-10-08T16:58:58+00:00 | Vulnerability · Source |
| CVE-2026-80863 | suse_vex | SUSE CVE CVE-2026-80863 | known affected: 349 known not affected: 4 recommended: 4 | 2026-10-08T16:58:56+00:00 | Vulnerability · Source |
| CVE-2026-80864 | suse_vex | SUSE CVE CVE-2026-80864 | known affected: 349 known not affected: 4 recommended: 4 | 2026-10-08T16:58:54+00:00 | Vulnerability · Source |
| CVE-2026-80865 | suse_vex | SUSE CVE CVE-2026-80865 | known affected: 168 known not affected: 185 | 2026-10-08T16:58:52+00:00 | Vulnerability · Source |
| CVE-2026-80880 | suse_vex | SUSE CVE CVE-2026-80880 | known affected: 198 known not affected: 155 | 2026-10-08T16:58:50+00:00 | Vulnerability · Source |
| CVE-2026-80932 | suse_vex | SUSE CVE CVE-2026-80932 | known affected: 347 known not affected: 6 | 2026-10-08T16:58:48+00:00 | Vulnerability · Source |
| CVE-2026-80976 | suse_vex | SUSE CVE CVE-2026-80976 | known affected: 293 known not affected: 60 recommended: 4 | 2026-10-08T16:58:46+00:00 | Vulnerability · Source |
| CVE-2026-80979 | suse_vex | SUSE CVE CVE-2026-80979 | known affected: 69 known not affected: 284 recommended: 4 | 2026-10-08T16:58:44+00:00 | Vulnerability · Source |
| CVE-2026-80983 | suse_vex | SUSE CVE CVE-2026-80983 | known affected: 210 known not affected: 143 recommended: 4 | 2026-10-08T16:58:41+00:00 | Vulnerability · Source |
| CVE-2026-80984 | suse_vex | SUSE CVE CVE-2026-80984 | known affected: 349 known not affected: 4 | 2026-10-08T16:58:39+00:00 | Vulnerability · Source |
| CVE-2026-81000 | suse_vex | SUSE CVE CVE-2026-81000 | known affected: 347 known not affected: 6 recommended: 78 | 2026-10-08T16:58:37+00:00 | Vulnerability · Source |
| CVE-2026-81001 | suse_vex | SUSE CVE CVE-2026-81001 | known affected: 353 recommended: 4 | 2026-10-08T16:58:35+00:00 | Vulnerability · Source |
| CVE-2026-81563 | suse_vex | SUSE CVE CVE-2026-81563 | known affected: 57 known not affected: 300 recommended: 10 | 2026-10-08T16:58:33+00:00 | Vulnerability · Source |
| CVE-2026-81627 | suse_vex | SUSE CVE CVE-2026-81627 | known affected: 1428 | 2026-10-08T16:58:30+00:00 | Vulnerability · Source |
| CVE-2026-81642 | suse_vex | SUSE CVE CVE-2026-81642 | known affected: 174 recommended: 4 | 2026-10-08T16:58:28+00:00 | Vulnerability · Source |
| CVE-2026-81665 | suse_vex | SUSE CVE CVE-2026-81665 | known affected: 407 recommended: 81 | 2026-10-08T16:58:25+00:00 | Vulnerability · Source |
| CVE-2026-81736 | suse_vex | SUSE CVE CVE-2026-81736 | known affected: 57 known not affected: 300 recommended: 10 | 2026-10-08T16:58:23+00:00 | Vulnerability · Source |
| CVE-2026-81934 | suse_vex | SUSE CVE CVE-2026-81934 | known affected: 8 known not affected: 31 recommended: 23 | 2026-10-08T16:58:19+00:00 | Vulnerability · Source |
| CVE-2026-83530 | suse_vex | SUSE CVE CVE-2026-83530 | known affected: 7 known not affected: 319 | 2026-10-08T16:58:18+00:00 | Vulnerability · Source |
| CVE-2026-84303 | suse_vex | SUSE CVE CVE-2026-84303 | known affected: 1384 known not affected: 398 recommended: 321 | 2026-10-08T16:58:16+00:00 | Vulnerability · Source |
| CVE-2026-84304 | suse_vex | SUSE CVE CVE-2026-84304 | known affected: 1454 known not affected: 319 recommended: 356 | 2026-10-08T16:58:14+00:00 | Vulnerability · Source |
| CVE-2026-85494 | suse_vex | SUSE CVE CVE-2026-85494 | No product status | 2026-10-08T16:58:11+00:00 | Vulnerability · Source |
| CVE-2026-86805 | suse_vex | SUSE CVE CVE-2026-86805 | known affected: 602 recommended: 48 | 2026-10-08T16:58:08+00:00 | Vulnerability · Source |
| CVE-2026-86898 | suse_vex | SUSE CVE CVE-2026-86898 | known affected: 179 | 2026-10-08T16:58:06+00:00 | Vulnerability · Source |
| CVE-2026-88010 | suse_vex | SUSE CVE CVE-2026-88010 | recommended: 1 | 2026-10-08T16:58:03+00:00 | Vulnerability · Source |
| CVE-2026-88384 | suse_vex | SUSE CVE CVE-2026-88384 | known affected: 189 recommended: 18 | 2026-10-08T16:58:00+00:00 | Vulnerability · Source |
| CVE-2026-89092 | suse_vex | SUSE CVE CVE-2026-89092 | known affected: 633 | 2026-10-08T16:57:56+00:00 | Vulnerability · Source |
| CVE-2026-89448 | suse_vex | SUSE CVE CVE-2026-89448 | known affected: 353 recommended: 4 | 2026-10-08T16:57:54+00:00 | Vulnerability · Source |
| CVE-2026-89451 | suse_vex | SUSE CVE CVE-2026-89451 | known affected: 114 known not affected: 239 recommended: 4 | 2026-10-08T16:57:52+00:00 | Vulnerability · Source |
| CVE-2026-89453 | suse_vex | SUSE CVE CVE-2026-89453 | known affected: 67 known not affected: 286 recommended: 4 | 2026-10-08T16:57:49+00:00 | Vulnerability · Source |
| CVE-2026-89477 | suse_vex | SUSE CVE CVE-2026-89477 | known affected: 347 known not affected: 6 recommended: 4 | 2026-10-08T16:57:46+00:00 | Vulnerability · Source |
| CVE-2026-89479 | suse_vex | SUSE CVE CVE-2026-89479 | known affected: 353 recommended: 4 | 2026-10-08T16:57:44+00:00 | Vulnerability · Source |
| CVE-2026-89480 | suse_vex | SUSE CVE CVE-2026-89480 | known affected: 293 known not affected: 60 recommended: 66 | 2026-10-08T16:57:42+00:00 | Vulnerability · Source |