VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291746 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-26891 | suse_vex | SUSE CVE CVE-2024-26891 | known affected: 381 known not affected: 166 recommended: 524 | 2026-08-13T01:53:23+00:00 | Vulnerability · Source |
| CVE-2024-26918 | suse_vex | SUSE CVE CVE-2024-26918 | known not affected: 311 | 2026-08-13T01:53:14+00:00 | Vulnerability · Source |
| CVE-2024-26932 | suse_vex | SUSE CVE CVE-2024-26932 | known affected: 394 known not affected: 312 recommended: 362 | 2026-08-13T01:53:10+00:00 | Vulnerability · Source |
| CVE-2024-26940 | suse_vex | SUSE CVE CVE-2024-26940 | known affected: 315 known not affected: 243 recommended: 695 | 2026-08-13T01:53:04+00:00 | Vulnerability · Source |
| CVE-2024-26993 | suse_vex | SUSE CVE CVE-2024-26993 | known affected: 522 known not affected: 6 recommended: 809 | 2026-08-13T01:52:52+00:00 | Vulnerability · Source |
| CVE-2024-27024 | suse_vex | SUSE CVE CVE-2024-27024 | known affected: 594 known not affected: 6 recommended: 606 | 2026-08-13T01:52:45+00:00 | Vulnerability · Source |
| CVE-2024-27069 | suse_vex | SUSE CVE CVE-2024-27069 | known not affected: 330 | 2026-08-13T01:52:30+00:00 | Vulnerability · Source |
| CVE-2024-27099 | suse_vex | SUSE CVE CVE-2024-27099 | known affected: 418 recommended: 40 | 2026-08-13T01:52:26+00:00 | Vulnerability · Source |
| CVE-2024-27459 | suse_vex | SUSE CVE CVE-2024-27459 | known not affected: 115 | 2026-08-13T01:52:12+00:00 | Vulnerability · Source |
| CVE-2024-27766 | suse_vex | SUSE CVE CVE-2024-27766 | known not affected: 348 | 2026-08-13T01:52:10+00:00 | Vulnerability · Source |
| CVE-2024-27983 | suse_vex | SUSE CVE CVE-2024-27983 | known not affected: 287 recommended: 307 | 2026-08-13T01:52:06+00:00 | Vulnerability · Source |
| CVE-2024-31082 | suse_vex | SUSE CVE CVE-2024-31082 | known affected: 422 known not affected: 36 recommended: 142 | 2026-08-13T01:51:55+00:00 | Vulnerability · Source |
| CVE-2024-31145 | suse_vex | SUSE CVE CVE-2024-31145 | known affected: 345 recommended: 152 | 2026-08-13T01:51:53+00:00 | Vulnerability · Source |
| CVE-2024-32650 | suse_vex | SUSE CVE CVE-2024-32650 | known affected: 29 known not affected: 69 recommended: 65 | 2026-08-13T01:51:48+00:00 | Vulnerability · Source |
| CVE-2024-32658 | suse_vex | SUSE CVE CVE-2024-32658 | recommended: 199 | 2026-08-13T01:51:46+00:00 | Vulnerability · Source |
| CVE-2024-32659 | suse_vex | SUSE CVE CVE-2024-32659 | recommended: 199 | 2026-08-13T01:51:45+00:00 | Vulnerability · Source |
| CVE-2024-32661 | suse_vex | SUSE CVE CVE-2024-32661 | recommended: 199 | 2026-08-13T01:51:44+00:00 | Vulnerability · Source |
| CVE-2024-33617 | suse_vex | SUSE CVE CVE-2024-33617 | known affected: 10 recommended: 126 | 2026-08-13T01:51:42+00:00 | Vulnerability · Source |
| CVE-2024-34030 | suse_vex | SUSE CVE CVE-2024-34030 | known not affected: 318 | 2026-08-13T01:51:39+00:00 | Vulnerability · Source |
| CVE-2024-34088 | suse_vex | SUSE CVE CVE-2024-34088 | known not affected: 405 recommended: 175 | 2026-08-13T01:51:38+00:00 | Vulnerability · Source |
| CVE-2024-34156 | suse_vex | SUSE CVE CVE-2024-34156 | recommended: 555 | 2026-08-13T01:51:36+00:00 | Vulnerability · Source |
| CVE-2024-34447 | suse_vex | SUSE CVE CVE-2024-34447 | known not affected: 126 | 2026-08-13T01:51:34+00:00 | Vulnerability · Source |
| CVE-2024-35328 | suse_vex | SUSE CVE CVE-2024-35328 | known not affected: 336 | 2026-08-13T01:51:28+00:00 | Vulnerability · Source |
| CVE-2024-35369 | suse_vex | SUSE CVE CVE-2024-35369 | known not affected: 823 | 2026-08-13T01:51:26+00:00 | Vulnerability · Source |
| CVE-2024-35790 | suse_vex | SUSE CVE CVE-2024-35790 | known affected: 407 known not affected: 58 recommended: 703 | 2026-08-13T01:51:23+00:00 | Vulnerability · Source |
| CVE-2024-35802 | suse_vex | SUSE CVE CVE-2024-35802 | known not affected: 330 | 2026-08-13T01:51:20+00:00 | Vulnerability · Source |
| CVE-2024-35821 | suse_vex | SUSE CVE CVE-2024-35821 | known affected: 584 known not affected: 64 recommended: 675 | 2026-08-13T01:51:17+00:00 | Vulnerability · Source |
| CVE-2024-35832 | suse_vex | SUSE CVE CVE-2024-35832 | known not affected: 330 | 2026-08-13T01:51:14+00:00 | Vulnerability · Source |
| CVE-2024-35846 | suse_vex | SUSE CVE CVE-2024-35846 | known not affected: 330 | 2026-08-13T01:51:11+00:00 | Vulnerability · Source |
| CVE-2024-35851 | suse_vex | SUSE CVE CVE-2024-35851 | known affected: 362 known not affected: 157 recommended: 675 | 2026-08-13T01:51:09+00:00 | Vulnerability · Source |
| CVE-2024-36002 | suse_vex | SUSE CVE CVE-2024-36002 | known not affected: 270 recommended: 362 | 2026-08-13T01:50:34+00:00 | Vulnerability · Source |
| CVE-2024-36015 | suse_vex | SUSE CVE CVE-2024-36015 | known affected: 407 known not affected: 10 recommended: 741 | 2026-08-13T01:50:29+00:00 | Vulnerability · Source |
| CVE-2024-36033 | suse_vex | SUSE CVE CVE-2024-36033 | known not affected: 330 recommended: 59 | 2026-08-13T01:50:25+00:00 | Vulnerability · Source |
| CVE-2024-36621 | suse_vex | SUSE CVE CVE-2024-36621 | known not affected: 127 recommended: 3 | 2026-08-13T01:50:21+00:00 | Vulnerability · Source |
| CVE-2024-36897 | suse_vex | SUSE CVE CVE-2024-36897 | known affected: 315 known not affected: 181 recommended: 675 | 2026-08-13T01:50:16+00:00 | Vulnerability · Source |
| CVE-2024-36905 | suse_vex | SUSE CVE CVE-2024-36905 | known affected: 503 known not affected: 34 recommended: 639 | 2026-08-13T01:50:14+00:00 | Vulnerability · Source |
| CVE-2024-36955 | suse_vex | SUSE CVE CVE-2024-36955 | known affected: 376 known not affected: 181 recommended: 679 | 2026-08-13T01:50:03+00:00 | Vulnerability · Source |
| CVE-2024-36956 | suse_vex | SUSE CVE CVE-2024-36956 | known not affected: 330 recommended: 59 | 2026-08-13T01:50:02+00:00 | Vulnerability · Source |
| CVE-2024-36976 | suse_vex | SUSE CVE CVE-2024-36976 | known not affected: 318 | 2026-08-13T01:49:59+00:00 | Vulnerability · Source |
| CVE-2024-38517 | suse_vex | SUSE CVE CVE-2024-38517 | known not affected: 46 | 2026-08-13T01:49:52+00:00 | Vulnerability · Source |
| CVE-2024-38526 | suse_vex | SUSE CVE CVE-2024-38526 | known affected: 2 known not affected: 708 recommended: 16 | 2026-08-13T01:49:51+00:00 | Vulnerability · Source |
| CVE-2024-38551 | suse_vex | SUSE CVE CVE-2024-38551 | known affected: 394 known not affected: 285 recommended: 358 | 2026-08-13T01:49:49+00:00 | Vulnerability · Source |
| CVE-2024-38625 | suse_vex | SUSE CVE CVE-2024-38625 | known not affected: 557 | 2026-08-13T01:49:37+00:00 | Vulnerability · Source |
| CVE-2024-38633 | suse_vex | SUSE CVE CVE-2024-38633 | known affected: 581 known not affected: 71 recommended: 656 | 2026-08-13T01:49:35+00:00 | Vulnerability · Source |
| CVE-2024-38636 | suse_vex | SUSE CVE CVE-2024-38636 | known affected: 394 known not affected: 285 recommended: 358 | 2026-08-13T01:49:33+00:00 | Vulnerability · Source |
| CVE-2024-38999 | suse_vex | SUSE CVE CVE-2024-38999 | known affected: 115 recommended: 39 | 2026-08-13T01:49:31+00:00 | Vulnerability · Source |
| CVE-2024-39286 | suse_vex | SUSE CVE CVE-2024-39286 | known not affected: 359 | 2026-08-13T01:49:29+00:00 | Vulnerability · Source |
| CVE-2024-39331 | suse_vex | SUSE CVE CVE-2024-39331 | known affected: 44 recommended: 265 | 2026-08-13T01:49:28+00:00 | Vulnerability · Source |
| CVE-2024-39461 | suse_vex | SUSE CVE CVE-2024-39461 | known not affected: 318 recommended: 59 | 2026-08-13T01:49:26+00:00 | Vulnerability · Source |
| CVE-2024-40780 | suse_vex | SUSE CVE CVE-2024-40780 | known affected: 93 known not affected: 55 recommended: 692 | 2026-08-13T01:49:15+00:00 | Vulnerability · Source |