VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
77072 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-1372 | suse_vex | SUSE CVE CVE-2025-1372 | known affected: 330 known not affected: 216 recommended: 282 | 2026-10-03T00:58:37+00:00 | Vulnerability · Source |
| CVE-2025-4035 | suse_vex | SUSE CVE CVE-2025-4035 | known affected: 454 recommended: 3 | 2026-10-03T00:58:34+00:00 | Vulnerability · Source |
| CVE-2025-4673 | suse_vex | SUSE CVE CVE-2025-4673 | known affected: 72 known not affected: 64 recommended: 277 | 2026-10-03T00:58:30+00:00 | Vulnerability · Source |
| CVE-2025-37963 | suse_vex | SUSE CVE CVE-2025-37963 | known affected: 339 known not affected: 252 recommended: 633 | 2026-10-03T00:58:12+00:00 | Vulnerability · Source |
| CVE-2025-38377 | suse_vex | SUSE CVE CVE-2025-38377 | known affected: 517 known not affected: 204 recommended: 472 | 2026-10-03T00:58:02+00:00 | Vulnerability · Source |
| CVE-2025-38733 | suse_vex | SUSE CVE CVE-2025-38733 | known affected: 74 known not affected: 475 recommended: 154 | 2026-10-03T00:57:54+00:00 | Vulnerability · Source |
| CVE-2025-39945 | suse_vex | SUSE CVE CVE-2025-39945 | known affected: 356 known not affected: 199 recommended: 697 | 2026-10-03T00:57:48+00:00 | Vulnerability · Source |
| CVE-2025-40052 | suse_vex | SUSE CVE CVE-2025-40052 | known affected: 463 known not affected: 323 recommended: 470 | 2026-10-03T00:57:44+00:00 | Vulnerability · Source |
| CVE-2025-40192 | suse_vex | SUSE CVE CVE-2025-40192 | known affected: 491 known not affected: 388 recommended: 163 | 2026-10-03T00:57:41+00:00 | Vulnerability · Source |
| CVE-2025-68358 | suse_vex | SUSE CVE CVE-2025-68358 | known affected: 557 known not affected: 6 recommended: 151 | 2026-10-03T00:57:29+00:00 | Vulnerability · Source |
| CVE-2025-69646 | suse_vex | SUSE CVE CVE-2025-69646 | known affected: 216 recommended: 7 | 2026-10-03T00:57:25+00:00 | Vulnerability · Source |
| CVE-2025-71093 | suse_vex | SUSE CVE CVE-2025-71093 | known affected: 710 recommended: 326 | 2026-10-03T00:57:21+00:00 | Vulnerability · Source |
| CVE-2026-6103 | suse_vex | SUSE CVE CVE-2026-6103 | known affected: 2235 recommended: 47 | 2026-10-03T00:57:15+00:00 | Vulnerability · Source |
| CVE-2026-7260 | suse_vex | SUSE CVE CVE-2026-7260 | known affected: 720 recommended: 1609 | 2026-10-03T00:57:10+00:00 | Vulnerability · Source |
| CVE-2026-15310 | suse_vex | SUSE CVE CVE-2026-15310 | known affected: 866 known not affected: 79 recommended: 165 | 2026-10-03T00:56:59+00:00 | Vulnerability · Source |
| CVE-2026-17084 | suse_vex | SUSE CVE CVE-2026-17084 | known affected: 956 recommended: 215 | 2026-10-03T00:56:54+00:00 | Vulnerability · Source |
| CVE-2026-18401 | suse_vex | SUSE CVE CVE-2026-18401 | known not affected: 17 recommended: 77 | 2026-10-03T00:56:46+00:00 | Vulnerability · Source |
| CVE-2026-19032 | suse_vex | SUSE CVE CVE-2026-19032 | known affected: 21 recommended: 77 | 2026-10-03T00:56:44+00:00 | Vulnerability · Source |
| CVE-2026-19672 | suse_vex | SUSE CVE CVE-2026-19672 | known affected: 980 recommended: 171 | 2026-10-03T00:56:40+00:00 | Vulnerability · Source |
| CVE-2026-19694 | suse_vex | SUSE CVE CVE-2026-19694 | known affected: 12 known not affected: 220 recommended: 30 | 2026-10-03T00:56:37+00:00 | Vulnerability · Source |
| CVE-2026-19695 | suse_vex | SUSE CVE CVE-2026-19695 | known affected: 13 known not affected: 207 recommended: 30 | 2026-10-03T00:56:35+00:00 | Vulnerability · Source |
| CVE-2026-19696 | suse_vex | SUSE CVE CVE-2026-19696 | known affected: 12 known not affected: 220 recommended: 30 | 2026-10-03T00:56:32+00:00 | Vulnerability · Source |
| CVE-2026-19880 | suse_vex | SUSE CVE CVE-2026-19880 | recommended: 4 | 2026-10-03T00:56:29+00:00 | Vulnerability · Source |
| CVE-2026-25727 | suse_vex | SUSE CVE CVE-2026-25727 | known affected: 545 known not affected: 552 recommended: 325 | 2026-10-03T00:56:18+00:00 | Vulnerability · Source |
| CVE-2026-31418 | suse_vex | SUSE CVE CVE-2026-31418 | known affected: 648 known not affected: 125 recommended: 252 | 2026-10-03T00:56:14+00:00 | Vulnerability · Source |
| CVE-2026-31531 | suse_vex | SUSE CVE CVE-2026-31531 | known affected: 648 known not affected: 125 recommended: 252 | 2026-10-03T00:56:11+00:00 | Vulnerability · Source |
| CVE-2026-33412 | suse_vex | SUSE CVE CVE-2026-33412 | known affected: 448 recommended: 214 | 2026-10-03T00:56:05+00:00 | Vulnerability · Source |
| CVE-2026-33515 | suse_vex | SUSE CVE CVE-2026-33515 | known affected: 49 recommended: 1 | 2026-10-03T00:56:03+00:00 | Vulnerability · Source |
| CVE-2026-35189 | suse_vex | SUSE CVE CVE-2026-35189 | known affected: 435 known not affected: 105 recommended: 65 | 2026-10-03T00:55:59+00:00 | Vulnerability · Source |
| CVE-2026-41080 | suse_vex | SUSE CVE CVE-2026-41080 | known affected: 176 known not affected: 395 recommended: 15 | 2026-10-03T00:55:55+00:00 | Vulnerability · Source |
| CVE-2026-41676 | suse_vex | SUSE CVE CVE-2026-41676 | known affected: 737 known not affected: 983 recommended: 441 | 2026-10-03T00:55:52+00:00 | Vulnerability · Source |
| CVE-2026-41677 | suse_vex | SUSE CVE CVE-2026-41677 | known affected: 1040 known not affected: 499 recommended: 211 | 2026-10-03T00:55:50+00:00 | Vulnerability · Source |
| CVE-2026-41678 | suse_vex | SUSE CVE CVE-2026-41678 | known affected: 1037 known not affected: 501 recommended: 216 | 2026-10-03T00:55:47+00:00 | Vulnerability · Source |
| CVE-2026-41681 | suse_vex | SUSE CVE CVE-2026-41681 | known affected: 1021 known not affected: 969 recommended: 209 | 2026-10-03T00:55:44+00:00 | Vulnerability · Source |
| CVE-2026-41898 | suse_vex | SUSE CVE CVE-2026-41898 | known affected: 1116 known not affected: 874 recommended: 216 | 2026-10-03T00:55:42+00:00 | Vulnerability · Source |
| CVE-2026-42151 | suse_vex | SUSE CVE CVE-2026-42151 | known affected: 3 recommended: 109 | 2026-10-03T00:55:40+00:00 | Vulnerability · Source |
| CVE-2026-42154 | suse_vex | SUSE CVE CVE-2026-42154 | known affected: 3 recommended: 109 | 2026-10-03T00:55:38+00:00 | Vulnerability · Source |
| CVE-2026-42327 | suse_vex | SUSE CVE CVE-2026-42327 | known affected: 1113 known not affected: 874 recommended: 227 | 2026-10-03T00:55:35+00:00 | Vulnerability · Source |
| CVE-2026-43116 | suse_vex | SUSE CVE CVE-2026-43116 | known affected: 697 recommended: 393 | 2026-10-03T00:55:32+00:00 | Vulnerability · Source |
| CVE-2026-43163 | suse_vex | SUSE CVE CVE-2026-43163 | known affected: 747 known not affected: 4 recommended: 368 | 2026-10-03T00:55:28+00:00 | Vulnerability · Source |
| CVE-2026-43239 | suse_vex | SUSE CVE CVE-2026-43239 | known affected: 530 known not affected: 175 recommended: 252 | 2026-10-03T00:55:24+00:00 | Vulnerability · Source |
| CVE-2026-43271 | suse_vex | SUSE CVE CVE-2026-43271 | known affected: 747 known not affected: 4 recommended: 252 | 2026-10-03T00:55:21+00:00 | Vulnerability · Source |
| CVE-2026-43299 | suse_vex | SUSE CVE CVE-2026-43299 | known affected: 385 known not affected: 4 recommended: 145 | 2026-10-03T00:55:18+00:00 | Vulnerability · Source |
| CVE-2026-43331 | suse_vex | SUSE CVE CVE-2026-43331 | known affected: 2 known not affected: 370 recommended: 145 | 2026-10-03T00:55:16+00:00 | Vulnerability · Source |
| CVE-2026-43355 | suse_vex | SUSE CVE CVE-2026-43355 | known affected: 383 known not affected: 6 recommended: 145 | 2026-10-03T00:55:13+00:00 | Vulnerability · Source |
| CVE-2026-43363 | suse_vex | SUSE CVE CVE-2026-43363 | known affected: 697 recommended: 275 | 2026-10-03T00:55:11+00:00 | Vulnerability · Source |
| CVE-2026-43448 | suse_vex | SUSE CVE CVE-2026-43448 | known affected: 638 known not affected: 125 recommended: 228 | 2026-10-03T00:55:07+00:00 | Vulnerability · Source |
| CVE-2026-44662 | suse_vex | SUSE CVE CVE-2026-44662 | known affected: 1116 known not affected: 874 recommended: 218 | 2026-10-03T00:55:05+00:00 | Vulnerability · Source |
| CVE-2026-45784 | suse_vex | SUSE CVE CVE-2026-45784 | known affected: 1001 known not affected: 978 recommended: 223 | 2026-10-03T00:55:01+00:00 | Vulnerability · Source |
| CVE-2026-45836 | suse_vex | SUSE CVE CVE-2026-45836 | known affected: 383 known not affected: 4 recommended: 4 | 2026-10-03T00:54:59+00:00 | Vulnerability · Source |