VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292268 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-58087 | suse_vex | SUSE CVE CVE-2024-58087 | known not affected: 463 | 2026-07-25T01:11:42+00:00 | Vulnerability · Source |
| CVE-2024-58237 | suse_vex | SUSE CVE CVE-2024-58237 | known affected: 486 known not affected: 216 recommended: 407 | 2026-07-25T01:11:25+00:00 | Vulnerability · Source |
| CVE-2024-58239 | suse_vex | SUSE CVE CVE-2024-58239 | known affected: 409 known not affected: 172 recommended: 658 | 2026-07-25T01:11:23+00:00 | Vulnerability · Source |
| CVE-2024-58249 | suse_vex | SUSE CVE CVE-2024-58249 | known not affected: 213 recommended: 137 | 2026-07-25T01:11:21+00:00 | Vulnerability · Source |
| CVE-2024-58266 | suse_vex | SUSE CVE CVE-2024-58266 | known affected: 89 known not affected: 1893 recommended: 19 | 2026-07-25T01:11:17+00:00 | Vulnerability · Source |
| CVE-2025-0395 | suse_vex | SUSE CVE CVE-2025-0395 | first fixed: 1 known affected: 460 known not affected: 13 recommended: 1077 | 2026-07-25T01:11:13+00:00 | Vulnerability · Source |
| CVE-2025-0624 | suse_vex | SUSE CVE CVE-2025-0624 | known affected: 424 recommended: 444 | 2026-07-25T01:11:11+00:00 | Vulnerability · Source |
| CVE-2025-1009 | suse_vex | SUSE CVE CVE-2025-1009 | known affected: 37 recommended: 178 | 2026-07-25T01:11:08+00:00 | Vulnerability · Source |
| CVE-2025-1151 | suse_vex | SUSE CVE CVE-2025-1151 | known affected: 470 known not affected: 74 recommended: 521 | 2026-07-25T01:11:02+00:00 | Vulnerability · Source |
| CVE-2025-1153 | suse_vex | SUSE CVE CVE-2025-1153 | known affected: 470 known not affected: 74 recommended: 521 | 2026-07-25T01:11:00+00:00 | Vulnerability · Source |
| CVE-2025-1215 | suse_vex | SUSE CVE CVE-2025-1215 | known affected: 473 known not affected: 4 recommended: 162 | 2026-07-25T01:10:58+00:00 | Vulnerability · Source |
| CVE-2025-1713 | suse_vex | SUSE CVE CVE-2025-1713 | known affected: 486 recommended: 196 | 2026-07-25T01:10:56+00:00 | Vulnerability · Source |
| CVE-2025-1934 | suse_vex | SUSE CVE CVE-2025-1934 | known affected: 37 recommended: 173 | 2026-07-25T01:10:52+00:00 | Vulnerability · Source |
| CVE-2025-2312 | suse_vex | SUSE CVE CVE-2025-2312 | known affected: 342 known not affected: 364 recommended: 500 | 2026-07-25T01:10:48+00:00 | Vulnerability · Source |
| CVE-2025-2574 | suse_vex | SUSE CVE CVE-2025-2574 | known not affected: 386 | 2026-07-25T01:10:45+00:00 | Vulnerability · Source |
| CVE-2025-2759 | suse_vex | SUSE CVE CVE-2025-2759 | known not affected: 272 | 2026-07-25T01:10:43+00:00 | Vulnerability · Source |
| CVE-2025-3359 | suse_vex | SUSE CVE CVE-2025-3359 | known affected: 40 recommended: 24 | 2026-07-25T01:10:35+00:00 | Vulnerability · Source |
| CVE-2025-3523 | suse_vex | SUSE CVE CVE-2025-3523 | known affected: 16 known not affected: 134 recommended: 24 | 2026-07-25T01:10:32+00:00 | Vulnerability · Source |
| CVE-2025-3548 | suse_vex | SUSE CVE CVE-2025-3548 | known affected: 1036 recommended: 11 | 2026-07-25T01:10:31+00:00 | Vulnerability · Source |
| CVE-2025-4447 | suse_vex | SUSE CVE CVE-2025-4447 | known affected: 434 known not affected: 487 recommended: 114 | 2026-07-25T01:10:23+00:00 | Vulnerability · Source |
| CVE-2025-4918 | suse_vex | SUSE CVE CVE-2025-4918 | known affected: 45 recommended: 152 | 2026-07-25T01:10:18+00:00 | Vulnerability · Source |
| CVE-2025-4920 | suse_vex | SUSE CVE CVE-2025-4920 | known affected: 45 recommended: 8 | 2026-07-25T01:10:16+00:00 | Vulnerability · Source |
| CVE-2025-5266 | suse_vex | SUSE CVE CVE-2025-5266 | known affected: 37 recommended: 186 | 2026-07-25T01:10:12+00:00 | Vulnerability · Source |
| CVE-2025-5889 | suse_vex | SUSE CVE CVE-2025-5889 | known affected: 536 known not affected: 6 recommended: 219 | 2026-07-25T01:10:05+00:00 | Vulnerability · Source |
| CVE-2025-5915 | suse_vex | SUSE CVE CVE-2025-5915 | known affected: 395 known not affected: 115 recommended: 72 | 2026-07-25T01:10:03+00:00 | Vulnerability · Source |
| CVE-2025-5916 | suse_vex | SUSE CVE CVE-2025-5916 | known affected: 453 known not affected: 50 recommended: 88 | 2026-07-25T01:10:01+00:00 | Vulnerability · Source |
| CVE-2025-6141 | suse_vex | SUSE CVE CVE-2025-6141 | known not affected: 578 | 2026-07-25T01:09:51+00:00 | Vulnerability · Source |
| CVE-2025-6199 | suse_vex | SUSE CVE CVE-2025-6199 | known affected: 444 known not affected: 83 recommended: 312 | 2026-07-25T01:09:47+00:00 | Vulnerability · Source |
| CVE-2025-6424 | suse_vex | SUSE CVE CVE-2025-6424 | known affected: 37 recommended: 361 | 2026-07-25T01:09:43+00:00 | Vulnerability · Source |
| CVE-2025-6425 | suse_vex | SUSE CVE CVE-2025-6425 | known affected: 37 recommended: 361 | 2026-07-25T01:09:42+00:00 | Vulnerability · Source |
| CVE-2025-6435 | suse_vex | SUSE CVE CVE-2025-6435 | known affected: 37 recommended: 342 | 2026-07-25T01:09:38+00:00 | Vulnerability · Source |
| CVE-2025-6494 | suse_vex | SUSE CVE CVE-2025-6494 | known not affected: 318 | 2026-07-25T01:09:34+00:00 | Vulnerability · Source |
| CVE-2025-7339 | suse_vex | SUSE CVE CVE-2025-7339 | known affected: 156 known not affected: 326 recommended: 1 | 2026-07-25T01:09:32+00:00 | Vulnerability · Source |
| CVE-2025-7394 | suse_vex | SUSE CVE CVE-2025-7394 | known not affected: 304 | 2026-07-25T01:09:29+00:00 | Vulnerability · Source |
| CVE-2025-7396 | suse_vex | SUSE CVE CVE-2025-7396 | known not affected: 304 | 2026-07-25T01:09:27+00:00 | Vulnerability · Source |
| CVE-2025-8033 | suse_vex | SUSE CVE CVE-2025-8033 | known affected: 37 recommended: 357 | 2026-07-25T01:09:22+00:00 | Vulnerability · Source |
| CVE-2025-8067 | suse_vex | SUSE CVE CVE-2025-8067 | known affected: 451 recommended: 259 | 2026-07-25T01:09:16+00:00 | Vulnerability · Source |
| CVE-2025-8114 | suse_vex | SUSE CVE CVE-2025-8114 | known affected: 497 recommended: 128 | 2026-07-25T01:09:15+00:00 | Vulnerability · Source |
| CVE-2025-8734 | suse_vex | SUSE CVE CVE-2025-8734 | known affected: 130 | 2026-07-25T01:09:07+00:00 | Vulnerability · Source |
| CVE-2025-9375 | suse_vex | SUSE CVE CVE-2025-9375 | known affected: 397 known not affected: 56 recommended: 25 | 2026-07-25T01:09:03+00:00 | Vulnerability · Source |
| CVE-2025-9403 | suse_vex | SUSE CVE CVE-2025-9403 | known affected: 444 known not affected: 11 recommended: 77 | 2026-07-25T01:09:02+00:00 | Vulnerability · Source |
| CVE-2025-9901 | suse_vex | SUSE CVE CVE-2025-9901 | known affected: 391 known not affected: 1 | 2026-07-25T01:08:59+00:00 | Vulnerability · Source |
| CVE-2025-10532 | suse_vex | SUSE CVE CVE-2025-10532 | known affected: 37 recommended: 187 | 2026-07-25T01:08:54+00:00 | Vulnerability · Source |
| CVE-2025-11713 | suse_vex | SUSE CVE CVE-2025-11713 | known affected: 70 recommended: 180 | 2026-07-25T01:08:46+00:00 | Vulnerability · Source |
| CVE-2025-11714 | suse_vex | SUSE CVE CVE-2025-11714 | known affected: 70 recommended: 185 | 2026-07-25T01:08:44+00:00 | Vulnerability · Source |
| CVE-2025-11715 | suse_vex | SUSE CVE CVE-2025-11715 | known affected: 70 recommended: 185 | 2026-07-25T01:08:43+00:00 | Vulnerability · Source |
| CVE-2025-11731 | suse_vex | SUSE CVE CVE-2025-11731 | known affected: 435 recommended: 143 | 2026-07-25T01:08:41+00:00 | Vulnerability · Source |
| CVE-2025-12199 | suse_vex | SUSE CVE CVE-2025-12199 | known not affected: 53 | 2026-07-25T01:08:38+00:00 | Vulnerability · Source |
| CVE-2025-12464 | suse_vex | SUSE CVE CVE-2025-12464 | known affected: 614 known not affected: 394 recommended: 1145 | 2026-07-25T01:08:36+00:00 | Vulnerability · Source |
| CVE-2025-12816 | suse_vex | SUSE CVE CVE-2025-12816 | known affected: 116 known not affected: 381 recommended: 115 | 2026-07-25T01:08:34+00:00 | Vulnerability · Source |