VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-36928 | suse_vex | SUSE CVE CVE-2024-36928 | known affected: 315 known not affected: 213 recommended: 690 | 2026-10-17T01:09:33+00:00 | Vulnerability · Source |
| CVE-2024-36952 | suse_vex | SUSE CVE CVE-2024-36952 | known affected: 497 known not affected: 114 recommended: 790 | 2026-10-17T01:09:31+00:00 | Vulnerability · Source |
| CVE-2024-36955 | suse_vex | SUSE CVE CVE-2024-36955 | known affected: 382 known not affected: 237 recommended: 674 | 2026-10-17T01:09:29+00:00 | Vulnerability · Source |
| CVE-2024-36960 | suse_vex | SUSE CVE CVE-2024-36960 | known affected: 612 known not affected: 28 recommended: 755 | 2026-10-17T01:09:28+00:00 | Vulnerability · Source |
| CVE-2024-36971 | suse_vex | SUSE CVE CVE-2024-36971 | known affected: 353 known not affected: 123 recommended: 1062 | 2026-10-17T01:09:26+00:00 | Vulnerability · Source |
| CVE-2024-37021 | suse_vex | SUSE CVE CVE-2024-37021 | known affected: 616 known not affected: 6 recommended: 735 | 2026-10-17T01:09:24+00:00 | Vulnerability · Source |
| CVE-2024-37890 | suse_vex | SUSE CVE CVE-2024-37890 | recommended: 9 | 2026-10-17T01:09:22+00:00 | Vulnerability · Source |
| CVE-2024-38473 | suse_vex | SUSE CVE CVE-2024-38473 | known affected: 467 known not affected: 1 recommended: 321 | 2026-10-17T01:09:20+00:00 | Vulnerability · Source |
| CVE-2024-38474 | suse_vex | SUSE CVE CVE-2024-38474 | known affected: 467 known not affected: 1 recommended: 347 | 2026-10-17T01:09:19+00:00 | Vulnerability · Source |
| CVE-2024-38538 | suse_vex | SUSE CVE CVE-2024-38538 | known affected: 521 known not affected: 29 recommended: 743 | 2026-10-17T01:09:17+00:00 | Vulnerability · Source |
| CVE-2024-38539 | suse_vex | SUSE CVE CVE-2024-38539 | known affected: 394 known not affected: 342 recommended: 353 | 2026-10-17T01:09:16+00:00 | Vulnerability · Source |
| CVE-2024-38542 | suse_vex | SUSE CVE CVE-2024-38542 | known affected: 394 known not affected: 335 recommended: 253 | 2026-10-17T01:09:15+00:00 | Vulnerability · Source |
| CVE-2024-38555 | suse_vex | SUSE CVE CVE-2024-38555 | known affected: 352 known not affected: 225 recommended: 766 | 2026-10-17T01:09:12+00:00 | Vulnerability · Source |
| CVE-2024-38573 | suse_vex | SUSE CVE CVE-2024-38573 | known affected: 383 known not affected: 223 recommended: 700 | 2026-10-17T01:09:10+00:00 | Vulnerability · Source |
| CVE-2024-38592 | suse_vex | SUSE CVE CVE-2024-38592 | known affected: 394 known not affected: 342 recommended: 353 | 2026-10-17T01:09:08+00:00 | Vulnerability · Source |
| CVE-2024-38605 | suse_vex | SUSE CVE CVE-2024-38605 | known affected: 397 known not affected: 253 recommended: 651 | 2026-10-17T01:09:06+00:00 | Vulnerability · Source |
| CVE-2024-38606 | suse_vex | SUSE CVE CVE-2024-38606 | known affected: 394 known not affected: 320 recommended: 306 | 2026-10-17T01:09:05+00:00 | Vulnerability · Source |
| CVE-2024-38664 | suse_vex | SUSE CVE CVE-2024-38664 | known affected: 394 known not affected: 345 recommended: 353 | 2026-10-17T01:09:00+00:00 | Vulnerability · Source |
| CVE-2024-39282 | suse_vex | SUSE CVE CVE-2024-39282 | known affected: 394 known not affected: 394 recommended: 389 | 2026-10-17T01:08:59+00:00 | Vulnerability · Source |
| CVE-2024-39474 | suse_vex | SUSE CVE CVE-2024-39474 | known affected: 394 known not affected: 361 recommended: 353 | 2026-10-17T01:08:57+00:00 | Vulnerability · Source |
| CVE-2024-39476 | suse_vex | SUSE CVE CVE-2024-39476 | known affected: 477 known not affected: 176 recommended: 730 | 2026-10-17T01:08:55+00:00 | Vulnerability · Source |
| CVE-2024-39484 | suse_vex | SUSE CVE CVE-2024-39484 | known affected: 394 known not affected: 493 recommended: 355 | 2026-10-17T01:08:53+00:00 | Vulnerability · Source |
| CVE-2024-39495 | suse_vex | SUSE CVE CVE-2024-39495 | known not affected: 373 | 2026-10-17T01:08:51+00:00 | Vulnerability · Source |
| CVE-2024-39496 | suse_vex | SUSE CVE CVE-2024-39496 | known affected: 394 known not affected: 292 recommended: 353 | 2026-10-17T01:08:50+00:00 | Vulnerability · Source |
| CVE-2024-39508 | suse_vex | SUSE CVE CVE-2024-39508 | known affected: 397 known not affected: 237 recommended: 653 | 2026-10-17T01:08:48+00:00 | Vulnerability · Source |
| CVE-2024-40898 | suse_vex | SUSE CVE CVE-2024-40898 | known affected: 0 known not affected: 262 recommended: 46 | 2026-10-17T01:08:46+00:00 | Vulnerability · Source |
| CVE-2024-40900 | suse_vex | SUSE CVE CVE-2024-40900 | known affected: 330 known not affected: 258 recommended: 653 | 2026-10-17T01:08:45+00:00 | Vulnerability · Source |
| CVE-2024-40918 | suse_vex | SUSE CVE CVE-2024-40918 | known not affected: 373 | 2026-10-17T01:08:43+00:00 | Vulnerability · Source |
| CVE-2024-40923 | suse_vex | SUSE CVE CVE-2024-40923 | known affected: 330 known not affected: 257 recommended: 721 | 2026-10-17T01:08:41+00:00 | Vulnerability · Source |
| CVE-2024-40929 | suse_vex | SUSE CVE CVE-2024-40929 | known affected: 572 known not affected: 14 recommended: 801 | 2026-10-17T01:08:40+00:00 | Vulnerability · Source |
| CVE-2024-40930 | suse_vex | SUSE CVE CVE-2024-40930 | known affected: 394 known not affected: 320 recommended: 355 | 2026-10-17T01:08:38+00:00 | Vulnerability · Source |
| CVE-2024-40932 | suse_vex | SUSE CVE CVE-2024-40932 | known affected: 500 known not affected: 12 recommended: 737 | 2026-10-17T01:08:36+00:00 | Vulnerability · Source |
| CVE-2024-40949 | suse_vex | SUSE CVE CVE-2024-40949 | known not affected: 373 | 2026-10-17T01:08:34+00:00 | Vulnerability · Source |
| CVE-2024-40950 | suse_vex | SUSE CVE CVE-2024-40950 | known not affected: 373 | 2026-10-17T01:08:33+00:00 | Vulnerability · Source |
| CVE-2024-40957 | suse_vex | SUSE CVE CVE-2024-40957 | known affected: 394 known not affected: 361 recommended: 413 | 2026-10-17T01:08:31+00:00 | Vulnerability · Source |
| CVE-2024-40963 | suse_vex | SUSE CVE CVE-2024-40963 | known not affected: 610 | 2026-10-17T01:08:30+00:00 | Vulnerability · Source |
| CVE-2024-40968 | suse_vex | SUSE CVE CVE-2024-40968 | known not affected: 373 | 2026-10-17T01:08:28+00:00 | Vulnerability · Source |
| CVE-2024-41019 | suse_vex | SUSE CVE CVE-2024-41019 | known not affected: 561 | 2026-10-17T01:08:24+00:00 | Vulnerability · Source |
| CVE-2024-41049 | suse_vex | SUSE CVE CVE-2024-41049 | known affected: 354 known not affected: 207 recommended: 624 | 2026-10-17T01:08:22+00:00 | Vulnerability · Source |
| CVE-2024-41050 | suse_vex | SUSE CVE CVE-2024-41050 | known affected: 471 known not affected: 299 recommended: 355 | 2026-10-17T01:08:21+00:00 | Vulnerability · Source |
| CVE-2024-41060 | suse_vex | SUSE CVE CVE-2024-41060 | known affected: 516 known not affected: 6 recommended: 747 | 2026-10-17T01:08:19+00:00 | Vulnerability · Source |
| CVE-2024-41065 | suse_vex | SUSE CVE CVE-2024-41065 | known affected: 567 recommended: 663 | 2026-10-17T01:08:17+00:00 | Vulnerability · Source |
| CVE-2024-41067 | suse_vex | SUSE CVE CVE-2024-41067 | known not affected: 379 | 2026-10-17T01:08:16+00:00 | Vulnerability · Source |
| CVE-2026-94439 | microsoft_vex | HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http | known affected: 4 | 2026-10-17T01:08:14+00:00 | Vulnerability · Source |
| CVE-2024-41149 | suse_vex | SUSE CVE CVE-2024-41149 | known affected: 609 known not affected: 225 recommended: 388 | 2026-10-17T01:08:12+00:00 | Vulnerability · Source |
| CVE-2024-42074 | suse_vex | SUSE CVE CVE-2024-42074 | known affected: 340 known not affected: 264 recommended: 643 | 2026-10-17T01:08:10+00:00 | Vulnerability · Source |
| CVE-2024-42089 | suse_vex | SUSE CVE CVE-2024-42089 | known affected: 407 known not affected: 272 recommended: 643 | 2026-10-17T01:08:08+00:00 | Vulnerability · Source |
| CVE-2024-42091 | suse_vex | SUSE CVE CVE-2024-42091 | known not affected: 379 recommended: 47 | 2026-10-17T01:08:07+00:00 | Vulnerability · Source |
| CVE-2024-42132 | suse_vex | SUSE CVE CVE-2024-42132 | known affected: 394 known not affected: 326 recommended: 355 | 2026-10-17T01:08:04+00:00 | Vulnerability · Source |
| CVE-2024-42156 | suse_vex | SUSE CVE CVE-2024-42156 | known affected: 491 known not affected: 141 recommended: 643 | 2026-10-17T01:08:02+00:00 | Vulnerability · Source |