VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305480 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-81871 | suse_vex | SUSE CVE CVE-2026-81871 | known affected: 157 recommended: 26 | 2026-10-05T16:33:26+00:00 | Vulnerability · Source |
| CVE-2026-81872 | suse_vex | SUSE CVE CVE-2026-81872 | known affected: 304 known not affected: 15 recommended: 26 | 2026-10-05T16:33:23+00:00 | Vulnerability · Source |
| CVE-2026-85185 | suse_vex | SUSE CVE CVE-2026-85185 | recommended: 6 | 2026-10-05T16:33:10+00:00 | Vulnerability · Source |
| CVE-2026-85515 | suse_vex | SUSE CVE CVE-2026-85515 | known affected: 134 | 2026-10-05T16:33:08+00:00 | Vulnerability · Source |
| CVE-2026-85526 | suse_vex | SUSE CVE CVE-2026-85526 | recommended: 6 | 2026-10-05T16:33:06+00:00 | Vulnerability · Source |
| CVE-2026-85731 | suse_vex | SUSE CVE CVE-2026-85731 | known affected: 12 known not affected: 23 recommended: 49 | 2026-10-05T16:33:03+00:00 | Vulnerability · Source |
| CVE-2026-85732 | suse_vex | SUSE CVE CVE-2026-85732 | known affected: 12 known not affected: 12 recommended: 67 | 2026-10-05T16:33:00+00:00 | Vulnerability · Source |
| CVE-2026-86145 | suse_vex | SUSE CVE CVE-2026-86145 | known affected: 394 known not affected: 391 recommended: 137 | 2026-10-05T16:32:57+00:00 | Vulnerability · Source |
| CVE-2026-86420 | suse_vex | SUSE CVE CVE-2026-86420 | known affected: 274 known not affected: 8 recommended: 108 | 2026-10-05T16:32:54+00:00 | Vulnerability · Source |
| CVE-2026-89970 | redhat_vex | kernel: nvmet-auth: Synchronize timeout work during SQ teardown | known affected: 185 known not affected: 90 | 2026-10-05T16:32:21+00:00 | Vulnerability · Source |
| CVE-2026-88922 | suse_vex | SUSE CVE CVE-2026-88922 | known affected: 108 recommended: 12 | 2026-10-05T16:30:56+00:00 | Vulnerability · Source |
| CVE-2026-89156 | suse_vex | SUSE CVE CVE-2026-89156 | known affected: 394 known not affected: 391 recommended: 137 | 2026-10-05T16:30:53+00:00 | Vulnerability · Source |
| CVE-2026-89157 | suse_vex | SUSE CVE CVE-2026-89157 | known affected: 466 known not affected: 319 recommended: 137 | 2026-10-05T16:30:50+00:00 | Vulnerability · Source |
| CVE-2026-89158 | suse_vex | SUSE CVE CVE-2026-89158 | known affected: 466 known not affected: 319 recommended: 137 | 2026-10-05T16:30:47+00:00 | Vulnerability · Source |
| CVE-2026-89160 | suse_vex | SUSE CVE CVE-2026-89160 | known affected: 466 known not affected: 319 recommended: 137 | 2026-10-05T16:30:44+00:00 | Vulnerability · Source |
| CVE-2026-89161 | suse_vex | SUSE CVE CVE-2026-89161 | known affected: 394 known not affected: 391 recommended: 137 | 2026-10-05T16:30:42+00:00 | Vulnerability · Source |
| CVE-2026-89793 | suse_vex | SUSE CVE CVE-2026-89793 | known affected: 341 known not affected: 6 recommended: 4 | 2026-10-05T16:30:37+00:00 | Vulnerability · Source |
| CVE-2026-89968 | suse_vex | SUSE CVE CVE-2026-89968 | known affected: 95 known not affected: 6 recommended: 4 | 2026-10-05T16:30:34+00:00 | Vulnerability · Source |
| CVE-2026-90947 | suse_vex | SUSE CVE CVE-2026-90947 | recommended: 37 | 2026-10-05T16:30:28+00:00 | Vulnerability · Source |
| CVE-2026-90948 | suse_vex | SUSE CVE CVE-2026-90948 | recommended: 46 | 2026-10-05T16:30:26+00:00 | Vulnerability · Source |
| CVE-2026-92248 | suse_vex | SUSE CVE CVE-2026-92248 | recommended: 46 | 2026-10-05T16:30:24+00:00 | Vulnerability · Source |
| CVE-2026-92925 | suse_vex | SUSE CVE CVE-2026-92925 | known affected: 6 known not affected: 19 recommended: 38 | 2026-10-05T16:30:21+00:00 | Vulnerability · Source |
| CVE-2026-93599 | suse_vex | SUSE CVE CVE-2026-93599 | known affected: 158 known not affected: 956 recommended: 10 | 2026-10-05T16:30:18+00:00 | Vulnerability · Source |
| CVE-2026-93600 | suse_vex | SUSE CVE CVE-2026-93600 | known affected: 158 known not affected: 956 recommended: 6 | 2026-10-05T16:30:16+00:00 | Vulnerability · Source |
| CVE-2026-93601 | suse_vex | SUSE CVE CVE-2026-93601 | known affected: 158 known not affected: 956 recommended: 6 | 2026-10-05T16:30:14+00:00 | Vulnerability · Source |
| CVE-2026-93602 | suse_vex | SUSE CVE CVE-2026-93602 | known affected: 158 known not affected: 956 recommended: 6 | 2026-10-05T16:30:12+00:00 | Vulnerability · Source |
| CVE-2026-95394 | suse_vex | SUSE CVE CVE-2026-95394 | known affected: 50 known not affected: 207 recommended: 6 | 2026-10-05T16:29:24+00:00 | Vulnerability · Source |
| CVE-2026-96512 | suse_vex | SUSE CVE CVE-2026-96512 | known affected: 143 recommended: 3 | 2026-10-05T16:29:22+00:00 | Vulnerability · Source |
| CVE-2026-97185 | suse_vex | SUSE CVE CVE-2026-97185 | known affected: 26 recommended: 2 | 2026-10-05T16:29:20+00:00 | Vulnerability · Source |
| CVE-2026-97508 | suse_vex | SUSE CVE CVE-2026-97508 | known affected: 300 known not affected: 47 | 2026-10-05T16:29:18+00:00 | Vulnerability · Source |
| CVE-2026-97873 | suse_vex | SUSE CVE CVE-2026-97873 | known affected: 134 | 2026-10-05T16:29:15+00:00 | Vulnerability · Source |
| CVE-2026-97876 | suse_vex | SUSE CVE CVE-2026-97876 | known affected: 121 known not affected: 260 | 2026-10-05T16:29:12+00:00 | Vulnerability · Source |
| CVE-2026-98078 | suse_vex | SUSE CVE CVE-2026-98078 | known affected: 343 known not affected: 4 | 2026-10-05T16:29:09+00:00 | Vulnerability · Source |
| CVE-2026-104843 | suse_vex | SUSE CVE CVE-2026-104843 | known not affected: 9 | 2026-10-05T16:28:54+00:00 | Vulnerability · Source |
| CVE-2026-104844 | suse_vex | SUSE CVE CVE-2026-104844 | known affected: 251 known not affected: 328 | 2026-10-05T16:28:52+00:00 | Vulnerability · Source |
| CVE-2026-104845 | suse_vex | SUSE CVE CVE-2026-104845 | No product status | 2026-10-05T16:28:50+00:00 | Vulnerability · Source |
| CVE-2026-104846 | suse_vex | SUSE CVE CVE-2026-104846 | No product status | 2026-10-05T16:28:48+00:00 | Vulnerability · Source |
| CVE-2026-104848 | suse_vex | SUSE CVE CVE-2026-104848 | known affected: 1 | 2026-10-05T16:28:46+00:00 | Vulnerability · Source |
| CVE-2026-104849 | suse_vex | SUSE CVE CVE-2026-104849 | known affected: 1 | 2026-10-05T16:28:44+00:00 | Vulnerability · Source |
| CVE-2026-104851 | suse_vex | SUSE CVE CVE-2026-104851 | No product status | 2026-10-05T16:28:42+00:00 | Vulnerability · Source |
| CVE-2026-104855 | suse_vex | SUSE CVE CVE-2026-104855 | known affected: 21 | 2026-10-05T16:28:40+00:00 | Vulnerability · Source |
| CVE-2026-104861 | suse_vex | SUSE CVE CVE-2026-104861 | known affected: 107 known not affected: 230 | 2026-10-05T16:28:38+00:00 | Vulnerability · Source |
| CVE-2026-104873 | suse_vex | SUSE CVE CVE-2026-104873 | No product status | 2026-10-05T16:28:35+00:00 | Vulnerability · Source |
| CVE-2026-104874 | suse_vex | SUSE CVE CVE-2026-104874 | known not affected: 92 | 2026-10-05T16:28:32+00:00 | Vulnerability · Source |
| CVE-2026-104982 | suse_vex | SUSE CVE CVE-2026-104982 | No product status | 2026-10-05T16:28:30+00:00 | Vulnerability · Source |
| CVE-2026-104983 | suse_vex | SUSE CVE CVE-2026-104983 | No product status | 2026-10-05T16:28:28+00:00 | Vulnerability · Source |
| CVE-2026-104994 | suse_vex | SUSE CVE CVE-2026-104994 | No product status | 2026-10-05T16:28:26+00:00 | Vulnerability · Source |
| CVE-2026-105083 | suse_vex | SUSE CVE CVE-2026-105083 | known affected: 368 known not affected: 8 | 2026-10-05T16:28:25+00:00 | Vulnerability · Source |
| CVE-2026-105245 | suse_vex | SUSE CVE CVE-2026-105245 | No product status | 2026-10-05T16:28:23+00:00 | Vulnerability · Source |
| CVE-2026-80274 | redhat_vex | bind: BIND: Denial of Service via crafted DNSSEC reply | fixed: 231 known affected: 47 known not affected: 12 | 2026-10-05T16:26:25+00:00 | Vulnerability · Source |