VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291368 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-26772 | suse_vex | SUSE CVE CVE-2024-26772 | known affected: 454 recommended: 780 | 2026-08-05T01:01:13+00:00 | Vulnerability · Source |
| CVE-2024-26779 | suse_vex | SUSE CVE CVE-2024-26779 | known affected: 489 known not affected: 58 recommended: 644 | 2026-08-05T01:01:11+00:00 | Vulnerability · Source |
| CVE-2024-26795 | suse_vex | SUSE CVE CVE-2024-26795 | known not affected: 353 | 2026-08-05T01:01:05+00:00 | Vulnerability · Source |
| CVE-2024-26800 | suse_vex | SUSE CVE CVE-2024-26800 | known affected: 292 known not affected: 156 recommended: 767 | 2026-08-05T01:01:02+00:00 | Vulnerability · Source |
| CVE-2024-26811 | suse_vex | SUSE CVE CVE-2024-26811 | known affected: 4 known not affected: 471 | 2026-08-05T01:00:58+00:00 | Vulnerability · Source |
| CVE-2024-26822 | suse_vex | SUSE CVE CVE-2024-26822 | known affected: 370 known not affected: 154 recommended: 762 | 2026-08-05T01:00:56+00:00 | Vulnerability · Source |
| CVE-2024-26895 | suse_vex | SUSE CVE CVE-2024-26895 | known affected: 310 known not affected: 278 recommended: 526 | 2026-08-05T01:00:37+00:00 | Vulnerability · Source |
| CVE-2024-26926 | suse_vex | SUSE CVE CVE-2024-26926 | known not affected: 288 | 2026-08-05T01:00:31+00:00 | Vulnerability · Source |
| CVE-2024-26930 | suse_vex | SUSE CVE CVE-2024-26930 | known affected: 269 known not affected: 218 recommended: 1026 | 2026-08-05T01:00:30+00:00 | Vulnerability · Source |
| CVE-2024-26944 | suse_vex | SUSE CVE CVE-2024-26944 | known affected: 394 known not affected: 306 recommended: 446 | 2026-08-05T01:00:27+00:00 | Vulnerability · Source |
| CVE-2024-26952 | suse_vex | SUSE CVE CVE-2024-26952 | known not affected: 442 | 2026-08-05T01:00:24+00:00 | Vulnerability · Source |
| CVE-2024-26954 | suse_vex | SUSE CVE CVE-2024-26954 | known not affected: 330 | 2026-08-05T01:00:22+00:00 | Vulnerability · Source |
| CVE-2024-26961 | suse_vex | SUSE CVE CVE-2024-26961 | known affected: 426 known not affected: 44 recommended: 709 | 2026-08-05T01:00:18+00:00 | Vulnerability · Source |
| CVE-2024-26969 | suse_vex | SUSE CVE CVE-2024-26969 | known affected: 453 known not affected: 181 recommended: 531 | 2026-08-05T01:00:14+00:00 | Vulnerability · Source |
| CVE-2024-26971 | suse_vex | SUSE CVE CVE-2024-26971 | known not affected: 330 | 2026-08-05T01:00:13+00:00 | Vulnerability · Source |
| CVE-2024-26996 | suse_vex | SUSE CVE CVE-2024-26996 | known affected: 521 known not affected: 14 recommended: 745 | 2026-08-05T01:00:07+00:00 | Vulnerability · Source |
| CVE-2024-27389 | suse_vex | SUSE CVE CVE-2024-27389 | known affected: 271 known not affected: 150 recommended: 824 | 2026-08-05T00:59:45+00:00 | Vulnerability · Source |
| CVE-2024-27413 | suse_vex | SUSE CVE CVE-2024-27413 | known affected: 269 known not affected: 98 recommended: 949 | 2026-08-05T00:59:37+00:00 | Vulnerability · Source |
| CVE-2024-35785 | suse_vex | SUSE CVE CVE-2024-35785 | known not affected: 330 | 2026-08-05T00:59:25+00:00 | Vulnerability · Source |
| CVE-2024-35787 | suse_vex | SUSE CVE CVE-2024-35787 | known not affected: 536 | 2026-08-05T00:59:23+00:00 | Vulnerability · Source |
| CVE-2024-35843 | suse_vex | SUSE CVE CVE-2024-35843 | known affected: 421 known not affected: 311 recommended: 358 | 2026-08-05T00:59:11+00:00 | Vulnerability · Source |
| CVE-2024-35856 | suse_vex | SUSE CVE CVE-2024-35856 | known not affected: 330 recommended: 59 | 2026-08-05T00:59:06+00:00 | Vulnerability · Source |
| CVE-2024-35861 | suse_vex | SUSE CVE CVE-2024-35861 | known affected: 269 known not affected: 107 recommended: 1094 | 2026-08-05T00:59:03+00:00 | Vulnerability · Source |
| CVE-2024-35874 | suse_vex | SUSE CVE CVE-2024-35874 | known not affected: 330 | 2026-08-05T00:58:53+00:00 | Vulnerability · Source |
| CVE-2024-35882 | suse_vex | SUSE CVE CVE-2024-35882 | known not affected: 330 | 2026-08-05T00:58:46+00:00 | Vulnerability · Source |
| CVE-2024-35887 | suse_vex | SUSE CVE CVE-2024-35887 | known affected: 521 known not affected: 6 recommended: 760 | 2026-08-05T00:58:44+00:00 | Vulnerability · Source |
| CVE-2024-35898 | suse_vex | SUSE CVE CVE-2024-35898 | known affected: 488 known not affected: 111 recommended: 705 | 2026-08-05T00:58:33+00:00 | Vulnerability · Source |
| CVE-2024-35920 | suse_vex | SUSE CVE CVE-2024-35920 | known not affected: 330 | 2026-08-05T00:58:27+00:00 | Vulnerability · Source |
| CVE-2024-35932 | suse_vex | SUSE CVE CVE-2024-35932 | known affected: 315 known not affected: 187 recommended: 745 | 2026-08-05T00:58:23+00:00 | Vulnerability · Source |
| CVE-2024-35951 | suse_vex | SUSE CVE CVE-2024-35951 | known affected: 394 known not affected: 121 recommended: 675 | 2026-08-05T00:58:19+00:00 | Vulnerability · Source |
| CVE-2024-35967 | suse_vex | SUSE CVE CVE-2024-35967 | known affected: 515 known not affected: 12 recommended: 802 | 2026-08-05T00:58:14+00:00 | Vulnerability · Source |
| CVE-2024-35968 | suse_vex | SUSE CVE CVE-2024-35968 | known not affected: 330 | 2026-08-05T00:58:13+00:00 | Vulnerability · Source |
| CVE-2024-35993 | suse_vex | SUSE CVE CVE-2024-35993 | known not affected: 330 | 2026-08-05T00:58:06+00:00 | Vulnerability · Source |
| CVE-2024-35994 | suse_vex | SUSE CVE CVE-2024-35994 | known not affected: 330 | 2026-08-05T00:58:04+00:00 | Vulnerability · Source |
| CVE-2024-36016 | suse_vex | SUSE CVE CVE-2024-36016 | known affected: 431 recommended: 804 | 2026-08-05T00:57:59+00:00 | Vulnerability · Source |
| CVE-2024-36018 | suse_vex | SUSE CVE CVE-2024-36018 | known affected: 394 known not affected: 270 recommended: 362 | 2026-08-05T00:57:57+00:00 | Vulnerability · Source |
| CVE-2024-36288 | suse_vex | SUSE CVE CVE-2024-36288 | known affected: 330 known not affected: 175 recommended: 728 | 2026-08-05T00:57:53+00:00 | Vulnerability · Source |
| CVE-2024-36884 | suse_vex | SUSE CVE CVE-2024-36884 | known not affected: 330 recommended: 59 | 2026-08-05T00:57:50+00:00 | Vulnerability · Source |
| CVE-2024-36894 | suse_vex | SUSE CVE CVE-2024-36894 | known affected: 365 known not affected: 6 recommended: 1026 | 2026-08-05T00:57:47+00:00 | Vulnerability · Source |
| CVE-2024-36958 | suse_vex | SUSE CVE CVE-2024-36958 | known not affected: 330 | 2026-08-05T00:57:35+00:00 | Vulnerability · Source |
| CVE-2024-36960 | suse_vex | SUSE CVE CVE-2024-36960 | known affected: 550 known not affected: 33 recommended: 760 | 2026-08-05T00:57:33+00:00 | Vulnerability · Source |
| CVE-2024-36962 | suse_vex | SUSE CVE CVE-2024-36962 | known affected: 394 known not affected: 235 recommended: 592 | 2026-08-05T00:57:32+00:00 | Vulnerability · Source |
| CVE-2024-38544 | suse_vex | SUSE CVE CVE-2024-38544 | known affected: 501 known not affected: 37 recommended: 755 | 2026-08-05T00:57:17+00:00 | Vulnerability · Source |
| CVE-2024-38564 | suse_vex | SUSE CVE CVE-2024-38564 | known affected: 317 known not affected: 169 recommended: 809 | 2026-08-05T00:57:14+00:00 | Vulnerability · Source |
| CVE-2024-38568 | suse_vex | SUSE CVE CVE-2024-38568 | known affected: 357 known not affected: 230 recommended: 656 | 2026-08-05T00:57:12+00:00 | Vulnerability · Source |
| CVE-2024-38599 | suse_vex | SUSE CVE CVE-2024-38599 | known affected: 397 known not affected: 142 recommended: 752 | 2026-08-05T00:56:58+00:00 | Vulnerability · Source |
| CVE-2024-38614 | suse_vex | SUSE CVE CVE-2024-38614 | known not affected: 318 | 2026-08-05T00:56:53+00:00 | Vulnerability · Source |
| CVE-2024-38620 | suse_vex | SUSE CVE CVE-2024-38620 | known not affected: 523 recommended: 59 | 2026-08-05T00:56:52+00:00 | Vulnerability · Source |
| CVE-2024-39292 | suse_vex | SUSE CVE CVE-2024-39292 | known not affected: 318 | 2026-08-05T00:56:47+00:00 | Vulnerability · Source |
| CVE-2024-39463 | suse_vex | SUSE CVE CVE-2024-39463 | known affected: 295 known not affected: 185 recommended: 784 | 2026-08-05T00:56:45+00:00 | Vulnerability · Source |