VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
78118 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-57931 | suse_vex | SUSE CVE CVE-2024-57931 | known affected: 761 known not affected: 38 recommended: 441 | 2026-10-04T16:53:49+00:00 | Vulnerability · Source |
| CVE-2024-57980 | suse_vex | SUSE CVE CVE-2024-57980 | known affected: 667 known not affected: 117 recommended: 473 | 2026-10-04T16:53:46+00:00 | Vulnerability · Source |
| CVE-2025-0444 | suse_vex | SUSE CVE CVE-2025-0444 | recommended: 10 | 2026-10-04T16:53:41+00:00 | Vulnerability · Source |
| CVE-2025-5455 | suse_vex | SUSE CVE CVE-2025-5455 | known affected: 2438 known not affected: 118 recommended: 807 | 2026-10-04T16:53:35+00:00 | Vulnerability · Source |
| CVE-2025-8177 | suse_vex | SUSE CVE CVE-2025-8177 | known affected: 479 known not affected: 7 recommended: 140 | 2026-10-04T16:53:32+00:00 | Vulnerability · Source |
| CVE-2025-11839 | suse_vex | SUSE CVE CVE-2025-11839 | known affected: 228 recommended: 7 | 2026-10-04T16:53:29+00:00 | Vulnerability · Source |
| CVE-2025-11896 | suse_vex | SUSE CVE CVE-2025-11896 | known affected: 324 recommended: 157 | 2026-10-04T16:53:28+00:00 | Vulnerability · Source |
| CVE-2025-12084 | suse_vex | SUSE CVE CVE-2025-12084 | known affected: 793 recommended: 751 | 2026-10-04T16:53:26+00:00 | Vulnerability · Source |
| CVE-2025-21645 | suse_vex | SUSE CVE CVE-2025-21645 | known affected: 461 known not affected: 343 recommended: 358 | 2026-10-04T16:53:21+00:00 | Vulnerability · Source |
| CVE-2025-21663 | suse_vex | SUSE CVE CVE-2025-21663 | known affected: 479 known not affected: 359 recommended: 401 | 2026-10-04T16:53:18+00:00 | Vulnerability · Source |
| CVE-2025-21702 | suse_vex | SUSE CVE CVE-2025-21702 | known affected: 612 recommended: 916 | 2026-10-04T16:53:15+00:00 | Vulnerability · Source |
| CVE-2025-21927 | suse_vex | SUSE CVE CVE-2025-21927 | known affected: 628 known not affected: 139 recommended: 454 | 2026-10-04T16:53:10+00:00 | Vulnerability · Source |
| CVE-2025-22025 | suse_vex | SUSE CVE CVE-2025-22025 | known affected: 394 known not affected: 350 recommended: 486 | 2026-10-04T16:53:08+00:00 | Vulnerability · Source |
| CVE-2025-24528 | suse_vex | SUSE CVE CVE-2025-24528 | known affected: 683 known not affected: 1 recommended: 254 | 2026-10-04T16:53:02+00:00 | Vulnerability · Source |
| CVE-2025-31498 | suse_vex | SUSE CVE CVE-2025-31498 | known affected: 394 known not affected: 82 recommended: 74 | 2026-10-04T16:52:59+00:00 | Vulnerability · Source |
| CVE-2025-38184 | suse_vex | SUSE CVE CVE-2025-38184 | known affected: 553 known not affected: 36 recommended: 780 | 2026-10-04T16:52:52+00:00 | Vulnerability · Source |
| CVE-2025-38263 | suse_vex | SUSE CVE CVE-2025-38263 | known affected: 716 known not affected: 34 recommended: 509 | 2026-10-04T16:52:48+00:00 | Vulnerability · Source |
| CVE-2025-38418 | suse_vex | SUSE CVE CVE-2025-38418 | known affected: 544 known not affected: 262 recommended: 472 | 2026-10-04T16:52:44+00:00 | Vulnerability · Source |
| CVE-2025-39726 | suse_vex | SUSE CVE CVE-2025-39726 | known affected: 479 known not affected: 68 recommended: 693 | 2026-10-04T16:52:37+00:00 | Vulnerability · Source |
| CVE-2025-39847 | suse_vex | SUSE CVE CVE-2025-39847 | known affected: 729 recommended: 501 | 2026-10-04T16:52:34+00:00 | Vulnerability · Source |
| CVE-2025-40283 | suse_vex | SUSE CVE CVE-2025-40283 | known affected: 690 known not affected: 83 recommended: 407 | 2026-10-04T16:52:26+00:00 | Vulnerability · Source |
| CVE-2025-46569 | suse_vex | SUSE CVE CVE-2025-46569 | known affected: 3 recommended: 54 | 2026-10-04T16:52:22+00:00 | Vulnerability · Source |
| CVE-2025-58181 | suse_vex | SUSE CVE CVE-2025-58181 | known affected: 1115 known not affected: 256 recommended: 508 | 2026-10-04T16:52:17+00:00 | Vulnerability · Source |
| CVE-2025-61730 | suse_vex | SUSE CVE CVE-2025-61730 | known affected: 48 known not affected: 109 recommended: 252 | 2026-10-04T16:52:15+00:00 | Vulnerability · Source |
| CVE-2025-67724 | suse_vex | SUSE CVE CVE-2025-67724 | known affected: 487 known not affected: 11 recommended: 451 | 2026-10-04T16:52:11+00:00 | Vulnerability · Source |
| CVE-2025-69418 | suse_vex | SUSE CVE CVE-2025-69418 | known affected: 458 known not affected: 343 recommended: 319 | 2026-10-04T16:52:06+00:00 | Vulnerability · Source |
| CVE-2025-69419 | suse_vex | SUSE CVE CVE-2025-69419 | known affected: 458 known not affected: 344 recommended: 324 | 2026-10-04T16:52:04+00:00 | Vulnerability · Source |
| CVE-2025-69420 | suse_vex | SUSE CVE CVE-2025-69420 | known affected: 458 known not affected: 212 recommended: 426 | 2026-10-04T16:52:03+00:00 | Vulnerability · Source |
| CVE-2025-69644 | suse_vex | SUSE CVE CVE-2025-69644 | known affected: 171 recommended: 7 | 2026-10-04T16:52:01+00:00 | Vulnerability · Source |
| CVE-2025-69645 | suse_vex | SUSE CVE CVE-2025-69645 | known affected: 216 recommended: 7 | 2026-10-04T16:51:59+00:00 | Vulnerability · Source |
| CVE-2025-69648 | suse_vex | SUSE CVE CVE-2025-69648 | known affected: 171 recommended: 7 | 2026-10-04T16:51:58+00:00 | Vulnerability · Source |
| CVE-2026-13820 | suse_vex | SUSE CVE CVE-2026-13820 | recommended: 10 | 2026-10-04T16:51:35+00:00 | Vulnerability · Source |
| CVE-2026-13833 | suse_vex | SUSE CVE CVE-2026-13833 | recommended: 14 | 2026-10-04T16:51:28+00:00 | Vulnerability · Source |
| CVE-2026-13834 | suse_vex | SUSE CVE CVE-2026-13834 | recommended: 14 | 2026-10-04T16:51:26+00:00 | Vulnerability · Source |
| CVE-2026-13883 | suse_vex | SUSE CVE CVE-2026-13883 | recommended: 14 | 2026-10-04T16:51:08+00:00 | Vulnerability · Source |
| CVE-2026-13885 | suse_vex | SUSE CVE CVE-2026-13885 | recommended: 10 | 2026-10-04T16:51:06+00:00 | Vulnerability · Source |
| CVE-2026-13975 | suse_vex | SUSE CVE CVE-2026-13975 | recommended: 14 | 2026-10-04T16:50:40+00:00 | Vulnerability · Source |
| CVE-2026-14385 | suse_vex | SUSE CVE CVE-2026-14385 | recommended: 14 | 2026-10-04T16:49:49+00:00 | Vulnerability · Source |
| CVE-2026-14388 | suse_vex | SUSE CVE CVE-2026-14388 | recommended: 14 | 2026-10-04T16:49:47+00:00 | Vulnerability · Source |
| CVE-2026-14390 | suse_vex | SUSE CVE CVE-2026-14390 | recommended: 14 | 2026-10-04T16:49:45+00:00 | Vulnerability · Source |
| CVE-2026-14398 | suse_vex | SUSE CVE CVE-2026-14398 | recommended: 14 | 2026-10-04T16:49:40+00:00 | Vulnerability · Source |
| CVE-2026-14401 | suse_vex | SUSE CVE CVE-2026-14401 | recommended: 14 | 2026-10-04T16:49:38+00:00 | Vulnerability · Source |
| CVE-2026-14402 | suse_vex | SUSE CVE CVE-2026-14402 | recommended: 14 | 2026-10-04T16:49:36+00:00 | Vulnerability · Source |
| CVE-2026-14411 | suse_vex | SUSE CVE CVE-2026-14411 | recommended: 14 | 2026-10-04T16:49:33+00:00 | Vulnerability · Source |
| CVE-2026-14412 | suse_vex | SUSE CVE CVE-2026-14412 | recommended: 14 | 2026-10-04T16:49:31+00:00 | Vulnerability · Source |
| CVE-2026-14413 | suse_vex | SUSE CVE CVE-2026-14413 | recommended: 14 | 2026-10-04T16:49:29+00:00 | Vulnerability · Source |
| CVE-2026-14425 | suse_vex | SUSE CVE CVE-2026-14425 | recommended: 14 | 2026-10-04T16:49:25+00:00 | Vulnerability · Source |
| CVE-2026-14429 | suse_vex | SUSE CVE CVE-2026-14429 | recommended: 10 | 2026-10-04T16:49:23+00:00 | Vulnerability · Source |
| CVE-2026-14457 | suse_vex | SUSE CVE CVE-2026-14457 | known affected: 394 known not affected: 561 recommended: 75 | 2026-10-04T16:49:19+00:00 | Vulnerability · Source |
| CVE-2026-45447 | suse_vex | SUSE CVE CVE-2026-45447 | known affected: 556 known not affected: 116 recommended: 370 | 2026-10-04T16:48:57+00:00 | Vulnerability · Source |