VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291925 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-57986 | suse_vex | SUSE CVE CVE-2024-57986 | known affected: 500 known not affected: 180 recommended: 445 | 2026-08-05T00:48:16+00:00 | Vulnerability · Source |
| CVE-2024-57995 | suse_vex | SUSE CVE CVE-2024-57995 | known affected: 394 known not affected: 352 recommended: 247 | 2026-08-05T00:48:14+00:00 | Vulnerability · Source |
| CVE-2024-58069 | suse_vex | SUSE CVE CVE-2024-58069 | known affected: 500 known not affected: 180 recommended: 447 | 2026-08-05T00:48:02+00:00 | Vulnerability · Source |
| CVE-2025-5025 | suse_vex | SUSE CVE CVE-2025-5025 | known affected: 394 known not affected: 115 recommended: 68 | 2026-08-05T00:47:46+00:00 | Vulnerability · Source |
| CVE-2025-7709 | suse_vex | SUSE CVE CVE-2025-7709 | known affected: 495 known not affected: 35 recommended: 134 | 2026-08-05T00:47:40+00:00 | Vulnerability · Source |
| CVE-2025-9086 | suse_vex | SUSE CVE CVE-2025-9086 | first fixed: 13 known affected: 364 known not affected: 31 recommended: 245 | 2026-08-05T00:47:38+00:00 | Vulnerability · Source |
| CVE-2025-10158 | suse_vex | SUSE CVE CVE-2025-10158 | known affected: 419 recommended: 44 | 2026-08-05T00:47:36+00:00 | Vulnerability · Source |
| CVE-2025-11002 | suse_vex | SUSE CVE CVE-2025-11002 | known not affected: 21 | 2026-08-05T00:47:33+00:00 | Vulnerability · Source |
| CVE-2025-12801 | suse_vex | SUSE CVE CVE-2025-12801 | known affected: 513 recommended: 69 | 2026-08-05T00:47:31+00:00 | Vulnerability · Source |
| CVE-2025-13499 | suse_vex | SUSE CVE CVE-2025-13499 | known affected: 182 known not affected: 42 recommended: 234 | 2026-08-05T00:47:29+00:00 | Vulnerability · Source |
| CVE-2025-13674 | suse_vex | SUSE CVE CVE-2025-13674 | known not affected: 250 recommended: 183 | 2026-08-05T00:47:27+00:00 | Vulnerability · Source |
| CVE-2025-21769 | suse_vex | SUSE CVE CVE-2025-21769 | known affected: 57 known not affected: 295 | 2026-08-05T00:47:14+00:00 | Vulnerability · Source |
| CVE-2025-27221 | suse_vex | SUSE CVE CVE-2025-27221 | known affected: 494 known not affected: 82 recommended: 224 | 2026-08-05T00:47:03+00:00 | Vulnerability · Source |
| CVE-2025-28162 | suse_vex | SUSE CVE CVE-2025-28162 | known affected: 399 known not affected: 139 recommended: 143 | 2026-08-05T00:47:01+00:00 | Vulnerability · Source |
| CVE-2025-32728 | suse_vex | SUSE CVE CVE-2025-32728 | known affected: 368 known not affected: 60 recommended: 298 | 2026-08-05T00:46:57+00:00 | Vulnerability · Source |
| CVE-2025-38079 | suse_vex | SUSE CVE CVE-2025-38079 | known affected: 405 recommended: 921 | 2026-08-05T00:46:47+00:00 | Vulnerability · Source |
| CVE-2025-38137 | suse_vex | SUSE CVE CVE-2025-38137 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-08-05T00:46:44+00:00 | Vulnerability · Source |
| CVE-2025-38177 | suse_vex | SUSE CVE CVE-2025-38177 | first fixed: 2 known affected: 192 recommended: 891 | 2026-08-05T00:46:42+00:00 | Vulnerability · Source |
| CVE-2025-38323 | suse_vex | SUSE CVE CVE-2025-38323 | first fixed: 2 known affected: 405 known not affected: 320 recommended: 816 | 2026-08-05T00:46:37+00:00 | Vulnerability · Source |
| CVE-2025-38380 | suse_vex | SUSE CVE CVE-2025-38380 | first fixed: 2 known affected: 344 recommended: 777 | 2026-08-05T00:46:33+00:00 | Vulnerability · Source |
| CVE-2025-38563 | suse_vex | SUSE CVE CVE-2025-38563 | first fixed: 2 known affected: 496 known not affected: 6 recommended: 830 | 2026-08-05T00:46:21+00:00 | Vulnerability · Source |
| CVE-2025-39973 | suse_vex | SUSE CVE CVE-2025-39973 | first fixed: 2 known affected: 415 recommended: 1026 | 2026-08-05T00:45:49+00:00 | Vulnerability · Source |
| CVE-2025-49180 | suse_vex | SUSE CVE CVE-2025-49180 | known affected: 420 known not affected: 1 recommended: 184 | 2026-08-05T00:45:20+00:00 | Vulnerability · Source |
| CVE-2025-52194 | suse_vex | SUSE CVE CVE-2025-52194 | known affected: 78 recommended: 58 | 2026-08-05T00:45:18+00:00 | Vulnerability · Source |
| CVE-2025-54505 | suse_vex | SUSE CVE CVE-2025-54505 | known affected: 657 known not affected: 23 recommended: 135 | 2026-08-05T00:45:16+00:00 | Vulnerability · Source |
| CVE-2025-54770 | suse_vex | SUSE CVE CVE-2025-54770 | known affected: 394 known not affected: 275 recommended: 209 | 2026-08-05T00:45:14+00:00 | Vulnerability · Source |
| CVE-2025-54771 | suse_vex | SUSE CVE CVE-2025-54771 | known affected: 596 recommended: 302 | 2026-08-05T00:45:12+00:00 | Vulnerability · Source |
| CVE-2025-61662 | suse_vex | SUSE CVE CVE-2025-61662 | known affected: 596 recommended: 348 | 2026-08-05T00:45:03+00:00 | Vulnerability · Source |
| CVE-2025-61984 | suse_vex | SUSE CVE CVE-2025-61984 | known affected: 395 recommended: 347 | 2026-08-05T00:45:01+00:00 | Vulnerability · Source |
| CVE-2025-67030 | suse_vex | SUSE CVE CVE-2025-67030 | known affected: 4 recommended: 579 | 2026-08-05T00:44:57+00:00 | Vulnerability · Source |
| CVE-2025-68287 | suse_vex | SUSE CVE CVE-2025-68287 | first fixed: 2 known affected: 624 known not affected: 61 recommended: 508 | 2026-08-05T00:44:53+00:00 | Vulnerability · Source |
| CVE-2025-71113 | suse_vex | SUSE CVE CVE-2025-71113 | first fixed: 2 known affected: 566 known not affected: 5 recommended: 510 | 2026-08-05T00:44:45+00:00 | Vulnerability · Source |
| CVE-2026-1526 | suse_vex | SUSE CVE CVE-2026-1526 | recommended: 34 | 2026-08-05T00:44:39+00:00 | Vulnerability · Source |
| CVE-2026-1528 | suse_vex | SUSE CVE CVE-2026-1528 | recommended: 34 | 2026-08-05T00:44:38+00:00 | Vulnerability · Source |
| CVE-2026-2229 | suse_vex | SUSE CVE CVE-2026-2229 | recommended: 34 | 2026-08-05T00:44:36+00:00 | Vulnerability · Source |
| CVE-2026-4631 | suse_vex | SUSE CVE CVE-2026-4631 | known not affected: 39 recommended: 110 | 2026-08-05T00:44:29+00:00 | Vulnerability · Source |
| CVE-2026-5450 | suse_vex | SUSE CVE CVE-2026-5450 | first fixed: 1 known affected: 532 recommended: 1100 | 2026-08-05T00:44:24+00:00 | Vulnerability · Source |
| CVE-2026-7020 | suse_vex | SUSE CVE CVE-2026-7020 | known affected: 4 | 2026-08-05T00:44:16+00:00 | Vulnerability · Source |
| CVE-2026-8997 | suse_vex | SUSE CVE CVE-2026-8997 | recommended: 1 | 2026-08-05T00:44:09+00:00 | Vulnerability · Source |
| CVE-2026-9147 | suse_vex | SUSE CVE CVE-2026-9147 | No product status | 2026-08-05T00:44:07+00:00 | Vulnerability · Source |
| CVE-2026-9499 | suse_vex | SUSE CVE CVE-2026-9499 | known affected: 1156 known not affected: 394 | 2026-08-05T00:44:04+00:00 | Vulnerability · Source |
| CVE-2026-16445 | suse_vex | SUSE CVE CVE-2026-16445 | known affected: 119 | 2026-08-05T00:42:32+00:00 | Vulnerability · Source |
| CVE-2026-16728 | suse_vex | SUSE CVE CVE-2026-16728 | known affected: 172 known not affected: 64 | 2026-08-05T00:42:21+00:00 | Vulnerability · Source |
| CVE-2026-16729 | suse_vex | SUSE CVE CVE-2026-16729 | known affected: 172 known not affected: 64 | 2026-08-05T00:42:20+00:00 | Vulnerability · Source |
| CVE-2026-17729 | suse_vex | SUSE CVE CVE-2026-17729 | recommended: 6 | 2026-08-05T00:42:19+00:00 | Vulnerability · Source |
| CVE-2026-17738 | suse_vex | SUSE CVE CVE-2026-17738 | recommended: 6 | 2026-08-05T00:42:17+00:00 | Vulnerability · Source |
| CVE-2026-17743 | suse_vex | SUSE CVE CVE-2026-17743 | recommended: 6 | 2026-08-05T00:42:16+00:00 | Vulnerability · Source |
| CVE-2026-17748 | suse_vex | SUSE CVE CVE-2026-17748 | recommended: 6 | 2026-08-05T00:42:15+00:00 | Vulnerability · Source |
| CVE-2026-17749 | suse_vex | SUSE CVE CVE-2026-17749 | recommended: 6 | 2026-08-05T00:42:14+00:00 | Vulnerability · Source |
| CVE-2026-17754 | suse_vex | SUSE CVE CVE-2026-17754 | recommended: 6 | 2026-08-05T00:42:13+00:00 | Vulnerability · Source |