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-12839 | suse_vex | SUSE CVE CVE-2025-12839 | known affected: 0 known not affected: 190 recommended: 79 | 2026-10-16T01:04:15+00:00 | Vulnerability · Source |
| CVE-2025-12840 | suse_vex | SUSE CVE CVE-2025-12840 | known affected: 0 known not affected: 190 recommended: 79 | 2026-10-16T01:04:13+00:00 | Vulnerability · Source |
| CVE-2025-13013 | suse_vex | SUSE CVE CVE-2025-13013 | known affected: 28 recommended: 186 | 2026-10-16T01:04:11+00:00 | Vulnerability · Source |
| CVE-2025-13017 | suse_vex | SUSE CVE CVE-2025-13017 | known affected: 28 recommended: 186 | 2026-10-16T01:04:09+00:00 | Vulnerability · Source |
| CVE-2025-13018 | suse_vex | SUSE CVE CVE-2025-13018 | known affected: 28 recommended: 186 | 2026-10-16T01:04:08+00:00 | Vulnerability · Source |
| CVE-2025-13020 | suse_vex | SUSE CVE CVE-2025-13020 | known affected: 28 recommended: 186 | 2026-10-16T01:04:06+00:00 | Vulnerability · Source |
| CVE-2025-13086 | suse_vex | SUSE CVE CVE-2025-13086 | known affected: 12 known not affected: 123 recommended: 56 | 2026-10-16T01:04:04+00:00 | Vulnerability · Source |
| CVE-2025-13352 | suse_vex | SUSE CVE CVE-2025-13352 | recommended: 2 | 2026-10-16T01:04:02+00:00 | Vulnerability · Source |
| CVE-2025-13357 | suse_vex | SUSE CVE CVE-2025-13357 | recommended: 2 | 2026-10-16T01:03:59+00:00 | Vulnerability · Source |
| CVE-2025-13465 | suse_vex | SUSE CVE CVE-2025-13465 | known affected: 522 known not affected: 351 recommended: 245 | 2026-10-16T01:03:56+00:00 | Vulnerability · Source |
| CVE-2025-13502 | suse_vex | SUSE CVE CVE-2025-13502 | known affected: 237 recommended: 606 | 2026-10-16T01:03:54+00:00 | Vulnerability · Source |
| CVE-2025-13609 | suse_vex | SUSE CVE CVE-2025-13609 | known affected: 36 recommended: 224 | 2026-10-16T01:03:50+00:00 | Vulnerability · Source |
| CVE-2025-13699 | suse_vex | SUSE CVE CVE-2025-13699 | known affected: 179 recommended: 250 | 2026-10-16T01:03:47+00:00 | Vulnerability · Source |
| CVE-2025-13763 | suse_vex | SUSE CVE CVE-2025-13763 | known affected: 57 recommended: 2 | 2026-10-16T01:03:44+00:00 | Vulnerability · Source |
| CVE-2025-13821 | suse_vex | SUSE CVE CVE-2025-13821 | recommended: 2 | 2026-10-16T01:03:42+00:00 | Vulnerability · Source |
| CVE-2025-13836 | suse_vex | SUSE CVE CVE-2025-13836 | known affected: 793 recommended: 1169 | 2026-10-16T01:03:39+00:00 | Vulnerability · Source |
| CVE-2025-13870 | suse_vex | SUSE CVE CVE-2025-13870 | recommended: 2 | 2026-10-16T01:03:37+00:00 | Vulnerability · Source |
| CVE-2025-13947 | suse_vex | SUSE CVE CVE-2025-13947 | known affected: 237 recommended: 606 | 2026-10-16T01:03:36+00:00 | Vulnerability · Source |
| CVE-2025-14087 | suse_vex | SUSE CVE CVE-2025-14087 | known affected: 666 known not affected: 1 recommended: 539 | 2026-10-16T01:03:34+00:00 | Vulnerability · Source |
| CVE-2025-14174 | suse_vex | SUSE CVE CVE-2025-14174 | known affected: 222 recommended: 608 | 2026-10-16T01:03:30+00:00 | Vulnerability · Source |
| CVE-2025-14178 | suse_vex | SUSE CVE CVE-2025-14178 | known affected: 1788 known not affected: 1 recommended: 1282 | 2026-10-16T01:03:28+00:00 | Vulnerability · Source |
| CVE-2025-14179 | suse_vex | SUSE CVE CVE-2025-14179 | known affected: 394 known not affected: 1264 recommended: 1091 | 2026-10-16T01:03:26+00:00 | Vulnerability · Source |
| CVE-2025-14180 | suse_vex | SUSE CVE CVE-2025-14180 | known affected: 188 known not affected: 2193 recommended: 646 | 2026-10-16T01:03:23+00:00 | Vulnerability · Source |
| CVE-2025-14321 | suse_vex | SUSE CVE CVE-2025-14321 | known affected: 73 recommended: 186 | 2026-10-16T01:03:19+00:00 | Vulnerability · Source |
| CVE-2025-14328 | suse_vex | SUSE CVE CVE-2025-14328 | known affected: 73 recommended: 186 | 2026-10-16T01:03:18+00:00 | Vulnerability · Source |
| CVE-2025-14329 | suse_vex | SUSE CVE CVE-2025-14329 | known affected: 73 recommended: 186 | 2026-10-16T01:03:16+00:00 | Vulnerability · Source |
| CVE-2025-14331 | suse_vex | SUSE CVE CVE-2025-14331 | known affected: 73 recommended: 186 | 2026-10-16T01:03:14+00:00 | Vulnerability · Source |
| CVE-2025-14435 | suse_vex | SUSE CVE CVE-2025-14435 | recommended: 2 | 2026-10-16T01:03:12+00:00 | Vulnerability · Source |
| CVE-2025-14512 | suse_vex | SUSE CVE CVE-2025-14512 | known affected: 667 recommended: 533 | 2026-10-16T01:03:10+00:00 | Vulnerability · Source |
| CVE-2025-14523 | suse_vex | SUSE CVE CVE-2025-14523 | known affected: 175 recommended: 230 | 2026-10-16T01:03:08+00:00 | Vulnerability · Source |
| CVE-2025-14525 | suse_vex | SUSE CVE CVE-2025-14525 | recommended: 14 | 2026-10-16T01:03:07+00:00 | Vulnerability · Source |
| CVE-2025-14575 | suse_vex | SUSE CVE CVE-2025-14575 | known affected: 2092 recommended: 37 | 2026-10-16T01:03:05+00:00 | Vulnerability · Source |
| CVE-2025-14576 | suse_vex | SUSE CVE CVE-2025-14576 | known affected: 170 known not affected: 425 recommended: 4 | 2026-10-16T01:03:03+00:00 | Vulnerability · Source |
| CVE-2025-14764 | suse_vex | SUSE CVE CVE-2025-14764 | recommended: 2 | 2026-10-16T01:03:01+00:00 | Vulnerability · Source |
| CVE-2025-14819 | suse_vex | SUSE CVE CVE-2025-14819 | known affected: 495 known not affected: 59 recommended: 128 | 2026-10-16T01:03:00+00:00 | Vulnerability · Source |
| CVE-2025-14831 | suse_vex | SUSE CVE CVE-2025-14831 | known affected: 645 recommended: 153 | 2026-10-16T01:02:58+00:00 | Vulnerability · Source |
| CVE-2025-14876 | suse_vex | SUSE CVE CVE-2025-14876 | known affected: 867 known not affected: 948 recommended: 682 | 2026-10-16T01:02:56+00:00 | Vulnerability · Source |
| CVE-2025-14986 | suse_vex | SUSE CVE CVE-2025-14986 | recommended: 2 | 2026-10-16T01:02:54+00:00 | Vulnerability · Source |
| CVE-2025-15079 | suse_vex | SUSE CVE CVE-2025-15079 | known affected: 539 known not affected: 15 recommended: 124 | 2026-10-16T01:02:52+00:00 | Vulnerability · Source |
| CVE-2025-15270 | suse_vex | SUSE CVE CVE-2025-15270 | known affected: 11 recommended: 37 | 2026-10-16T01:02:50+00:00 | Vulnerability · Source |
| CVE-2025-15275 | suse_vex | SUSE CVE CVE-2025-15275 | known affected: 11 recommended: 37 | 2026-10-16T01:02:45+00:00 | Vulnerability · Source |
| CVE-2025-15281 | suse_vex | SUSE CVE CVE-2025-15281 | known affected: 619 known not affected: 78 recommended: 774 | 2026-10-16T01:02:43+00:00 | Vulnerability · Source |
| CVE-2025-15282 | suse_vex | SUSE CVE CVE-2025-15282 | known affected: 410 known not affected: 142 recommended: 800 | 2026-10-16T01:02:41+00:00 | Vulnerability · Source |
| CVE-2025-15366 | suse_vex | SUSE CVE CVE-2025-15366 | known affected: 506 known not affected: 40 recommended: 904 | 2026-10-16T01:02:38+00:00 | Vulnerability · Source |
| CVE-2025-15367 | suse_vex | SUSE CVE CVE-2025-15367 | known affected: 410 known not affected: 136 recommended: 904 | 2026-10-16T01:02:36+00:00 | Vulnerability · Source |
| CVE-2025-15444 | suse_vex | SUSE CVE CVE-2025-15444 | known affected: 470 recommended: 100 | 2026-10-16T01:02:34+00:00 | Vulnerability · Source |
| CVE-2025-15467 | suse_vex | SUSE CVE CVE-2025-15467 | known affected: 396 known not affected: 600 recommended: 163 | 2026-10-16T01:02:32+00:00 | Vulnerability · Source |
| CVE-2025-15468 | suse_vex | SUSE CVE CVE-2025-15468 | known affected: 394 known not affected: 695 recommended: 69 | 2026-10-16T01:02:30+00:00 | Vulnerability · Source |
| CVE-2025-15469 | suse_vex | SUSE CVE CVE-2025-15469 | known affected: 394 known not affected: 701 recommended: 57 | 2026-10-16T01:02:27+00:00 | Vulnerability · Source |
| CVE-2025-15649 | suse_vex | SUSE CVE CVE-2025-15649 | known affected: 426 known not affected: 152 recommended: 21 | 2026-10-16T01:02:25+00:00 | Vulnerability · Source |