VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287378 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-57924 | suse_vex | SUSE CVE CVE-2024-57924 | known affected: 705 recommended: 421 | 2026-07-31T01:23:27+00:00 | Vulnerability · Source |
| CVE-2024-57925 | suse_vex | SUSE CVE CVE-2024-57925 | known not affected: 453 | 2026-07-31T01:23:25+00:00 | Vulnerability · Source |
| CVE-2024-57939 | suse_vex | SUSE CVE CVE-2024-57939 | known not affected: 453 | 2026-07-31T01:23:22+00:00 | Vulnerability · Source |
| CVE-2024-57945 | suse_vex | SUSE CVE CVE-2024-57945 | known not affected: 453 | 2026-07-31T01:23:20+00:00 | Vulnerability · Source |
| CVE-2024-57948 | suse_vex | SUSE CVE CVE-2024-57948 | known affected: 381 known not affected: 153 recommended: 588 | 2026-07-31T01:23:18+00:00 | Vulnerability · Source |
| CVE-2024-57977 | suse_vex | SUSE CVE CVE-2024-57977 | known not affected: 459 recommended: 42 | 2026-07-31T01:23:16+00:00 | Vulnerability · Source |
| CVE-2024-58010 | suse_vex | SUSE CVE CVE-2024-58010 | known not affected: 461 | 2026-07-31T01:23:14+00:00 | Vulnerability · Source |
| CVE-2024-58015 | suse_vex | SUSE CVE CVE-2024-58015 | known affected: 579 known not affected: 234 recommended: 247 | 2026-07-31T01:23:13+00:00 | Vulnerability · Source |
| CVE-2024-58016 | suse_vex | SUSE CVE CVE-2024-58016 | known not affected: 461 | 2026-07-31T01:23:11+00:00 | Vulnerability · Source |
| CVE-2024-58058 | suse_vex | SUSE CVE CVE-2024-58058 | known affected: 533 known not affected: 257 recommended: 309 | 2026-07-31T01:23:09+00:00 | Vulnerability · Source |
| CVE-2024-58085 | suse_vex | SUSE CVE CVE-2024-58085 | known affected: 455 known not affected: 345 recommended: 309 | 2026-07-31T01:23:06+00:00 | Vulnerability · Source |
| CVE-2024-58094 | suse_vex | SUSE CVE CVE-2024-58094 | known affected: 394 known not affected: 367 recommended: 365 | 2026-07-31T01:23:04+00:00 | Vulnerability · Source |
| CVE-2024-58095 | suse_vex | SUSE CVE CVE-2024-58095 | known affected: 394 known not affected: 367 recommended: 365 | 2026-07-31T01:23:02+00:00 | Vulnerability · Source |
| CVE-2025-1372 | suse_vex | SUSE CVE CVE-2025-1372 | known affected: 241 known not affected: 68 recommended: 308 | 2026-07-31T01:22:56+00:00 | Vulnerability · Source |
| CVE-2025-1377 | suse_vex | SUSE CVE CVE-2025-1377 | known affected: 162 known not affected: 147 recommended: 308 | 2026-07-31T01:22:54+00:00 | Vulnerability · Source |
| CVE-2025-2784 | suse_vex | SUSE CVE CVE-2025-2784 | known affected: 55 recommended: 246 | 2026-07-31T01:22:52+00:00 | Vulnerability · Source |
| CVE-2025-2786 | suse_vex | SUSE CVE CVE-2025-2786 | No product status | 2026-07-31T01:22:50+00:00 | Vulnerability · Source |
| CVE-2025-2842 | suse_vex | SUSE CVE CVE-2025-2842 | No product status | 2026-07-31T01:22:47+00:00 | Vulnerability · Source |
| CVE-2025-2843 | suse_vex | SUSE CVE CVE-2025-2843 | No product status | 2026-07-31T01:22:45+00:00 | Vulnerability · Source |
| CVE-2025-3512 | suse_vex | SUSE CVE CVE-2025-3512 | known not affected: 1825 | 2026-07-31T01:22:41+00:00 | Vulnerability · Source |
| CVE-2025-5455 | suse_vex | SUSE CVE CVE-2025-5455 | known affected: 1822 known not affected: 60 recommended: 919 | 2026-07-31T01:22:34+00:00 | Vulnerability · Source |
| CVE-2025-5683 | suse_vex | SUSE CVE CVE-2025-5683 | known affected: 74 | 2026-07-31T01:22:32+00:00 | Vulnerability · Source |
| CVE-2025-5991 | suse_vex | SUSE CVE CVE-2025-5991 | known not affected: 2250 | 2026-07-31T01:22:29+00:00 | Vulnerability · Source |
| CVE-2025-5992 | suse_vex | SUSE CVE CVE-2025-5992 | known not affected: 2194 recommended: 172 | 2026-07-31T01:22:26+00:00 | Vulnerability · Source |
| CVE-2025-6203 | suse_vex | SUSE CVE CVE-2025-6203 | recommended: 9 | 2026-07-31T01:22:23+00:00 | Vulnerability · Source |
| CVE-2025-7453 | suse_vex | SUSE CVE CVE-2025-7453 | No product status | 2026-07-31T01:22:20+00:00 | Vulnerability · Source |
| CVE-2025-7783 | suse_vex | SUSE CVE CVE-2025-7783 | known affected: 223 known not affected: 283 recommended: 21 | 2026-07-31T01:22:18+00:00 | Vulnerability · Source |
| CVE-2025-8028 | suse_vex | SUSE CVE CVE-2025-8028 | known affected: 37 recommended: 357 | 2026-07-31T01:22:15+00:00 | Vulnerability · Source |
| CVE-2025-8036 | suse_vex | SUSE CVE CVE-2025-8036 | known affected: 37 recommended: 338 | 2026-07-31T01:22:11+00:00 | Vulnerability · Source |
| CVE-2025-8038 | suse_vex | SUSE CVE CVE-2025-8038 | known affected: 37 recommended: 338 | 2026-07-31T01:22:08+00:00 | Vulnerability · Source |
| CVE-2025-10728 | suse_vex | SUSE CVE CVE-2025-10728 | known affected: 21 known not affected: 155 recommended: 15 | 2026-07-31T01:21:58+00:00 | Vulnerability · Source |
| CVE-2025-10729 | suse_vex | SUSE CVE CVE-2025-10729 | known affected: 11 known not affected: 164 recommended: 15 | 2026-07-31T01:21:56+00:00 | Vulnerability · Source |
| CVE-2025-11776 | suse_vex | SUSE CVE CVE-2025-11776 | No product status | 2026-07-31T01:21:51+00:00 | Vulnerability · Source |
| CVE-2025-11794 | suse_vex | SUSE CVE CVE-2025-11794 | No product status | 2026-07-31T01:21:49+00:00 | Vulnerability · Source |
| CVE-2025-13353 | suse_vex | SUSE CVE CVE-2025-13353 | No product status | 2026-07-31T01:21:46+00:00 | Vulnerability · Source |
| CVE-2025-14523 | suse_vex | SUSE CVE CVE-2025-14523 | known affected: 126 recommended: 231 | 2026-07-31T01:21:41+00:00 | Vulnerability · Source |
| CVE-2025-14576 | suse_vex | SUSE CVE CVE-2025-14576 | known affected: 169 known not affected: 402 recommended: 4 | 2026-07-31T01:21:38+00:00 | Vulnerability · Source |
| CVE-2025-15366 | suse_vex | SUSE CVE CVE-2025-15366 | known affected: 470 recommended: 808 | 2026-07-31T01:21:33+00:00 | Vulnerability · Source |
| CVE-2025-15367 | suse_vex | SUSE CVE CVE-2025-15367 | known affected: 422 known not affected: 48 recommended: 808 | 2026-07-31T01:21:31+00:00 | Vulnerability · Source |
| CVE-2025-21634 | suse_vex | SUSE CVE CVE-2025-21634 | known affected: 394 known not affected: 399 recommended: 53 | 2026-07-31T01:21:26+00:00 | Vulnerability · Source |
| CVE-2025-21635 | suse_vex | SUSE CVE CVE-2025-21635 | known affected: 663 known not affected: 8 recommended: 421 | 2026-07-31T01:21:23+00:00 | Vulnerability · Source |
| CVE-2025-21638 | suse_vex | SUSE CVE CVE-2025-21638 | known affected: 663 known not affected: 42 recommended: 403 | 2026-07-31T01:21:20+00:00 | Vulnerability · Source |
| CVE-2025-21640 | suse_vex | SUSE CVE CVE-2025-21640 | known affected: 663 known not affected: 42 recommended: 403 | 2026-07-31T01:21:18+00:00 | Vulnerability · Source |
| CVE-2025-21646 | suse_vex | SUSE CVE CVE-2025-21646 | known affected: 508 known not affected: 282 recommended: 353 | 2026-07-31T01:21:15+00:00 | Vulnerability · Source |
| CVE-2025-21647 | suse_vex | SUSE CVE CVE-2025-21647 | known affected: 384 known not affected: 249 recommended: 548 | 2026-07-31T01:21:12+00:00 | Vulnerability · Source |
| CVE-2025-21648 | suse_vex | SUSE CVE CVE-2025-21648 | known affected: 394 known not affected: 22 recommended: 475 | 2026-07-31T01:21:10+00:00 | Vulnerability · Source |
| CVE-2025-21652 | suse_vex | SUSE CVE CVE-2025-21652 | known affected: 410 known not affected: 308 recommended: 405 | 2026-07-31T01:21:07+00:00 | Vulnerability · Source |
| CVE-2025-21660 | suse_vex | SUSE CVE CVE-2025-21660 | known not affected: 453 | 2026-07-31T01:21:03+00:00 | Vulnerability · Source |
| CVE-2025-21672 | suse_vex | SUSE CVE CVE-2025-21672 | known not affected: 459 recommended: 41 | 2026-07-31T01:20:58+00:00 | Vulnerability · Source |
| CVE-2025-21673 | suse_vex | SUSE CVE CVE-2025-21673 | known affected: 634 known not affected: 58 recommended: 389 | 2026-07-31T01:20:56+00:00 | Vulnerability · Source |