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-54232 | suse_vex | SUSE CVE CVE-2023-54232 | known affected: 212 known not affected: 215 | 2026-08-05T01:02:34+00:00 | Vulnerability · Source |
| CVE-2023-54250 | suse_vex | SUSE CVE CVE-2023-54250 | known not affected: 437 | 2026-08-05T01:02:31+00:00 | Vulnerability · Source |
| CVE-2023-54280 | suse_vex | SUSE CVE CVE-2023-54280 | known affected: 409 known not affected: 258 recommended: 196 | 2026-08-05T01:02:27+00:00 | Vulnerability · Source |
| CVE-2024-0775 | suse_vex | SUSE CVE CVE-2024-0775 | known affected: 287 known not affected: 126 recommended: 811 | 2026-08-05T01:02:18+00:00 | Vulnerability · Source |
| CVE-2024-25260 | suse_vex | SUSE CVE CVE-2024-25260 | known affected: 9 known not affected: 693 | 2026-08-05T01:02:04+00:00 | Vulnerability · Source |
| CVE-2024-26327 | suse_vex | SUSE CVE CVE-2024-26327 | known affected: 394 known not affected: 941 recommended: 318 | 2026-08-05T01:02:02+00:00 | Vulnerability · Source |
| CVE-2024-26581 | suse_vex | SUSE CVE CVE-2024-26581 | known affected: 388 known not affected: 215 recommended: 526 | 2026-08-05T01:02:00+00:00 | Vulnerability · Source |
| CVE-2024-26611 | suse_vex | SUSE CVE CVE-2024-26611 | known affected: 394 known not affected: 355 recommended: 362 | 2026-08-05T01:01:49+00:00 | Vulnerability · Source |
| CVE-2024-26614 | suse_vex | SUSE CVE CVE-2024-26614 | known affected: 345 recommended: 1081 | 2026-08-05T01:01:48+00:00 | Vulnerability · Source |
| CVE-2024-26617 | suse_vex | SUSE CVE CVE-2024-26617 | known not affected: 292 | 2026-08-05T01:01:47+00:00 | Vulnerability · Source |
| CVE-2024-26621 | suse_vex | SUSE CVE CVE-2024-26621 | known not affected: 292 | 2026-08-05T01:01:45+00:00 | Vulnerability · Source |
| CVE-2024-26626 | suse_vex | SUSE CVE CVE-2024-26626 | known not affected: 331 | 2026-08-05T01:01:43+00:00 | Vulnerability · Source |
| CVE-2024-26641 | suse_vex | SUSE CVE CVE-2024-26641 | known affected: 567 known not affected: 66 recommended: 726 | 2026-08-05T01:01:39+00:00 | Vulnerability · Source |
| CVE-2024-26664 | suse_vex | SUSE CVE CVE-2024-26664 | known affected: 384 known not affected: 189 recommended: 581 | 2026-08-05T01:01:34+00:00 | Vulnerability · Source |
| CVE-2024-26666 | suse_vex | SUSE CVE CVE-2024-26666 | known not affected: 307 recommended: 206 | 2026-08-05T01:01:32+00:00 | Vulnerability · Source |
| CVE-2024-26699 | suse_vex | SUSE CVE CVE-2024-26699 | known not affected: 307 recommended: 206 | 2026-08-05T01:01:29+00:00 | Vulnerability · Source |
| CVE-2024-26704 | suse_vex | SUSE CVE CVE-2024-26704 | known affected: 414 known not affected: 6 recommended: 989 | 2026-08-05T01:01:28+00:00 | Vulnerability · Source |
| CVE-2024-26706 | suse_vex | SUSE CVE CVE-2024-26706 | known not affected: 272 | 2026-08-05T01:01:27+00:00 | Vulnerability · Source |
| CVE-2024-26712 | suse_vex | SUSE CVE CVE-2024-26712 | known not affected: 272 | 2026-08-05T01:01:25+00:00 | Vulnerability · Source |
| CVE-2024-26762 | suse_vex | SUSE CVE CVE-2024-26762 | known affected: 394 known not affected: 325 recommended: 111 | 2026-08-05T01:01:18+00:00 | Vulnerability · Source |
| CVE-2024-26768 | suse_vex | SUSE CVE CVE-2024-26768 | known not affected: 299 | 2026-08-05T01:01:15+00:00 | Vulnerability · Source |
| 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 |