VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286450 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-45802 | suse_vex | SUSE CVE CVE-2024-45802 | known affected: 34 known not affected: 7 recommended: 9 | 2026-07-27T17:13:23+00:00 | Vulnerability · Source |
| CVE-2024-46693 | suse_vex | SUSE CVE CVE-2024-46693 | known affected: 394 known not affected: 347 recommended: 330 | 2026-07-27T17:13:21+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-46956 | suse_vex | SUSE CVE CVE-2024-46956 | known affected: 31 known not affected: 37 recommended: 132 | 2026-07-27T17:13:16+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-52532 | suse_vex | SUSE CVE CVE-2024-52532 | known affected: 55 recommended: 285 | 2026-07-27T17:13:03+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-7519 | suse_vex | SUSE CVE CVE-2025-7519 | known affected: 442 recommended: 189 | 2026-07-27T17:12:16+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-13837 | suse_vex | SUSE CVE CVE-2025-13837 | known affected: 592 known not affected: 92 recommended: 668 | 2026-07-27T17:11:47+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-22024 | suse_vex | SUSE CVE CVE-2025-22024 | known not affected: 346 recommended: 53 | 2026-07-27T17:11:31+00:00 | Vulnerability · Source |
| CVE-2025-26625 | suse_vex | SUSE CVE CVE-2025-26625 | known affected: 12 recommended: 33 | 2026-07-27T17:11:24+00:00 | Vulnerability · Source |
| CVE-2025-27587 | suse_vex | SUSE CVE CVE-2025-27587 | first fixed: 45 known affected: 396 known not affected: 586 recommended: 100 | 2026-07-27T17:11:22+00:00 | Vulnerability · Source |
| CVE-2025-31115 | suse_vex | SUSE CVE CVE-2025-31115 | known affected: 394 known not affected: 173 recommended: 87 | 2026-07-27T17:11:20+00:00 | Vulnerability · Source |
| CVE-2025-32906 | suse_vex | SUSE CVE CVE-2025-32906 | known affected: 21 recommended: 246 | 2026-07-27T17:11:18+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 |
| 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-47913 | suse_vex | SUSE CVE CVE-2025-47913 | known affected: 663 recommended: 485 | 2026-07-27T17:10:52+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 |