VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289782 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-52990 | suse_vex | SUSE CVE CVE-2023-52990 | known not affected: 344 | 2026-08-06T01:58:17+00:00 | Vulnerability · Source |
| CVE-2024-0211 | suse_vex | SUSE CVE CVE-2024-0211 | known not affected: 326 recommended: 84 | 2026-08-06T01:56:14+00:00 | Vulnerability · Source |
| CVE-2024-0397 | suse_vex | SUSE CVE CVE-2024-0397 | known affected: 454 known not affected: 258 recommended: 653 | 2026-08-06T01:56:13+00:00 | Vulnerability · Source |
| CVE-2024-0985 | suse_vex | SUSE CVE CVE-2024-0985 | known affected: 548 known not affected: 450 recommended: 1354 | 2026-08-06T01:56:10+00:00 | Vulnerability · Source |
| CVE-2024-2609 | suse_vex | SUSE CVE CVE-2024-2609 | known affected: 41 recommended: 212 | 2026-08-06T01:56:07+00:00 | Vulnerability · Source |
| CVE-2024-2955 | suse_vex | SUSE CVE CVE-2024-2955 | known not affected: 245 recommended: 84 | 2026-08-06T01:56:04+00:00 | Vulnerability · Source |
| CVE-2024-5642 | suse_vex | SUSE CVE CVE-2024-5642 | known affected: 389 known not affected: 205 recommended: 575 | 2026-08-06T01:56:00+00:00 | Vulnerability · Source |
| CVE-2024-6387 | suse_vex | SUSE CVE CVE-2024-6387 | known affected: 394 known not affected: 391 recommended: 130 | 2026-08-06T01:55:56+00:00 | Vulnerability · Source |
| CVE-2024-9264 | suse_vex | SUSE CVE CVE-2024-9264 | known not affected: 2 recommended: 25 | 2026-08-06T01:55:49+00:00 | Vulnerability · Source |
| CVE-2024-9476 | suse_vex | SUSE CVE CVE-2024-9476 | known not affected: 2 recommended: 22 | 2026-08-06T01:55:45+00:00 | Vulnerability · Source |
| CVE-2024-10979 | suse_vex | SUSE CVE CVE-2024-10979 | known affected: 645 recommended: 1904 | 2026-08-06T01:55:42+00:00 | Vulnerability · Source |
| CVE-2024-11187 | suse_vex | SUSE CVE CVE-2024-11187 | known affected: 453 known not affected: 1 recommended: 410 | 2026-08-06T01:55:40+00:00 | Vulnerability · Source |
| CVE-2024-12747 | suse_vex | SUSE CVE CVE-2024-12747 | known affected: 415 recommended: 52 | 2026-08-06T01:55:36+00:00 | Vulnerability · Source |
| CVE-2024-20918 | suse_vex | SUSE CVE CVE-2024-20918 | known affected: 497 known not affected: 178 recommended: 883 | 2026-08-06T01:55:32+00:00 | Vulnerability · Source |
| CVE-2024-20921 | suse_vex | SUSE CVE CVE-2024-20921 | known affected: 497 known not affected: 178 recommended: 883 | 2026-08-06T01:55:30+00:00 | Vulnerability · Source |
| CVE-2024-21094 | suse_vex | SUSE CVE CVE-2024-21094 | known affected: 464 known not affected: 37 recommended: 827 | 2026-08-06T01:55:28+00:00 | Vulnerability · Source |
| CVE-2024-24577 | suse_vex | SUSE CVE CVE-2024-24577 | known affected: 351 recommended: 565 | 2026-08-06T01:55:23+00:00 | Vulnerability · Source |
| CVE-2024-27856 | suse_vex | SUSE CVE CVE-2024-27856 | known affected: 88 recommended: 603 | 2026-08-06T01:54:03+00:00 | Vulnerability · Source |
| CVE-2024-40896 | suse_vex | SUSE CVE CVE-2024-40896 | known affected: 394 known not affected: 590 recommended: 119 | 2026-08-06T01:52:34+00:00 | Vulnerability · Source |
| CVE-2024-45774 | suse_vex | SUSE CVE CVE-2024-45774 | known affected: 485 recommended: 418 | 2026-08-06T01:51:03+00:00 | Vulnerability · Source |
| CVE-2024-45780 | suse_vex | SUSE CVE CVE-2024-45780 | known affected: 485 recommended: 408 | 2026-08-06T01:51:01+00:00 | Vulnerability · Source |
| CVE-2024-47535 | suse_vex | SUSE CVE CVE-2024-47535 | known affected: 394 known not affected: 33 recommended: 62 | 2026-08-06T01:50:28+00:00 | Vulnerability · Source |
| CVE-2024-47554 | suse_vex | SUSE CVE CVE-2024-47554 | known affected: 15 known not affected: 11 recommended: 41 | 2026-08-06T01:50:27+00:00 | Vulnerability · Source |
| CVE-2024-52615 | suse_vex | SUSE CVE CVE-2024-52615 | known affected: 835 recommended: 502 | 2026-08-06T01:48:56+00:00 | Vulnerability · Source |
| CVE-2024-54658 | suse_vex | SUSE CVE CVE-2024-54658 | known affected: 88 recommended: 627 | 2026-08-06T01:48:14+00:00 | Vulnerability · Source |
| CVE-2024-56566 | suse_vex | SUSE CVE CVE-2024-56566 | known affected: 697 known not affected: 62 recommended: 406 | 2026-08-06T01:48:05+00:00 | Vulnerability · Source |
| CVE-2024-56659 | suse_vex | SUSE CVE CVE-2024-56659 | known affected: 733 known not affected: 36 recommended: 363 | 2026-08-06T01:47:48+00:00 | Vulnerability · Source |
| CVE-2025-0620 | suse_vex | SUSE CVE CVE-2025-0620 | known affected: 394 known not affected: 1227 recommended: 193 | 2026-08-06T01:47:01+00:00 | Vulnerability · Source |
| CVE-2025-0678 | suse_vex | SUSE CVE CVE-2025-0678 | known affected: 424 recommended: 408 | 2026-08-06T01:46:59+00:00 | Vulnerability · Source |
| CVE-2025-0840 | suse_vex | SUSE CVE CVE-2025-0840 | known affected: 470 recommended: 521 | 2026-08-06T01:46:57+00:00 | Vulnerability · Source |
| CVE-2025-1180 | suse_vex | SUSE CVE CVE-2025-1180 | known affected: 436 known not affected: 108 recommended: 521 | 2026-08-06T01:46:54+00:00 | Vulnerability · Source |
| CVE-2025-1182 | suse_vex | SUSE CVE CVE-2025-1182 | known affected: 470 recommended: 521 | 2026-08-06T01:46:52+00:00 | Vulnerability · Source |
| CVE-2025-1365 | suse_vex | SUSE CVE CVE-2025-1365 | known not affected: 428 recommended: 13 | 2026-08-06T01:46:50+00:00 | Vulnerability · Source |
| CVE-2025-3277 | suse_vex | SUSE CVE CVE-2025-3277 | known affected: 132 known not affected: 13 recommended: 201 | 2026-08-06T01:46:47+00:00 | Vulnerability · Source |
| CVE-2025-3454 | suse_vex | SUSE CVE CVE-2025-3454 | known affected: 1 recommended: 25 | 2026-08-06T01:46:45+00:00 | Vulnerability · Source |
| CVE-2025-4207 | suse_vex | SUSE CVE CVE-2025-4207 | known affected: 563 known not affected: 424 recommended: 1294 | 2026-08-06T01:46:42+00:00 | Vulnerability · Source |
| CVE-2025-5222 | suse_vex | SUSE CVE CVE-2025-5222 | known affected: 460 known not affected: 284 recommended: 222 | 2026-08-06T01:46:38+00:00 | Vulnerability · Source |
| CVE-2025-5244 | suse_vex | SUSE CVE CVE-2025-5244 | known affected: 457 recommended: 524 | 2026-08-06T01:46:37+00:00 | Vulnerability · Source |
| CVE-2025-5399 | suse_vex | SUSE CVE CVE-2025-5399 | known affected: 394 known not affected: 127 recommended: 83 | 2026-08-06T01:46:34+00:00 | Vulnerability · Source |
| CVE-2025-6297 | suse_vex | SUSE CVE CVE-2025-6297 | known affected: 60 recommended: 55 | 2026-08-06T01:46:29+00:00 | Vulnerability · Source |
| CVE-2025-8677 | suse_vex | SUSE CVE CVE-2025-8677 | known affected: 394 known not affected: 282 recommended: 96 | 2026-08-06T01:46:24+00:00 | Vulnerability · Source |
| CVE-2025-8713 | suse_vex | SUSE CVE CVE-2025-8713 | known affected: 555 known not affected: 406 recommended: 1325 | 2026-08-06T01:46:22+00:00 | Vulnerability · Source |
| CVE-2025-8715 | suse_vex | SUSE CVE CVE-2025-8715 | known affected: 555 known not affected: 406 recommended: 1358 | 2026-08-06T01:46:21+00:00 | Vulnerability · Source |
| CVE-2025-9817 | suse_vex | SUSE CVE CVE-2025-9817 | known not affected: 212 recommended: 255 | 2026-08-06T01:46:18+00:00 | Vulnerability · Source |
| CVE-2025-10911 | suse_vex | SUSE CVE CVE-2025-10911 | known affected: 395 recommended: 261 | 2026-08-06T01:46:15+00:00 | Vulnerability · Source |
| CVE-2025-11083 | suse_vex | SUSE CVE CVE-2025-11083 | known affected: 444 known not affected: 24 recommended: 548 | 2026-08-06T01:46:13+00:00 | Vulnerability · Source |
| CVE-2025-11414 | suse_vex | SUSE CVE CVE-2025-11414 | known affected: 445 known not affected: 23 recommended: 521 | 2026-08-06T01:46:11+00:00 | Vulnerability · Source |
| CVE-2025-11495 | suse_vex | SUSE CVE CVE-2025-11495 | known affected: 444 known not affected: 1 recommended: 521 | 2026-08-06T01:46:10+00:00 | Vulnerability · Source |
| CVE-2025-11561 | suse_vex | SUSE CVE CVE-2025-11561 | known affected: 210 recommended: 1039 | 2026-08-06T01:46:08+00:00 | Vulnerability · Source |
| CVE-2025-12748 | suse_vex | SUSE CVE CVE-2025-12748 | known affected: 1119 recommended: 591 | 2026-08-06T01:46:06+00:00 | Vulnerability · Source |