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-2023-43804 | suse_vex | SUSE CVE CVE-2023-43804 | known affected: 253 recommended: 447 | 2026-07-31T01:28:52+00:00 | Vulnerability · Source |
| CVE-2023-52740 | suse_vex | SUSE CVE CVE-2023-52740 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-31T01:28:36+00:00 | Vulnerability · Source |
| CVE-2023-52928 | suse_vex | SUSE CVE CVE-2023-52928 | known affected: 369 known not affected: 294 recommended: 124 | 2026-07-31T01:28:31+00:00 | Vulnerability · Source |
| CVE-2023-53018 | suse_vex | SUSE CVE CVE-2023-53018 | known affected: 369 known not affected: 294 recommended: 124 | 2026-07-31T01:28:29+00:00 | Vulnerability · Source |
| CVE-2023-53298 | suse_vex | SUSE CVE CVE-2023-53298 | known affected: 462 known not affected: 187 recommended: 243 | 2026-07-31T01:28:22+00:00 | Vulnerability · Source |
| CVE-2023-53345 | suse_vex | SUSE CVE CVE-2023-53345 | known not affected: 416 | 2026-07-31T01:28:21+00:00 | Vulnerability · Source |
| CVE-2023-53470 | suse_vex | SUSE CVE CVE-2023-53470 | known affected: 106 known not affected: 310 | 2026-07-31T01:28:18+00:00 | Vulnerability · Source |
| CVE-2023-53802 | suse_vex | SUSE CVE CVE-2023-53802 | known affected: 476 known not affected: 182 recommended: 219 | 2026-07-31T01:28:14+00:00 | Vulnerability · Source |
| CVE-2023-53845 | suse_vex | SUSE CVE CVE-2023-53845 | known affected: 476 known not affected: 214 recommended: 196 | 2026-07-31T01:28:12+00:00 | Vulnerability · Source |
| CVE-2023-53986 | suse_vex | SUSE CVE CVE-2023-53986 | known affected: 167 known not affected: 286 | 2026-07-31T01:28:10+00:00 | Vulnerability · Source |
| CVE-2026-9029 | redhat_vex | grafana: Grafana: Arbitrary code execution and information disclosure via Cross-Site Scripting in geomap panel | known not affected: 31 | 2026-07-31T01:28:09+00:00 | Vulnerability · Source |
| CVE-2024-8250 | suse_vex | SUSE CVE CVE-2024-8250 | known affected: 158 recommended: 159 | 2026-07-31T01:28:00+00:00 | Vulnerability · Source |
| CVE-2024-9395 | suse_vex | SUSE CVE CVE-2024-9395 | known affected: 29 recommended: 9 | 2026-07-31T01:27:58+00:00 | Vulnerability · Source |
| CVE-2024-11699 | suse_vex | SUSE CVE CVE-2024-11699 | known affected: 29 recommended: 227 | 2026-07-31T01:27:45+00:00 | Vulnerability · Source |
| CVE-2024-11706 | suse_vex | SUSE CVE CVE-2024-11706 | known affected: 29 recommended: 9 | 2026-07-31T01:27:43+00:00 | Vulnerability · Source |
| CVE-2024-21537 | suse_vex | SUSE CVE CVE-2024-21537 | known not affected: 144 | 2026-07-31T01:27:39+00:00 | Vulnerability · Source |
| CVE-2024-21635 | suse_vex | SUSE CVE CVE-2024-21635 | No product status | 2026-07-31T01:27:37+00:00 | Vulnerability · Source |
| CVE-2024-29507 | suse_vex | SUSE CVE CVE-2024-29507 | known not affected: 122 | 2026-07-31T01:27:21+00:00 | Vulnerability · Source |
| CVE-2024-30204 | suse_vex | SUSE CVE CVE-2024-30204 | known affected: 77 known not affected: 51 recommended: 173 | 2026-07-31T01:27:18+00:00 | Vulnerability · Source |
| CVE-2024-31074 | suse_vex | SUSE CVE CVE-2024-31074 | known affected: 8 known not affected: 2 recommended: 126 | 2026-07-31T01:27:15+00:00 | Vulnerability · Source |
| CVE-2024-36932 | suse_vex | SUSE CVE CVE-2024-36932 | known not affected: 330 recommended: 59 | 2026-07-31T01:26:50+00:00 | Vulnerability · Source |
| CVE-2024-38796 | suse_vex | SUSE CVE CVE-2024-38796 | known affected: 241 recommended: 3 | 2026-07-31T01:26:45+00:00 | Vulnerability · Source |
| CVE-2024-41935 | suse_vex | SUSE CVE CVE-2024-41935 | known not affected: 453 | 2026-07-31T01:26:39+00:00 | Vulnerability · Source |
| CVE-2024-47175 | suse_vex | SUSE CVE CVE-2024-47175 | known affected: 578 known not affected: 92 recommended: 429 | 2026-07-31T01:26:15+00:00 | Vulnerability · Source |
| CVE-2024-48875 | suse_vex | SUSE CVE CVE-2024-48875 | known not affected: 461 | 2026-07-31T01:26:08+00:00 | Vulnerability · Source |
| CVE-2024-49963 | suse_vex | SUSE CVE CVE-2024-49963 | known affected: 571 known not affected: 55 recommended: 667 | 2026-07-31T01:25:59+00:00 | Vulnerability · Source |
| CVE-2024-50036 | suse_vex | SUSE CVE CVE-2024-50036 | known affected: 706 known not affected: 42 recommended: 356 | 2026-07-31T01:25:50+00:00 | Vulnerability · Source |
| CVE-2024-50072 | suse_vex | SUSE CVE CVE-2024-50072 | known not affected: 462 recommended: 6 | 2026-07-31T01:25:46+00:00 | Vulnerability · Source |
| CVE-2024-50193 | suse_vex | SUSE CVE CVE-2024-50193 | known not affected: 439 recommended: 6 | 2026-07-31T01:25:39+00:00 | Vulnerability · Source |
| CVE-2024-50272 | suse_vex | SUSE CVE CVE-2024-50272 | known affected: 675 known not affected: 60 recommended: 379 | 2026-07-31T01:25:35+00:00 | Vulnerability · Source |
| CVE-2024-52560 | suse_vex | SUSE CVE CVE-2024-52560 | known not affected: 461 | 2026-07-31T01:25:33+00:00 | Vulnerability · Source |
| CVE-2024-53050 | suse_vex | SUSE CVE CVE-2024-53050 | known affected: 596 known not affected: 36 recommended: 353 | 2026-07-31T01:25:31+00:00 | Vulnerability · Source |
| CVE-2024-53052 | suse_vex | SUSE CVE CVE-2024-53052 | known affected: 535 known not affected: 106 recommended: 620 | 2026-07-31T01:25:29+00:00 | Vulnerability · Source |
| CVE-2024-53060 | suse_vex | SUSE CVE CVE-2024-53060 | known affected: 358 known not affected: 287 recommended: 622 | 2026-07-31T01:25:28+00:00 | Vulnerability · Source |
| CVE-2024-53124 | suse_vex | SUSE CVE CVE-2024-53124 | known affected: 721 known not affected: 6 recommended: 525 | 2026-07-31T01:25:20+00:00 | Vulnerability · Source |
| CVE-2024-53130 | suse_vex | SUSE CVE CVE-2024-53130 | known affected: 629 known not affected: 82 recommended: 420 | 2026-07-31T01:25:18+00:00 | Vulnerability · Source |
| CVE-2024-53140 | suse_vex | SUSE CVE CVE-2024-53140 | known affected: 720 known not affected: 6 recommended: 382 | 2026-07-31T01:25:16+00:00 | Vulnerability · Source |
| CVE-2024-53412 | suse_vex | SUSE CVE CVE-2024-53412 | No product status | 2026-07-31T01:25:01+00:00 | Vulnerability · Source |
| CVE-2024-53687 | suse_vex | SUSE CVE CVE-2024-53687 | known not affected: 275 | 2026-07-31T01:24:57+00:00 | Vulnerability · Source |
| CVE-2024-53690 | suse_vex | SUSE CVE CVE-2024-53690 | known affected: 364 known not affected: 333 recommended: 411 | 2026-07-31T01:24:55+00:00 | Vulnerability · Source |
| CVE-2024-56557 | suse_vex | SUSE CVE CVE-2024-56557 | known affected: 423 known not affected: 295 recommended: 464 | 2026-07-31T01:24:47+00:00 | Vulnerability · Source |
| CVE-2024-56559 | suse_vex | SUSE CVE CVE-2024-56559 | known not affected: 545 | 2026-07-31T01:24:44+00:00 | Vulnerability · Source |
| CVE-2024-56564 | suse_vex | SUSE CVE CVE-2024-56564 | known not affected: 545 | 2026-07-31T01:24:43+00:00 | Vulnerability · Source |
| CVE-2024-56565 | suse_vex | SUSE CVE CVE-2024-56565 | known not affected: 545 | 2026-07-31T01:24:41+00:00 | Vulnerability · Source |
| CVE-2024-56581 | suse_vex | SUSE CVE CVE-2024-56581 | known affected: 267 known not affected: 300 | 2026-07-31T01:24:39+00:00 | Vulnerability · Source |
| CVE-2024-56585 | suse_vex | SUSE CVE CVE-2024-56585 | known not affected: 545 | 2026-07-31T01:24:37+00:00 | Vulnerability · Source |
| CVE-2024-56586 | suse_vex | SUSE CVE CVE-2024-56586 | known not affected: 545 | 2026-07-31T01:24:35+00:00 | Vulnerability · Source |
| CVE-2024-56595 | suse_vex | SUSE CVE CVE-2024-56595 | known affected: 597 known not affected: 182 recommended: 411 | 2026-07-31T01:24:31+00:00 | Vulnerability · Source |
| CVE-2024-56596 | suse_vex | SUSE CVE CVE-2024-56596 | known affected: 545 known not affected: 224 recommended: 411 | 2026-07-31T01:24:29+00:00 | Vulnerability · Source |
| CVE-2024-56598 | suse_vex | SUSE CVE CVE-2024-56598 | known affected: 405 known not affected: 286 recommended: 557 | 2026-07-31T01:24:27+00:00 | Vulnerability · Source |