VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38330 | suse_vex | SUSE CVE CVE-2025-38330 | known not affected: 416 recommended: 69 | 2026-07-27T17:11:09+00:00 | Vulnerability · Source |
| CVE-2025-38658 | suse_vex | SUSE CVE CVE-2025-38658 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-27T17:11:04+00:00 | Vulnerability · Source |
| CVE-2025-39723 | suse_vex | SUSE CVE CVE-2025-39723 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 127 | 2026-07-27T17:11:02+00:00 | Vulnerability · Source |
| CVE-2025-49709 | suse_vex | SUSE CVE CVE-2025-49709 | known affected: 15 known not affected: 97 recommended: 5 | 2026-07-27T17:10:48+00:00 | Vulnerability · Source |
| CVE-2025-53905 | suse_vex | SUSE CVE CVE-2025-53905 | known affected: 515 recommended: 153 | 2026-07-27T17:10:46+00:00 | Vulnerability · Source |
| CVE-2025-53906 | suse_vex | SUSE CVE CVE-2025-53906 | first fixed: 2 known affected: 427 recommended: 245 | 2026-07-27T17:10:45+00:00 | Vulnerability · Source |
| CVE-2025-59353 | suse_vex | SUSE CVE CVE-2025-59353 | recommended: 1 | 2026-07-27T17:10:30+00:00 | Vulnerability · Source |
| CVE-2025-59362 | suse_vex | SUSE CVE CVE-2025-59362 | known affected: 405 recommended: 34 | 2026-07-27T17:10:29+00:00 | Vulnerability · Source |
| CVE-2025-59800 | suse_vex | SUSE CVE CVE-2025-59800 | known affected: 1 known not affected: 123 recommended: 14 | 2026-07-27T17:10:25+00:00 | Vulnerability · Source |
| CVE-2025-64433 | suse_vex | SUSE CVE CVE-2025-64433 | first fixed: 1 known not affected: 70 recommended: 71 | 2026-07-27T17:10:10+00:00 | Vulnerability · Source |
| CVE-2025-64435 | suse_vex | SUSE CVE CVE-2025-64435 | first fixed: 1 known not affected: 70 recommended: 27 | 2026-07-27T17:10:09+00:00 | Vulnerability · Source |
| CVE-2025-69420 | suse_vex | SUSE CVE CVE-2025-69420 | known affected: 406 known not affected: 143 recommended: 427 | 2026-07-27T17:09:50+00:00 | Vulnerability · Source |
| CVE-2025-71147 | suse_vex | SUSE CVE CVE-2025-71147 | first fixed: 2 known affected: 482 known not affected: 129 recommended: 444 | 2026-07-27T17:09:48+00:00 | Vulnerability · Source |
| CVE-2026-0716 | suse_vex | SUSE CVE CVE-2026-0716 | known affected: 104 recommended: 214 | 2026-07-27T17:09:45+00:00 | Vulnerability · Source |
| CVE-2026-0964 | suse_vex | SUSE CVE CVE-2026-0964 | known affected: 465 recommended: 109 | 2026-07-27T17:09:42+00:00 | Vulnerability · Source |
| CVE-2026-0965 | suse_vex | SUSE CVE CVE-2026-0965 | known affected: 465 recommended: 109 | 2026-07-27T17:09:40+00:00 | Vulnerability · Source |
| CVE-2026-0966 | suse_vex | SUSE CVE CVE-2026-0966 | known affected: 465 recommended: 109 | 2026-07-27T17:09:39+00:00 | Vulnerability · Source |
| CVE-2026-0967 | suse_vex | SUSE CVE CVE-2026-0967 | known affected: 465 recommended: 109 | 2026-07-27T17:09:38+00:00 | Vulnerability · Source |
| CVE-2026-3833 | suse_vex | SUSE CVE CVE-2026-3833 | known affected: 466 recommended: 242 | 2026-07-27T17:09:30+00:00 | Vulnerability · Source |
| CVE-2026-4111 | suse_vex | SUSE CVE CVE-2026-4111 | known affected: 443 known not affected: 29 recommended: 75 | 2026-07-27T17:09:28+00:00 | Vulnerability · Source |
| CVE-2026-4437 | suse_vex | SUSE CVE CVE-2026-4437 | first fixed: 1 known affected: 430 known not affected: 278 recommended: 657 | 2026-07-27T17:09:25+00:00 | Vulnerability · Source |
| CVE-2026-4438 | suse_vex | SUSE CVE CVE-2026-4438 | first fixed: 1 known affected: 432 known not affected: 276 recommended: 657 | 2026-07-27T17:09:23+00:00 | Vulnerability · Source |
| CVE-2026-5201 | suse_vex | SUSE CVE CVE-2026-5201 | known affected: 501 known not affected: 281 recommended: 260 | 2026-07-27T17:09:20+00:00 | Vulnerability · Source |
| CVE-2026-5260 | suse_vex | SUSE CVE CVE-2026-5260 | known affected: 466 recommended: 242 | 2026-07-27T17:09:19+00:00 | Vulnerability · Source |
| CVE-2026-5435 | suse_vex | SUSE CVE CVE-2026-5435 | first fixed: 1 known affected: 570 known not affected: 61 recommended: 912 | 2026-07-27T17:09:15+00:00 | Vulnerability · Source |
| CVE-2026-5928 | suse_vex | SUSE CVE CVE-2026-5928 | first fixed: 1 known affected: 532 recommended: 948 | 2026-07-27T17:09:12+00:00 | Vulnerability · Source |
| CVE-2026-6238 | suse_vex | SUSE CVE CVE-2026-6238 | first fixed: 1 known affected: 570 known not affected: 61 recommended: 912 | 2026-07-27T17:09:10+00:00 | Vulnerability · Source |
| CVE-2026-7383 | suse_vex | SUSE CVE CVE-2026-7383 | known affected: 503 known not affected: 84 recommended: 362 | 2026-07-27T17:09:07+00:00 | Vulnerability · Source |
| CVE-2026-9076 | suse_vex | SUSE CVE CVE-2026-9076 | known affected: 503 known not affected: 84 recommended: 362 | 2026-07-27T17:08:58+00:00 | Vulnerability · Source |
| CVE-2026-10517 | suse_vex | SUSE CVE CVE-2026-10517 | No product status | 2026-07-27T17:08:53+00:00 | Vulnerability · Source |
| CVE-2026-14241 | suse_vex | SUSE CVE CVE-2026-14241 | known not affected: 106 | 2026-07-27T17:08:40+00:00 | Vulnerability · Source |
| CVE-2026-21441 | suse_vex | SUSE CVE CVE-2026-21441 | known affected: 370 recommended: 222 | 2026-07-27T17:08:29+00:00 | Vulnerability · Source |
| CVE-2026-48524 | redhat_vex | python-pyjwt: PyJWT: Denial of Service via unverified JSON Web Token key IDs | known affected: 181 known not affected: 8 | 2026-07-27T17:08:24+00:00 | Vulnerability · Source |
| CVE-2026-23490 | suse_vex | SUSE CVE CVE-2026-23490 | known affected: 394 recommended: 254 | 2026-07-27T17:08:23+00:00 | Vulnerability · Source |
| CVE-2026-23745 | suse_vex | SUSE CVE CVE-2026-23745 | known affected: 16 known not affected: 219 recommended: 14 | 2026-07-27T17:08:22+00:00 | Vulnerability · Source |
| CVE-2026-24842 | suse_vex | SUSE CVE CVE-2026-24842 | known not affected: 235 recommended: 18 | 2026-07-27T17:08:19+00:00 | Vulnerability · Source |
| CVE-2026-25679 | suse_vex | SUSE CVE CVE-2026-25679 | known affected: 12 known not affected: 81 recommended: 382 | 2026-07-27T17:08:15+00:00 | Vulnerability · Source |
| CVE-2026-27137 | suse_vex | SUSE CVE CVE-2026-27137 | known not affected: 177 recommended: 159 | 2026-07-27T17:08:06+00:00 | Vulnerability · Source |
| CVE-2026-31579 | suse_vex | SUSE CVE CVE-2026-31579 | first fixed: 2 known affected: 644 known not affected: 65 recommended: 149 | 2026-07-27T17:07:55+00:00 | Vulnerability · Source |
| CVE-2026-31664 | suse_vex | SUSE CVE CVE-2026-31664 | first fixed: 55 known affected: 612 recommended: 275 | 2026-07-27T17:07:53+00:00 | Vulnerability · Source |
| CVE-2026-31670 | suse_vex | SUSE CVE CVE-2026-31670 | first fixed: 55 known affected: 612 recommended: 246 | 2026-07-27T17:07:52+00:00 | Vulnerability · Source |
| CVE-2026-32286 | suse_vex | SUSE CVE CVE-2026-32286 | known affected: 8 recommended: 3 | 2026-07-27T17:07:44+00:00 | Vulnerability · Source |
| CVE-2026-33816 | suse_vex | SUSE CVE CVE-2026-33816 | known not affected: 32 recommended: 8 | 2026-07-27T17:07:32+00:00 | Vulnerability · Source |
| CVE-2026-33845 | suse_vex | SUSE CVE CVE-2026-33845 | known affected: 448 recommended: 251 | 2026-07-27T17:07:31+00:00 | Vulnerability · Source |
| CVE-2026-33846 | suse_vex | SUSE CVE CVE-2026-33846 | known affected: 448 recommended: 251 | 2026-07-27T17:07:30+00:00 | Vulnerability · Source |
| CVE-2026-33997 | suse_vex | SUSE CVE CVE-2026-33997 | known affected: 139 recommended: 70 | 2026-07-27T17:07:28+00:00 | Vulnerability · Source |
| CVE-2026-34040 | suse_vex | SUSE CVE CVE-2026-34040 | known affected: 138 recommended: 64 | 2026-07-27T17:07:27+00:00 | Vulnerability · Source |
| CVE-2026-34180 | suse_vex | SUSE CVE CVE-2026-34180 | known affected: 503 known not affected: 84 recommended: 362 | 2026-07-27T17:07:26+00:00 | Vulnerability · Source |
| CVE-2026-34980 | suse_vex | SUSE CVE CVE-2026-34980 | known affected: 623 recommended: 159 | 2026-07-27T17:07:21+00:00 | Vulnerability · Source |
| CVE-2026-41568 | suse_vex | SUSE CVE CVE-2026-41568 | known affected: 181 | 2026-07-27T17:06:50+00:00 | Vulnerability · Source |