VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
81830 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50459 | suse_vex | SUSE CVE CVE-2022-50459 | known affected: 403 known not affected: 235 recommended: 323 | 2026-10-07T23:57:25+00:00 | Vulnerability · Source |
| CVE-2023-41074 | suse_vex | SUSE CVE CVE-2023-41074 | known affected: 130 known not affected: 101 recommended: 861 | 2026-10-07T23:57:04+00:00 | Vulnerability · Source |
| CVE-2023-53400 | suse_vex | SUSE CVE CVE-2023-53400 | known affected: 540 known not affected: 176 recommended: 292 | 2026-10-07T23:56:48+00:00 | Vulnerability · Source |
| CVE-2023-54283 | suse_vex | SUSE CVE CVE-2023-54283 | known affected: 746 known not affected: 105 recommended: 241 | 2026-10-07T23:56:35+00:00 | Vulnerability · Source |
| CVE-2024-14027 | suse_vex | SUSE CVE CVE-2024-14027 | known affected: 2 known not affected: 429 recommended: 172 | 2026-10-07T23:56:28+00:00 | Vulnerability · Source |
| CVE-2024-21503 | suse_vex | SUSE CVE CVE-2024-21503 | recommended: 11 | 2026-10-07T23:56:24+00:00 | Vulnerability · Source |
| CVE-2024-24762 | suse_vex | SUSE CVE CVE-2024-24762 | known not affected: 2 recommended: 18 | 2026-10-07T23:56:20+00:00 | Vulnerability · Source |
| CVE-2024-26730 | suse_vex | SUSE CVE CVE-2024-26730 | known affected: 65 known not affected: 334 | 2026-10-07T23:56:15+00:00 | Vulnerability · Source |
| CVE-2024-44981 | suse_vex | SUSE CVE CVE-2024-44981 | known affected: 459 known not affected: 376 recommended: 138 | 2026-10-07T23:55:56+00:00 | Vulnerability · Source |
| CVE-2024-50099 | suse_vex | SUSE CVE CVE-2024-50099 | known affected: 557 known not affected: 85 recommended: 601 | 2026-10-07T23:55:47+00:00 | Vulnerability · Source |
| CVE-2024-53203 | suse_vex | SUSE CVE CVE-2024-53203 | known affected: 643 known not affected: 278 recommended: 401 | 2026-10-07T23:55:40+00:00 | Vulnerability · Source |
| CVE-2024-57952 | suse_vex | SUSE CVE CVE-2024-57952 | known affected: 2 known not affected: 469 recommended: 154 | 2026-10-07T23:55:32+00:00 | Vulnerability · Source |
| CVE-2024-58090 | suse_vex | SUSE CVE CVE-2024-58090 | known affected: 712 known not affected: 34 recommended: 464 | 2026-10-07T23:55:29+00:00 | Vulnerability · Source |
| CVE-2025-6052 | suse_vex | SUSE CVE CVE-2025-6052 | known affected: 394 known not affected: 655 recommended: 201 | 2026-10-07T23:55:23+00:00 | Vulnerability · Source |
| CVE-2025-27587 | suse_vex | SUSE CVE CVE-2025-27587 | known affected: 396 known not affected: 766 recommended: 95 | 2026-10-07T23:55:08+00:00 | Vulnerability · Source |
| CVE-2025-37751 | suse_vex | SUSE CVE CVE-2025-37751 | known affected: 396 known not affected: 459 recommended: 265 | 2026-10-07T23:55:02+00:00 | Vulnerability · Source |
| CVE-2025-37841 | suse_vex | SUSE CVE CVE-2025-37841 | known affected: 714 known not affected: 49 recommended: 490 | 2026-10-07T23:54:58+00:00 | Vulnerability · Source |
| CVE-2025-38090 | suse_vex | SUSE CVE CVE-2025-38090 | known affected: 396 known not affected: 442 recommended: 472 | 2026-10-07T23:54:47+00:00 | Vulnerability · Source |
| CVE-2025-38141 | suse_vex | SUSE CVE CVE-2025-38141 | known affected: 7 known not affected: 555 recommended: 239 | 2026-10-07T23:54:40+00:00 | Vulnerability · Source |
| CVE-2025-38148 | suse_vex | SUSE CVE CVE-2025-38148 | known affected: 396 known not affected: 442 recommended: 514 | 2026-10-07T23:54:38+00:00 | Vulnerability · Source |
| CVE-2025-38182 | suse_vex | SUSE CVE CVE-2025-38182 | known affected: 444 known not affected: 405 recommended: 472 | 2026-10-07T23:54:34+00:00 | Vulnerability · Source |
| CVE-2025-38217 | suse_vex | SUSE CVE CVE-2025-38217 | known affected: 396 known not affected: 442 recommended: 472 | 2026-10-07T23:54:28+00:00 | Vulnerability · Source |
| CVE-2025-38262 | suse_vex | SUSE CVE CVE-2025-38262 | known affected: 2 known not affected: 524 recommended: 172 | 2026-10-07T23:54:22+00:00 | Vulnerability · Source |
| CVE-2025-38278 | suse_vex | SUSE CVE CVE-2025-38278 | known affected: 2 known not affected: 399 recommended: 154 | 2026-10-07T23:54:19+00:00 | Vulnerability · Source |
| CVE-2025-38287 | suse_vex | SUSE CVE CVE-2025-38287 | known affected: 396 known not affected: 492 recommended: 247 | 2026-10-07T23:54:17+00:00 | Vulnerability · Source |
| CVE-2025-38288 | suse_vex | SUSE CVE CVE-2025-38288 | known affected: 396 known not affected: 497 recommended: 330 | 2026-10-07T23:54:14+00:00 | Vulnerability · Source |
| CVE-2025-38299 | suse_vex | SUSE CVE CVE-2025-38299 | known affected: 396 known not affected: 484 recommended: 247 | 2026-10-07T23:54:11+00:00 | Vulnerability · Source |
| CVE-2025-38362 | suse_vex | SUSE CVE CVE-2025-38362 | known affected: 582 known not affected: 268 recommended: 472 | 2026-10-07T23:54:05+00:00 | Vulnerability · Source |
| CVE-2025-38364 | suse_vex | SUSE CVE CVE-2025-38364 | known affected: 439 known not affected: 399 recommended: 472 | 2026-10-07T23:54:03+00:00 | Vulnerability · Source |
| CVE-2025-38379 | suse_vex | SUSE CVE CVE-2025-38379 | known affected: 396 known not affected: 441 recommended: 384 | 2026-10-07T23:54:00+00:00 | Vulnerability · Source |
| CVE-2025-38397 | suse_vex | SUSE CVE CVE-2025-38397 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-07T23:53:56+00:00 | Vulnerability · Source |
| CVE-2025-38409 | suse_vex | SUSE CVE CVE-2025-38409 | known affected: 660 known not affected: 120 recommended: 472 | 2026-10-07T23:53:53+00:00 | Vulnerability · Source |
| CVE-2025-38410 | suse_vex | SUSE CVE CVE-2025-38410 | known affected: 729 known not affected: 109 recommended: 472 | 2026-10-07T23:53:50+00:00 | Vulnerability · Source |
| CVE-2025-38454 | suse_vex | SUSE CVE CVE-2025-38454 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-07T23:53:42+00:00 | Vulnerability · Source |
| CVE-2025-38456 | suse_vex | SUSE CVE CVE-2025-38456 | known affected: 401 known not affected: 405 recommended: 472 | 2026-10-07T23:53:40+00:00 | Vulnerability · Source |
| CVE-2025-38480 | suse_vex | SUSE CVE CVE-2025-38480 | known affected: 735 known not affected: 43 recommended: 472 | 2026-10-07T23:53:35+00:00 | Vulnerability · Source |
| CVE-2025-38484 | suse_vex | SUSE CVE CVE-2025-38484 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-07T23:53:32+00:00 | Vulnerability · Source |
| CVE-2025-38530 | suse_vex | SUSE CVE CVE-2025-38530 | known affected: 735 known not affected: 114 recommended: 490 | 2026-10-07T23:53:28+00:00 | Vulnerability · Source |
| CVE-2025-38537 | suse_vex | SUSE CVE CVE-2025-38537 | known affected: 396 known not affected: 453 recommended: 490 | 2026-10-07T23:53:25+00:00 | Vulnerability · Source |
| CVE-2025-38540 | suse_vex | SUSE CVE CVE-2025-38540 | known affected: 735 known not affected: 54 recommended: 490 | 2026-10-07T23:53:23+00:00 | Vulnerability · Source |
| CVE-2025-38550 | suse_vex | SUSE CVE CVE-2025-38550 | known affected: 539 known not affected: 310 recommended: 533 | 2026-10-07T23:53:20+00:00 | Vulnerability · Source |
| CVE-2025-38608 | suse_vex | SUSE CVE CVE-2025-38608 | known affected: 500 known not affected: 154 recommended: 827 | 2026-10-07T23:53:13+00:00 | Vulnerability · Source |
| CVE-2025-38619 | suse_vex | SUSE CVE CVE-2025-38619 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-07T23:53:10+00:00 | Vulnerability · Source |
| CVE-2025-38704 | suse_vex | SUSE CVE CVE-2025-38704 | known affected: 461 known not affected: 517 recommended: 172 | 2026-10-07T23:53:03+00:00 | Vulnerability · Source |
| CVE-2025-39693 | suse_vex | SUSE CVE CVE-2025-39693 | known affected: 524 known not affected: 259 recommended: 464 | 2026-10-07T23:52:55+00:00 | Vulnerability · Source |
| CVE-2025-39713 | suse_vex | SUSE CVE CVE-2025-39713 | known affected: 686 known not affected: 39 recommended: 464 | 2026-10-07T23:52:52+00:00 | Vulnerability · Source |
| CVE-2025-39722 | suse_vex | SUSE CVE CVE-2025-39722 | known affected: 69 known not affected: 450 recommended: 154 | 2026-10-07T23:52:48+00:00 | Vulnerability · Source |
| CVE-2025-39747 | suse_vex | SUSE CVE CVE-2025-39747 | known affected: 517 known not affected: 208 recommended: 247 | 2026-10-07T23:52:45+00:00 | Vulnerability · Source |
| CVE-2025-39749 | suse_vex | SUSE CVE CVE-2025-39749 | known affected: 596 known not affected: 187 recommended: 464 | 2026-10-07T23:52:42+00:00 | Vulnerability · Source |
| CVE-2025-39766 | suse_vex | SUSE CVE CVE-2025-39766 | known affected: 599 known not affected: 187 recommended: 547 | 2026-10-07T23:52:38+00:00 | Vulnerability · Source |