VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306223 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-24014 | suse_vex | SUSE CVE CVE-2025-24014 | known affected: 541 known not affected: 3 recommended: 158 | 2026-10-10T02:18:32+00:00 | Vulnerability · Source |
| CVE-2025-24049 | suse_vex | SUSE CVE CVE-2025-24049 | known affected: 394 known not affected: 31 recommended: 4852 | 2026-10-10T02:18:29+00:00 | Vulnerability · Source |
| CVE-2025-24162 | suse_vex | SUSE CVE CVE-2025-24162 | known affected: 176 recommended: 577 | 2026-10-10T02:18:27+00:00 | Vulnerability · Source |
| CVE-2025-24216 | suse_vex | SUSE CVE CVE-2025-24216 | known affected: 176 recommended: 566 | 2026-10-10T02:18:25+00:00 | Vulnerability · Source |
| CVE-2025-24355 | suse_vex | SUSE CVE CVE-2025-24355 | recommended: 4 | 2026-10-10T02:18:23+00:00 | Vulnerability · Source |
| CVE-2025-24358 | suse_vex | SUSE CVE CVE-2025-24358 | recommended: 5 | 2026-10-10T02:18:21+00:00 | Vulnerability · Source |
| CVE-2025-24366 | suse_vex | SUSE CVE CVE-2025-24366 | recommended: 4 | 2026-10-10T02:18:20+00:00 | Vulnerability · Source |
| CVE-2025-24369 | suse_vex | SUSE CVE CVE-2025-24369 | recommended: 5 | 2026-10-10T02:18:18+00:00 | Vulnerability · Source |
| CVE-2025-24371 | suse_vex | SUSE CVE CVE-2025-24371 | recommended: 4 | 2026-10-10T02:18:16+00:00 | Vulnerability · Source |
| CVE-2025-24376 | suse_vex | SUSE CVE CVE-2025-24376 | recommended: 4 | 2026-10-10T02:18:14+00:00 | Vulnerability · Source |
| CVE-2025-24495 | suse_vex | SUSE CVE CVE-2025-24495 | known affected: 20 recommended: 46 | 2026-10-10T02:18:13+00:00 | Vulnerability · Source |
| CVE-2025-24526 | suse_vex | SUSE CVE CVE-2025-24526 | recommended: 4 | 2026-10-10T02:18:11+00:00 | Vulnerability · Source |
| CVE-2025-24866 | suse_vex | SUSE CVE CVE-2025-24866 | recommended: 4 | 2026-10-10T02:18:09+00:00 | Vulnerability · Source |
| CVE-2025-24898 | suse_vex | SUSE CVE CVE-2025-24898 | known affected: 489 known not affected: 389 recommended: 34 | 2026-10-10T02:18:07+00:00 | Vulnerability · Source |
| CVE-2025-24912 | suse_vex | SUSE CVE CVE-2025-24912 | known affected: 394 known not affected: 50 recommended: 29 | 2026-10-10T02:18:05+00:00 | Vulnerability · Source |
| CVE-2025-24928 | suse_vex | SUSE CVE CVE-2025-24928 | known affected: 468 recommended: 304 | 2026-10-10T02:18:03+00:00 | Vulnerability · Source |
| CVE-2025-25196 | suse_vex | SUSE CVE CVE-2025-25196 | recommended: 4 | 2026-10-10T02:18:01+00:00 | Vulnerability · Source |
| CVE-2025-25208 | suse_vex | SUSE CVE CVE-2025-25208 | recommended: 4 | 2026-10-10T02:17:59+00:00 | Vulnerability · Source |
| CVE-2025-25279 | suse_vex | SUSE CVE CVE-2025-25279 | recommended: 4 | 2026-10-10T02:17:58+00:00 | Vulnerability · Source |
| CVE-2025-25473 | suse_vex | SUSE CVE CVE-2025-25473 | known not affected: 564 recommended: 273 | 2026-10-10T02:17:55+00:00 | Vulnerability · Source |
| CVE-2025-26260 | suse_vex | SUSE CVE CVE-2025-26260 | recommended: 4 | 2026-10-10T02:17:53+00:00 | Vulnerability · Source |
| CVE-2025-26465 | suse_vex | SUSE CVE CVE-2025-26465 | known affected: 404 recommended: 357 | 2026-10-10T02:17:51+00:00 | Vulnerability · Source |
| CVE-2025-26595 | suse_vex | SUSE CVE CVE-2025-26595 | known affected: 506 known not affected: 1 recommended: 259 | 2026-10-10T02:17:49+00:00 | Vulnerability · Source |
| CVE-2025-26596 | suse_vex | SUSE CVE CVE-2025-26596 | known affected: 446 known not affected: 1 recommended: 183 | 2026-10-10T02:17:47+00:00 | Vulnerability · Source |
| CVE-2025-26599 | suse_vex | SUSE CVE CVE-2025-26599 | known affected: 447 recommended: 183 | 2026-10-10T02:17:46+00:00 | Vulnerability · Source |
| CVE-2025-26601 | suse_vex | SUSE CVE CVE-2025-26601 | known affected: 446 known not affected: 1 recommended: 183 | 2026-10-10T02:17:44+00:00 | Vulnerability · Source |
| CVE-2025-26625 | suse_vex | SUSE CVE CVE-2025-26625 | known affected: 4 recommended: 42 | 2026-10-10T02:17:43+00:00 | Vulnerability · Source |
| CVE-2025-27088 | suse_vex | SUSE CVE CVE-2025-27088 | recommended: 4 | 2026-10-10T02:17:41+00:00 | Vulnerability · Source |
| CVE-2025-27093 | suse_vex | SUSE CVE CVE-2025-27093 | recommended: 1 | 2026-10-10T02:17:39+00:00 | Vulnerability · Source |
| CVE-2025-27112 | suse_vex | SUSE CVE CVE-2025-27112 | recommended: 4 | 2026-10-10T02:17:37+00:00 | Vulnerability · Source |
| CVE-2025-27219 | suse_vex | SUSE CVE CVE-2025-27219 | known affected: 500 known not affected: 156 recommended: 242 | 2026-10-10T02:17:35+00:00 | Vulnerability · Source |
| CVE-2025-27221 | suse_vex | SUSE CVE CVE-2025-27221 | known affected: 570 known not affected: 118 recommended: 242 | 2026-10-10T02:17:33+00:00 | Vulnerability · Source |
| CVE-2025-27421 | suse_vex | SUSE CVE CVE-2025-27421 | recommended: 4 | 2026-10-10T02:17:31+00:00 | Vulnerability · Source |
| CVE-2025-27509 | suse_vex | SUSE CVE CVE-2025-27509 | recommended: 4 | 2026-10-10T02:17:29+00:00 | Vulnerability · Source |
| CVE-2025-27516 | suse_vex | SUSE CVE CVE-2025-27516 | known affected: 401 known not affected: 26 recommended: 200 | 2026-10-10T02:17:27+00:00 | Vulnerability · Source |
| CVE-2025-27538 | suse_vex | SUSE CVE CVE-2025-27538 | recommended: 4 | 2026-10-10T02:17:26+00:00 | Vulnerability · Source |
| CVE-2025-27571 | suse_vex | SUSE CVE CVE-2025-27571 | recommended: 4 | 2026-10-10T02:17:24+00:00 | Vulnerability · Source |
| CVE-2025-27613 | suse_vex | SUSE CVE CVE-2025-27613 | known not affected: 214 recommended: 444 | 2026-10-10T02:17:21+00:00 | Vulnerability · Source |
| CVE-2025-27614 | suse_vex | SUSE CVE CVE-2025-27614 | known not affected: 261 recommended: 397 | 2026-10-10T02:17:20+00:00 | Vulnerability · Source |
| CVE-2025-27616 | suse_vex | SUSE CVE CVE-2025-27616 | recommended: 4 | 2026-10-10T02:17:18+00:00 | Vulnerability · Source |
| CVE-2025-27715 | suse_vex | SUSE CVE CVE-2025-27715 | recommended: 4 | 2026-10-10T02:17:16+00:00 | Vulnerability · Source |
| CVE-2025-27795 | suse_vex | SUSE CVE CVE-2025-27795 | known affected: 16 known not affected: 490 recommended: 24 | 2026-10-10T02:17:14+00:00 | Vulnerability · Source |
| CVE-2025-27831 | suse_vex | SUSE CVE CVE-2025-27831 | known not affected: 57 recommended: 101 | 2026-10-10T02:17:13+00:00 | Vulnerability · Source |
| CVE-2025-27833 | suse_vex | SUSE CVE CVE-2025-27833 | known not affected: 147 recommended: 11 | 2026-10-10T02:17:11+00:00 | Vulnerability · Source |
| CVE-2025-27834 | suse_vex | SUSE CVE CVE-2025-27834 | known not affected: 147 recommended: 11 | 2026-10-10T02:17:09+00:00 | Vulnerability · Source |
| CVE-2025-27837 | suse_vex | SUSE CVE CVE-2025-27837 | known not affected: 147 recommended: 11 | 2026-10-10T02:17:07+00:00 | Vulnerability · Source |
| CVE-2025-28164 | suse_vex | SUSE CVE CVE-2025-28164 | known affected: 429 known not affected: 222 recommended: 139 | 2026-10-10T02:17:05+00:00 | Vulnerability · Source |
| CVE-2025-29072 | suse_vex | SUSE CVE CVE-2025-29072 | recommended: 4 | 2026-10-10T02:17:04+00:00 | Vulnerability · Source |
| CVE-2025-29088 | suse_vex | SUSE CVE CVE-2025-29088 | known affected: 427 known not affected: 11 recommended: 246 | 2026-10-10T02:17:02+00:00 | Vulnerability · Source |
| CVE-2025-29778 | suse_vex | SUSE CVE CVE-2025-29778 | recommended: 4 | 2026-10-10T02:17:00+00:00 | Vulnerability · Source |