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-2024-26780 | suse_vex | SUSE CVE CVE-2024-26780 | known not affected: 266 recommended: 358 | 2026-07-27T17:14:34+00:00 | Vulnerability · Source |
| CVE-2024-27035 | suse_vex | SUSE CVE CVE-2024-27035 | known not affected: 283 | 2026-07-27T17:14:26+00:00 | Vulnerability · Source |
| CVE-2024-34027 | suse_vex | SUSE CVE CVE-2024-34027 | known not affected: 226 | 2026-07-27T17:14:18+00:00 | Vulnerability · Source |
| CVE-2024-35858 | suse_vex | SUSE CVE CVE-2024-35858 | known not affected: 283 | 2026-07-27T17:14:14+00:00 | Vulnerability · Source |
| CVE-2024-35876 | suse_vex | SUSE CVE CVE-2024-35876 | recommended: 20 | 2026-07-27T17:14:11+00:00 | Vulnerability · Source |
| CVE-2024-35919 | suse_vex | SUSE CVE CVE-2024-35919 | known not affected: 283 | 2026-07-27T17:14:09+00:00 | Vulnerability · Source |
| CVE-2024-35962 | suse_vex | SUSE CVE CVE-2024-35962 | known not affected: 223 recommended: 677 | 2026-07-27T17:14:07+00:00 | Vulnerability · Source |
| CVE-2024-38591 | suse_vex | SUSE CVE CVE-2024-38591 | known affected: 449 known not affected: 90 recommended: 656 | 2026-07-27T17:13:57+00:00 | Vulnerability · Source |
| CVE-2024-39499 | suse_vex | SUSE CVE CVE-2024-39499 | known affected: 518 known not affected: 18 recommended: 714 | 2026-07-27T17:13:51+00:00 | Vulnerability · Source |
| CVE-2024-40899 | suse_vex | SUSE CVE CVE-2024-40899 | known affected: 394 known not affected: 252 recommended: 333 | 2026-07-27T17:13:50+00:00 | Vulnerability · Source |
| CVE-2024-41064 | suse_vex | SUSE CVE CVE-2024-41064 | known affected: 453 known not affected: 8 recommended: 734 | 2026-07-27T17:13:45+00:00 | Vulnerability · Source |
| CVE-2024-42084 | suse_vex | SUSE CVE CVE-2024-42084 | known affected: 443 known not affected: 28 recommended: 20 | 2026-07-27T17:13:43+00:00 | Vulnerability · Source |
| CVE-2024-44943 | suse_vex | SUSE CVE CVE-2024-44943 | known not affected: 271 | 2026-07-27T17:13:32+00:00 | Vulnerability · Source |
| CVE-2024-44953 | suse_vex | SUSE CVE CVE-2024-44953 | known not affected: 270 | 2026-07-27T17:13:30+00:00 | Vulnerability · Source |
| CVE-2024-44976 | suse_vex | SUSE CVE CVE-2024-44976 | known not affected: 270 | 2026-07-27T17:13:29+00:00 | Vulnerability · Source |
| CVE-2026-41324 | redhat_vex | basic-ftp: basic-ftp: Denial of Service via unbounded memory growth from malicious directory listings | known affected: 37 known not affected: 1 | 2026-07-27T17:13:28+00:00 | Vulnerability · Source |
| CVE-2026-48522 | redhat_vex | python-pyjwt: PyJWT: Server-Side Request Forgery (SSRF) via uncontrolled URL fetching in PyJWKClient | known affected: 190 known not affected: 8 | 2026-07-27T17:13:27+00:00 | Vulnerability · Source |
| CVE-2024-44988 | suse_vex | SUSE CVE CVE-2024-44988 | known affected: 474 known not affected: 133 recommended: 645 | 2026-07-27T17:13:27+00:00 | Vulnerability · Source |
| CVE-2026-48523 | redhat_vex | python-pyjwt: PyJWT: Verifier-side algorithm bypass leads to unauthorized information access | known affected: 178 known not affected: 20 | 2026-07-27T17:13:26+00:00 | Vulnerability · Source |
| CVE-2024-45018 | suse_vex | SUSE CVE CVE-2024-45018 | known affected: 441 known not affected: 166 recommended: 695 | 2026-07-27T17:13:25+00:00 | Vulnerability · Source |
| CVE-2024-46789 | suse_vex | SUSE CVE CVE-2024-46789 | known not affected: 271 | 2026-07-27T17:13:18+00:00 | Vulnerability · Source |
| CVE-2024-47611 | suse_vex | SUSE CVE CVE-2024-47611 | known not affected: 236 | 2026-07-27T17:13:14+00:00 | Vulnerability · Source |
| CVE-2026-48525 | redhat_vex | python-pyjwt: PyJWT: Denial of Service via processing of crafted detached JWS tokens | known affected: 190 known not affected: 8 | 2026-07-27T17:13:12+00:00 | Vulnerability · Source |
| CVE-2024-50612 | suse_vex | SUSE CVE CVE-2024-50612 | known not affected: 148 recommended: 11 | 2026-07-27T17:13:04+00:00 | Vulnerability · Source |
| CVE-2024-56697 | suse_vex | SUSE CVE CVE-2024-56697 | known not affected: 423 recommended: 112 | 2026-07-27T17:12:44+00:00 | Vulnerability · Source |
| CVE-2025-0244 | suse_vex | SUSE CVE CVE-2025-0244 | known affected: 57 recommended: 5 | 2026-07-27T17:12:33+00:00 | Vulnerability · Source |
| CVE-2025-0247 | suse_vex | SUSE CVE CVE-2025-0247 | known affected: 57 recommended: 5 | 2026-07-27T17:12:32+00:00 | Vulnerability · Source |
| CVE-2025-1019 | suse_vex | SUSE CVE CVE-2025-1019 | known affected: 110 recommended: 5 | 2026-07-27T17:12:30+00:00 | Vulnerability · Source |
| CVE-2025-1020 | suse_vex | SUSE CVE CVE-2025-1020 | known not affected: 179 recommended: 5 | 2026-07-27T17:12:29+00:00 | Vulnerability · Source |
| CVE-2025-3034 | suse_vex | SUSE CVE CVE-2025-3034 | known affected: 37 recommended: 5 | 2026-07-27T17:12:27+00:00 | Vulnerability · Source |
| CVE-2025-4083 | suse_vex | SUSE CVE CVE-2025-4083 | known affected: 69 recommended: 113 | 2026-07-27T17:12:23+00:00 | Vulnerability · Source |
| CVE-2025-4090 | suse_vex | SUSE CVE CVE-2025-4090 | known affected: 69 recommended: 5 | 2026-07-27T17:12:22+00:00 | Vulnerability · Source |
| CVE-2025-5272 | suse_vex | SUSE CVE CVE-2025-5272 | known affected: 37 recommended: 5 | 2026-07-27T17:12:20+00:00 | Vulnerability · Source |
| CVE-2025-8177 | suse_vex | SUSE CVE CVE-2025-8177 | known affected: 443 known not affected: 7 recommended: 142 | 2026-07-27T17:12:14+00:00 | Vulnerability · Source |
| CVE-2025-9566 | suse_vex | SUSE CVE CVE-2025-9566 | known affected: 394 recommended: 162 | 2026-07-27T17:12:11+00:00 | Vulnerability · Source |
| CVE-2025-9615 | suse_vex | SUSE CVE CVE-2025-9615 | known affected: 547 recommended: 216 | 2026-07-27T17:12:09+00:00 | Vulnerability · Source |
| CVE-2025-11152 | suse_vex | SUSE CVE CVE-2025-11152 | known not affected: 151 recommended: 5 | 2026-07-27T17:12:05+00:00 | Vulnerability · Source |
| CVE-2025-11621 | suse_vex | SUSE CVE CVE-2025-11621 | recommended: 1 | 2026-07-27T17:12:01+00:00 | Vulnerability · Source |
| CVE-2025-11712 | suse_vex | SUSE CVE CVE-2025-11712 | known affected: 70 recommended: 182 | 2026-07-27T17:12:00+00:00 | Vulnerability · Source |
| CVE-2025-11716 | suse_vex | SUSE CVE CVE-2025-11716 | known affected: 70 recommended: 5 | 2026-07-27T17:11:59+00:00 | Vulnerability · Source |
| CVE-2025-11719 | suse_vex | SUSE CVE CVE-2025-11719 | known affected: 70 recommended: 5 | 2026-07-27T17:11:58+00:00 | Vulnerability · Source |
| CVE-2025-12044 | suse_vex | SUSE CVE CVE-2025-12044 | recommended: 1 | 2026-07-27T17:11:56+00:00 | Vulnerability · Source |
| CVE-2025-13014 | suse_vex | SUSE CVE CVE-2025-13014 | known affected: 14 recommended: 176 | 2026-07-27T17:11:55+00:00 | Vulnerability · Source |
| CVE-2025-13015 | suse_vex | SUSE CVE CVE-2025-13015 | known affected: 14 recommended: 176 | 2026-07-27T17:11:54+00:00 | Vulnerability · Source |
| CVE-2025-13019 | suse_vex | SUSE CVE CVE-2025-13019 | known affected: 14 recommended: 183 | 2026-07-27T17:11:52+00:00 | Vulnerability · Source |
| CVE-2025-13023 | suse_vex | SUSE CVE CVE-2025-13023 | known affected: 14 recommended: 5 | 2026-07-27T17:11:51+00:00 | Vulnerability · Source |
| CVE-2025-14831 | suse_vex | SUSE CVE CVE-2025-14831 | known affected: 537 recommended: 148 | 2026-07-27T17:11:44+00:00 | Vulnerability · Source |
| CVE-2025-21921 | suse_vex | SUSE CVE CVE-2025-21921 | known not affected: 346 recommended: 26 | 2026-07-27T17:11:33+00:00 | Vulnerability · Source |
| CVE-2025-37828 | suse_vex | SUSE CVE CVE-2025-37828 | known affected: 57 known not affected: 338 recommended: 26 | 2026-07-27T17:11:16+00:00 | Vulnerability · Source |
| CVE-2025-38096 | suse_vex | SUSE CVE CVE-2025-38096 | first fixed: 2 known affected: 239 known not affected: 63 recommended: 127 | 2026-07-27T17:11:12+00:00 | Vulnerability · Source |