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-2023-53804 | suse_vex | SUSE CVE CVE-2023-53804 | known affected: 354 known not affected: 336 recommended: 196 | 2026-08-05T01:03:35+00:00 | Vulnerability · Source |
| CVE-2023-53810 | suse_vex | SUSE CVE CVE-2023-53810 | known affected: 147 known not affected: 261 recommended: 29 | 2026-08-05T01:03:33+00:00 | Vulnerability · Source |
| CVE-2023-53822 | suse_vex | SUSE CVE CVE-2023-53822 | known affected: 112 known not affected: 302 | 2026-08-05T01:03:31+00:00 | Vulnerability · Source |
| CVE-2023-53827 | suse_vex | SUSE CVE CVE-2023-53827 | known affected: 354 known not affected: 267 recommended: 237 | 2026-08-05T01:03:29+00:00 | Vulnerability · Source |
| CVE-2023-53838 | suse_vex | SUSE CVE CVE-2023-53838 | known not affected: 408 | 2026-08-05T01:03:26+00:00 | Vulnerability · Source |
| CVE-2023-53862 | suse_vex | SUSE CVE CVE-2023-53862 | known affected: 421 known not affected: 239 recommended: 219 | 2026-08-05T01:03:24+00:00 | Vulnerability · Source |
| CVE-2023-53990 | suse_vex | SUSE CVE CVE-2023-53990 | known affected: 354 known not affected: 341 recommended: 225 | 2026-08-05T01:03:21+00:00 | Vulnerability · Source |
| CVE-2023-54004 | suse_vex | SUSE CVE CVE-2023-54004 | known affected: 244 known not affected: 211 recommended: 29 | 2026-08-05T01:03:18+00:00 | Vulnerability · Source |
| CVE-2023-54050 | suse_vex | SUSE CVE CVE-2023-54050 | known affected: 415 known not affected: 233 recommended: 196 | 2026-08-05T01:03:13+00:00 | Vulnerability · Source |
| CVE-2023-54065 | suse_vex | SUSE CVE CVE-2023-54065 | known not affected: 453 | 2026-08-05T01:03:10+00:00 | Vulnerability · Source |
| CVE-2023-54071 | suse_vex | SUSE CVE CVE-2023-54071 | known not affected: 453 recommended: 49 | 2026-08-05T01:03:08+00:00 | Vulnerability · Source |
| CVE-2023-54079 | suse_vex | SUSE CVE CVE-2023-54079 | known affected: 454 known not affected: 177 recommended: 196 | 2026-08-05T01:03:05+00:00 | Vulnerability · Source |
| CVE-2023-54090 | suse_vex | SUSE CVE CVE-2023-54090 | known affected: 354 known not affected: 341 recommended: 225 | 2026-08-05T01:03:02+00:00 | Vulnerability · Source |
| CVE-2023-54100 | suse_vex | SUSE CVE CVE-2023-54100 | known affected: 395 known not affected: 300 recommended: 225 | 2026-08-05T01:02:58+00:00 | Vulnerability · Source |
| CVE-2023-54139 | suse_vex | SUSE CVE CVE-2023-54139 | known not affected: 453 | 2026-08-05T01:02:52+00:00 | Vulnerability · Source |
| CVE-2023-54157 | suse_vex | SUSE CVE CVE-2023-54157 | known not affected: 453 | 2026-08-05T01:02:48+00:00 | Vulnerability · Source |
| CVE-2023-54168 | suse_vex | SUSE CVE CVE-2023-54168 | known affected: 447 known not affected: 205 recommended: 252 | 2026-08-05T01:02:45+00:00 | Vulnerability · Source |
| CVE-2023-54193 | suse_vex | SUSE CVE CVE-2023-54193 | known affected: 167 known not affected: 286 | 2026-08-05T01:02:42+00:00 | Vulnerability · Source |
| CVE-2023-54200 | suse_vex | SUSE CVE CVE-2023-54200 | known affected: 112 known not affected: 341 recommended: 29 | 2026-08-05T01:02:41+00:00 | Vulnerability · Source |
| CVE-2023-54203 | suse_vex | SUSE CVE CVE-2023-54203 | known not affected: 453 | 2026-08-05T01:02:38+00:00 | Vulnerability · Source |
| 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 |