VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
97904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-54247 | suse_vex | SUSE CVE CVE-2023-54247 | known affected: 595 known not affected: 222 recommended: 212 | 2026-10-16T13:20:04+00:00 | Vulnerability · Source |
| CVE-2023-54254 | suse_vex | SUSE CVE CVE-2023-54254 | known affected: 435 known not affected: 295 recommended: 328 | 2026-10-16T13:20:02+00:00 | Vulnerability · Source |
| CVE-2023-54258 | suse_vex | SUSE CVE CVE-2023-54258 | known affected: 522 known not affected: 295 recommended: 212 | 2026-10-16T13:20:00+00:00 | Vulnerability · Source |
| CVE-2023-54262 | suse_vex | SUSE CVE CVE-2023-54262 | known affected: 374 known not affected: 490 recommended: 136 | 2026-10-16T13:19:58+00:00 | Vulnerability · Source |
| CVE-2023-54264 | suse_vex | SUSE CVE CVE-2023-54264 | known affected: 354 known not affected: 268 recommended: 431 | 2026-10-16T13:19:57+00:00 | Vulnerability · Source |
| CVE-2023-54266 | suse_vex | SUSE CVE CVE-2023-54266 | known affected: 401 known not affected: 221 recommended: 431 | 2026-10-16T13:19:55+00:00 | Vulnerability · Source |
| CVE-2023-54269 | suse_vex | SUSE CVE CVE-2023-54269 | known affected: 354 known not affected: 429 recommended: 245 | 2026-10-16T13:19:54+00:00 | Vulnerability · Source |
| CVE-2023-54280 | suse_vex | SUSE CVE CVE-2023-54280 | known affected: 427 known not affected: 300 recommended: 196 | 2026-10-16T13:19:52+00:00 | Vulnerability · Source |
| CVE-2023-54281 | suse_vex | SUSE CVE CVE-2023-54281 | known affected: 595 known not affected: 222 recommended: 212 | 2026-10-16T13:19:50+00:00 | Vulnerability · Source |
| CVE-2023-54285 | suse_vex | SUSE CVE CVE-2023-54285 | known affected: 394 known not affected: 423 recommended: 212 | 2026-10-16T13:19:49+00:00 | Vulnerability · Source |
| CVE-2023-54292 | suse_vex | SUSE CVE CVE-2023-54292 | known affected: 354 known not affected: 295 recommended: 437 | 2026-10-16T13:19:47+00:00 | Vulnerability · Source |
| CVE-2023-54302 | suse_vex | SUSE CVE CVE-2023-54302 | known affected: 354 known not affected: 295 recommended: 437 | 2026-10-16T13:19:45+00:00 | Vulnerability · Source |
| CVE-2023-54306 | suse_vex | SUSE CVE CVE-2023-54306 | known affected: 201 known not affected: 356 recommended: 29 | 2026-10-16T13:19:44+00:00 | Vulnerability · Source |
| CVE-2023-54308 | suse_vex | SUSE CVE CVE-2023-54308 | known affected: 0 known not affected: 557 recommended: 49 | 2026-10-16T13:19:42+00:00 | Vulnerability · Source |
| CVE-2023-54311 | suse_vex | SUSE CVE CVE-2023-54311 | known affected: 357 known not affected: 366 recommended: 233 | 2026-10-16T13:19:41+00:00 | Vulnerability · Source |
| CVE-2023-54318 | suse_vex | SUSE CVE CVE-2023-54318 | known affected: 569 known not affected: 248 recommended: 253 | 2026-10-16T13:19:39+00:00 | Vulnerability · Source |
| CVE-2024-0397 | suse_vex | SUSE CVE CVE-2024-0397 | known affected: 484 known not affected: 301 recommended: 608 | 2026-10-16T13:19:37+00:00 | Vulnerability · Source |
| CVE-2024-0565 | suse_vex | SUSE CVE CVE-2024-0565 | known affected: 239 known not affected: 236 recommended: 1078 | 2026-10-16T13:19:35+00:00 | Vulnerability · Source |
| CVE-2024-0911 | suse_vex | SUSE CVE CVE-2024-0911 | known affected: 35 recommended: 25 | 2026-10-16T13:19:32+00:00 | Vulnerability · Source |
| CVE-2024-1062 | suse_vex | SUSE CVE CVE-2024-1062 | known affected: 31 known not affected: 24 recommended: 103 | 2026-10-16T13:19:30+00:00 | Vulnerability · Source |
| CVE-2024-1065 | suse_vex | SUSE CVE CVE-2024-1065 | known not affected: 385 | 2026-10-16T13:19:28+00:00 | Vulnerability · Source |
| CVE-2024-1552 | suse_vex | SUSE CVE CVE-2024-1552 | known affected: 48 recommended: 201 | 2026-10-16T13:19:24+00:00 | Vulnerability · Source |
| CVE-2024-1597 | suse_vex | SUSE CVE CVE-2024-1597 | known affected: 406 recommended: 44 | 2026-10-16T13:19:22+00:00 | Vulnerability · Source |
| CVE-2024-4767 | suse_vex | SUSE CVE CVE-2024-4767 | known affected: 52 recommended: 214 | 2026-10-16T13:19:16+00:00 | Vulnerability · Source |
| CVE-2024-4768 | suse_vex | SUSE CVE CVE-2024-4768 | known affected: 52 recommended: 214 | 2026-10-16T13:19:15+00:00 | Vulnerability · Source |
| CVE-2024-4769 | suse_vex | SUSE CVE CVE-2024-4769 | known affected: 52 recommended: 211 | 2026-10-16T13:19:13+00:00 | Vulnerability · Source |
| CVE-2024-4773 | suse_vex | SUSE CVE CVE-2024-4773 | known affected: 52 recommended: 9 | 2026-10-16T13:19:12+00:00 | Vulnerability · Source |
| CVE-2024-4777 | suse_vex | SUSE CVE CVE-2024-4777 | known affected: 52 recommended: 214 | 2026-10-16T13:19:10+00:00 | Vulnerability · Source |
| CVE-2024-4855 | suse_vex | SUSE CVE CVE-2024-4855 | known affected: 180 known not affected: 58 recommended: 123 | 2026-10-16T13:19:09+00:00 | Vulnerability · Source |
| CVE-2024-5197 | suse_vex | SUSE CVE CVE-2024-5197 | known affected: 72 recommended: 106 | 2026-10-16T13:19:07+00:00 | Vulnerability · Source |
| CVE-2024-5696 | suse_vex | SUSE CVE CVE-2024-5696 | known affected: 52 recommended: 211 | 2026-10-16T13:19:05+00:00 | Vulnerability · Source |
| CVE-2024-5702 | suse_vex | SUSE CVE CVE-2024-5702 | known affected: 52 recommended: 205 | 2026-10-16T13:19:03+00:00 | Vulnerability · Source |
| CVE-2024-5953 | suse_vex | SUSE CVE CVE-2024-5953 | known affected: 53 known not affected: 36 recommended: 136 | 2026-10-16T13:19:02+00:00 | Vulnerability · Source |
| CVE-2024-6600 | suse_vex | SUSE CVE CVE-2024-6600 | known affected: 52 recommended: 237 | 2026-10-16T13:18:58+00:00 | Vulnerability · Source |
| CVE-2024-6603 | suse_vex | SUSE CVE CVE-2024-6603 | known affected: 52 recommended: 242 | 2026-10-16T13:18:57+00:00 | Vulnerability · Source |
| CVE-2024-6605 | suse_vex | SUSE CVE CVE-2024-6605 | known affected: 52 recommended: 180 | 2026-10-16T13:18:56+00:00 | Vulnerability · Source |
| CVE-2024-7347 | suse_vex | SUSE CVE CVE-2024-7347 | known affected: 42 recommended: 68 | 2026-10-16T13:18:53+00:00 | Vulnerability · Source |
| CVE-2024-7519 | suse_vex | SUSE CVE CVE-2024-7519 | known affected: 46 recommended: 242 | 2026-10-16T13:18:51+00:00 | Vulnerability · Source |
| CVE-2024-7589 | suse_vex | SUSE CVE CVE-2024-7589 | known not affected: 252 | 2026-10-16T13:18:49+00:00 | Vulnerability · Source |
| CVE-2024-7592 | suse_vex | SUSE CVE CVE-2024-7592 | known affected: 660 recommended: 1190 | 2026-10-16T13:18:47+00:00 | Vulnerability · Source |
| CVE-2024-8037 | suse_vex | SUSE CVE CVE-2024-8037 | recommended: 4 | 2026-10-16T13:18:44+00:00 | Vulnerability · Source |
| CVE-2024-8088 | suse_vex | SUSE CVE CVE-2024-8088 | known affected: 394 known not affected: 427 recommended: 672 | 2026-10-16T13:18:41+00:00 | Vulnerability · Source |
| CVE-2024-8250 | suse_vex | SUSE CVE CVE-2024-8250 | known affected: 228 recommended: 153 | 2026-10-16T13:18:39+00:00 | Vulnerability · Source |
| CVE-2024-8636 | suse_vex | SUSE CVE CVE-2024-8636 | known affected: 179 recommended: 29 | 2026-10-16T13:18:37+00:00 | Vulnerability · Source |
| CVE-2024-8932 | suse_vex | SUSE CVE CVE-2024-8932 | known affected: 0 known not affected: 2242 recommended: 468 | 2026-10-16T13:18:34+00:00 | Vulnerability · Source |
| CVE-2024-9391 | suse_vex | SUSE CVE CVE-2024-9391 | known affected: 57 recommended: 9 | 2026-10-16T13:18:31+00:00 | Vulnerability · Source |
| CVE-2024-9675 | suse_vex | SUSE CVE CVE-2024-9675 | known affected: 403 known not affected: 18 recommended: 187 | 2026-10-16T13:18:29+00:00 | Vulnerability · Source |
| CVE-2024-9680 | suse_vex | SUSE CVE CVE-2024-9680 | known affected: 72 recommended: 223 | 2026-10-16T13:18:27+00:00 | Vulnerability · Source |
| CVE-2024-9780 | suse_vex | SUSE CVE CVE-2024-9780 | known not affected: 353 recommended: 154 | 2026-10-16T13:18:24+00:00 | Vulnerability · Source |
| CVE-2024-10458 | suse_vex | SUSE CVE CVE-2024-10458 | known affected: 67 recommended: 219 | 2026-10-16T13:18:22+00:00 | Vulnerability · Source |