VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-71309 | suse_vex | SUSE CVE CVE-2025-71309 | known affected: 0 known not affected: 385 | 2026-10-16T12:47:05+00:00 | Vulnerability · Source |
| CVE-2026-0716 | suse_vex | SUSE CVE CVE-2026-0716 | known affected: 148 recommended: 219 | 2026-10-16T12:47:03+00:00 | Vulnerability · Source |
| CVE-2026-1539 | suse_vex | SUSE CVE CVE-2026-1539 | known affected: 108 recommended: 219 | 2026-10-16T12:47:01+00:00 | Vulnerability · Source |
| CVE-2026-4631 | suse_vex | SUSE CVE CVE-2026-4631 | known not affected: 39 recommended: 117 | 2026-10-16T12:46:55+00:00 | Vulnerability · Source |
| CVE-2026-4775 | suse_vex | SUSE CVE CVE-2026-4775 | known affected: 468 recommended: 126 | 2026-10-16T12:46:53+00:00 | Vulnerability · Source |
| CVE-2026-12478 | suse_vex | SUSE CVE CVE-2026-12478 | known affected: 198 recommended: 115 | 2026-10-16T12:46:34+00:00 | Vulnerability · Source |
| CVE-2026-14362 | suse_vex | SUSE CVE CVE-2026-14362 | known affected: 366 known not affected: 255 recommended: 1 | 2026-10-16T12:46:27+00:00 | Vulnerability · Source |
| CVE-2026-23471 | suse_vex | SUSE CVE CVE-2026-23471 | known affected: 345 known not affected: 51 | 2026-10-16T12:46:02+00:00 | Vulnerability · Source |
| CVE-2026-25646 | suse_vex | SUSE CVE CVE-2026-25646 | known affected: 514 recommended: 263 | 2026-10-16T12:45:59+00:00 | Vulnerability · Source |
| CVE-2026-28984 | suse_vex | SUSE CVE CVE-2026-28984 | known affected: 195 recommended: 312 | 2026-10-16T12:45:56+00:00 | Vulnerability · Source |
| CVE-2026-31688 | suse_vex | SUSE CVE CVE-2026-31688 | known affected: 409 | 2026-10-16T12:45:52+00:00 | Vulnerability · Source |
| CVE-2026-41603 | suse_vex | SUSE CVE CVE-2026-41603 | known affected: 28 known not affected: 506 recommended: 132 | 2026-10-16T12:45:43+00:00 | Vulnerability · Source |
| CVE-2026-42009 | suse_vex | SUSE CVE CVE-2026-42009 | known affected: 493 recommended: 256 | 2026-10-16T12:45:41+00:00 | Vulnerability · Source |
| CVE-2026-43804 | suse_vex | SUSE CVE CVE-2026-43804 | known affected: 195 recommended: 308 | 2026-10-16T12:45:31+00:00 | Vulnerability · Source |
| CVE-2026-48551 | suse_vex | SUSE CVE CVE-2026-48551 | No product status | 2026-10-16T12:45:23+00:00 | Vulnerability · Source |
| CVE-2026-61837 | suse_vex | SUSE CVE CVE-2026-61837 | known affected: 21 known not affected: 97 | 2026-10-16T12:45:12+00:00 | Vulnerability · Source |
| CVE-2026-64713 | suse_vex | SUSE CVE CVE-2026-64713 | known affected: 160 recommended: 300 | 2026-10-16T12:45:04+00:00 | Vulnerability · Source |
| CVE-2026-64719 | suse_vex | SUSE CVE CVE-2026-64719 | known affected: 160 recommended: 300 | 2026-10-16T12:45:03+00:00 | Vulnerability · Source |
| CVE-2026-64728 | suse_vex | SUSE CVE CVE-2026-64728 | known affected: 160 recommended: 300 | 2026-10-16T12:45:01+00:00 | Vulnerability · Source |
| CVE-2026-64730 | suse_vex | SUSE CVE CVE-2026-64730 | known affected: 160 recommended: 300 | 2026-10-16T12:45:00+00:00 | Vulnerability · Source |
| CVE-2026-64757 | suse_vex | SUSE CVE CVE-2026-64757 | known affected: 160 recommended: 300 | 2026-10-16T12:44:56+00:00 | Vulnerability · Source |
| CVE-2026-64783 | suse_vex | SUSE CVE CVE-2026-64783 | known affected: 160 recommended: 300 | 2026-10-16T12:44:46+00:00 | Vulnerability · Source |
| CVE-2026-66071 | suse_vex | SUSE CVE CVE-2026-66071 | known affected: 118 | 2026-10-16T12:44:28+00:00 | Vulnerability · Source |
| CVE-2026-66078 | suse_vex | SUSE CVE CVE-2026-66078 | known affected: 118 | 2026-10-16T12:44:27+00:00 | Vulnerability · Source |
| CVE-2026-67222 | suse_vex | SUSE CVE CVE-2026-67222 | known affected: 118 | 2026-10-16T12:44:23+00:00 | Vulnerability · Source |
| CVE-2026-67223 | suse_vex | SUSE CVE CVE-2026-67223 | known affected: 118 | 2026-10-16T12:44:22+00:00 | Vulnerability · Source |
| CVE-2026-67236 | suse_vex | SUSE CVE CVE-2026-67236 | known affected: 118 | 2026-10-16T12:44:20+00:00 | Vulnerability · Source |
| CVE-2026-72057 | suse_vex | SUSE CVE CVE-2026-72057 | known affected: 271 known not affected: 91 | 2026-10-16T12:44:12+00:00 | Vulnerability · Source |
| CVE-2026-72096 | suse_vex | SUSE CVE CVE-2026-72096 | known affected: 358 known not affected: 4 | 2026-10-16T12:44:10+00:00 | Vulnerability · Source |
| CVE-2026-72099 | suse_vex | SUSE CVE CVE-2026-72099 | known affected: 245 known not affected: 117 | 2026-10-16T12:44:08+00:00 | Vulnerability · Source |
| CVE-2026-72109 | suse_vex | SUSE CVE CVE-2026-72109 | known affected: 219 known not affected: 143 | 2026-10-16T12:44:06+00:00 | Vulnerability · Source |
| CVE-2026-72170 | suse_vex | SUSE CVE CVE-2026-72170 | known affected: 269 known not affected: 93 | 2026-10-16T12:44:04+00:00 | Vulnerability · Source |
| CVE-2026-72175 | suse_vex | SUSE CVE CVE-2026-72175 | known affected: 29 known not affected: 333 | 2026-10-16T12:44:02+00:00 | Vulnerability · Source |
| CVE-2026-72178 | suse_vex | SUSE CVE CVE-2026-72178 | known affected: 29 known not affected: 333 | 2026-10-16T12:44:00+00:00 | Vulnerability · Source |
| CVE-2026-72364 | suse_vex | SUSE CVE CVE-2026-72364 | known affected: 29 known not affected: 333 | 2026-10-16T12:43:57+00:00 | Vulnerability · Source |
| CVE-2026-80732 | suse_vex | SUSE CVE CVE-2026-80732 | known affected: 353 | 2026-10-16T12:43:47+00:00 | Vulnerability · Source |
| CVE-2026-80767 | suse_vex | SUSE CVE CVE-2026-80767 | known affected: 265 known not affected: 88 recommended: 4 | 2026-10-16T12:43:45+00:00 | Vulnerability · Source |
| CVE-2026-80768 | suse_vex | SUSE CVE CVE-2026-80768 | known affected: 42 known not affected: 311 recommended: 4 | 2026-10-16T12:43:43+00:00 | Vulnerability · Source |
| CVE-2026-80794 | suse_vex | SUSE CVE CVE-2026-80794 | known affected: 265 known not affected: 88 recommended: 4 | 2026-10-16T12:43:42+00:00 | Vulnerability · Source |
| CVE-2026-80795 | suse_vex | SUSE CVE CVE-2026-80795 | known affected: 265 known not affected: 88 recommended: 4 | 2026-10-16T12:43:40+00:00 | Vulnerability · Source |
| CVE-2026-80796 | suse_vex | SUSE CVE CVE-2026-80796 | known affected: 349 known not affected: 4 recommended: 4 | 2026-10-16T12:43:38+00:00 | Vulnerability · Source |
| CVE-2026-80835 | suse_vex | SUSE CVE CVE-2026-80835 | known affected: 29 known not affected: 324 recommended: 4 | 2026-10-16T12:43:36+00:00 | Vulnerability · Source |
| CVE-2026-80935 | suse_vex | SUSE CVE CVE-2026-80935 | known affected: 114 known not affected: 239 recommended: 4 | 2026-10-16T12:43:32+00:00 | Vulnerability · Source |
| CVE-2026-80937 | suse_vex | SUSE CVE CVE-2026-80937 | known affected: 224 known not affected: 129 recommended: 4 | 2026-10-16T12:43:30+00:00 | Vulnerability · Source |
| CVE-2026-80939 | suse_vex | SUSE CVE CVE-2026-80939 | known affected: 29 known not affected: 324 recommended: 4 | 2026-10-16T12:43:28+00:00 | Vulnerability · Source |
| CVE-2026-80948 | suse_vex | SUSE CVE CVE-2026-80948 | known affected: 349 known not affected: 4 recommended: 4 | 2026-10-16T12:43:26+00:00 | Vulnerability · Source |
| CVE-2026-80963 | suse_vex | SUSE CVE CVE-2026-80963 | known affected: 349 known not affected: 4 recommended: 4 | 2026-10-16T12:43:24+00:00 | Vulnerability · Source |
| CVE-2026-84268 | suse_vex | SUSE CVE CVE-2026-84268 | known affected: 84 recommended: 178 | 2026-10-16T12:43:18+00:00 | Vulnerability · Source |
| CVE-2026-89462 | suse_vex | SUSE CVE CVE-2026-89462 | known affected: 324 known not affected: 29 recommended: 4 | 2026-10-16T12:43:10+00:00 | Vulnerability · Source |
| CVE-2026-89465 | suse_vex | SUSE CVE CVE-2026-89465 | known affected: 269 known not affected: 84 recommended: 4 | 2026-10-16T12:43:09+00:00 | Vulnerability · Source |