VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292260 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-42116 | suse_vex | SUSE CVE CVE-2024-42116 | known not affected: 324 | 2026-07-25T01:43:06+00:00 | Vulnerability · Source |
| CVE-2024-42127 | suse_vex | SUSE CVE CVE-2024-42127 | known affected: 340 known not affected: 204 recommended: 648 | 2026-07-25T01:43:01+00:00 | Vulnerability · Source |
| CVE-2024-42132 | suse_vex | SUSE CVE CVE-2024-42132 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-25T01:43:00+00:00 | Vulnerability · Source |
| CVE-2024-42133 | suse_vex | SUSE CVE CVE-2024-42133 | known affected: 394 known not affected: 264 recommended: 410 | 2026-07-25T01:42:58+00:00 | Vulnerability · Source |
| CVE-2024-42135 | suse_vex | SUSE CVE CVE-2024-42135 | known not affected: 324 | 2026-07-25T01:42:56+00:00 | Vulnerability · Source |
| CVE-2024-42140 | suse_vex | SUSE CVE CVE-2024-42140 | known not affected: 327 | 2026-07-25T01:42:53+00:00 | Vulnerability · Source |
| CVE-2024-42141 | suse_vex | SUSE CVE CVE-2024-42141 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-25T01:42:51+00:00 | Vulnerability · Source |
| CVE-2024-42154 | suse_vex | SUSE CVE CVE-2024-42154 | known affected: 543 known not affected: 38 recommended: 749 | 2026-07-25T01:42:45+00:00 | Vulnerability · Source |
| CVE-2024-42225 | suse_vex | SUSE CVE CVE-2024-42225 | known affected: 372 known not affected: 115 recommended: 697 | 2026-07-25T01:42:42+00:00 | Vulnerability · Source |
| CVE-2024-42229 | suse_vex | SUSE CVE CVE-2024-42229 | known affected: 542 recommended: 811 | 2026-07-25T01:42:39+00:00 | Vulnerability · Source |
| CVE-2024-42231 | suse_vex | SUSE CVE CVE-2024-42231 | known not affected: 324 | 2026-07-25T01:42:36+00:00 | Vulnerability · Source |
| CVE-2024-42234 | suse_vex | SUSE CVE CVE-2024-42234 | known not affected: 311 | 2026-07-25T01:42:34+00:00 | Vulnerability · Source |
| CVE-2024-42249 | suse_vex | SUSE CVE CVE-2024-42249 | known not affected: 310 | 2026-07-25T01:42:30+00:00 | Vulnerability · Source |
| CVE-2024-42268 | suse_vex | SUSE CVE CVE-2024-42268 | known affected: 340 known not affected: 211 recommended: 648 | 2026-07-25T01:42:28+00:00 | Vulnerability · Source |
| CVE-2024-42275 | suse_vex | SUSE CVE CVE-2024-42275 | known not affected: 311 recommended: 59 | 2026-07-25T01:42:22+00:00 | Vulnerability · Source |
| CVE-2024-42294 | suse_vex | SUSE CVE CVE-2024-42294 | known affected: 394 known not affected: 339 recommended: 392 | 2026-07-25T01:42:17+00:00 | Vulnerability · Source |
| CVE-2024-42299 | suse_vex | SUSE CVE CVE-2024-42299 | known not affected: 513 | 2026-07-25T01:42:15+00:00 | Vulnerability · Source |
| CVE-2024-42305 | suse_vex | SUSE CVE CVE-2024-42305 | known affected: 537 known not affected: 32 recommended: 764 | 2026-07-25T01:42:14+00:00 | Vulnerability · Source |
| CVE-2024-42307 | suse_vex | SUSE CVE CVE-2024-42307 | known affected: 369 known not affected: 227 recommended: 404 | 2026-07-25T01:42:10+00:00 | Vulnerability · Source |
| CVE-2024-42312 | suse_vex | SUSE CVE CVE-2024-42312 | known affected: 465 known not affected: 57 recommended: 761 | 2026-07-25T01:42:09+00:00 | Vulnerability · Source |
| CVE-2024-42316 | suse_vex | SUSE CVE CVE-2024-42316 | known affected: 394 known not affected: 280 recommended: 403 | 2026-07-25T01:42:05+00:00 | Vulnerability · Source |
| CVE-2024-42322 | suse_vex | SUSE CVE CVE-2024-42322 | known affected: 512 known not affected: 10 recommended: 782 | 2026-07-25T01:42:02+00:00 | Vulnerability · Source |
| CVE-2024-42326 | suse_vex | SUSE CVE CVE-2024-42326 | known not affected: 12 | 2026-07-25T01:42:01+00:00 | Vulnerability · Source |
| CVE-2024-42330 | suse_vex | SUSE CVE CVE-2024-42330 | known not affected: 12 | 2026-07-25T01:42:00+00:00 | Vulnerability · Source |
| CVE-2024-42331 | suse_vex | SUSE CVE CVE-2024-42331 | known not affected: 12 | 2026-07-25T01:41:59+00:00 | Vulnerability · Source |
| CVE-2024-42333 | suse_vex | SUSE CVE CVE-2024-42333 | known affected: 10 recommended: 3 | 2026-07-25T01:41:57+00:00 | Vulnerability · Source |
| CVE-2024-42415 | suse_vex | SUSE CVE CVE-2024-42415 | known affected: 37 recommended: 94 | 2026-07-25T01:41:56+00:00 | Vulnerability · Source |
| CVE-2024-43820 | suse_vex | SUSE CVE CVE-2024-43820 | known affected: 410 known not affected: 311 recommended: 385 | 2026-07-25T01:41:51+00:00 | Vulnerability · Source |
| CVE-2024-43826 | suse_vex | SUSE CVE CVE-2024-43826 | known affected: 394 known not affected: 280 recommended: 360 | 2026-07-25T01:41:47+00:00 | Vulnerability · Source |
| CVE-2024-43836 | suse_vex | SUSE CVE CVE-2024-43836 | known not affected: 310 recommended: 59 | 2026-07-25T01:41:40+00:00 | Vulnerability · Source |
| CVE-2024-43840 | suse_vex | SUSE CVE CVE-2024-43840 | known affected: 394 known not affected: 254 recommended: 360 | 2026-07-25T01:41:37+00:00 | Vulnerability · Source |
| CVE-2024-43849 | suse_vex | SUSE CVE CVE-2024-43849 | known affected: 340 known not affected: 139 recommended: 648 | 2026-07-25T01:41:32+00:00 | Vulnerability · Source |
| CVE-2024-43857 | suse_vex | SUSE CVE CVE-2024-43857 | known not affected: 310 | 2026-07-25T01:41:29+00:00 | Vulnerability · Source |
| CVE-2024-43858 | suse_vex | SUSE CVE CVE-2024-43858 | known affected: 438 known not affected: 170 recommended: 648 | 2026-07-25T01:41:28+00:00 | Vulnerability · Source |
| CVE-2024-43859 | suse_vex | SUSE CVE CVE-2024-43859 | known not affected: 509 | 2026-07-25T01:41:26+00:00 | Vulnerability · Source |
| CVE-2024-43868 | suse_vex | SUSE CVE CVE-2024-43868 | known not affected: 403 | 2026-07-25T01:41:23+00:00 | Vulnerability · Source |
| CVE-2024-43875 | suse_vex | SUSE CVE CVE-2024-43875 | known affected: 394 known not affected: 254 recommended: 360 | 2026-07-25T01:41:19+00:00 | Vulnerability · Source |
| CVE-2024-43882 | suse_vex | SUSE CVE CVE-2024-43882 | known affected: 357 known not affected: 2 recommended: 1080 | 2026-07-25T01:41:17+00:00 | Vulnerability · Source |
| CVE-2024-43884 | suse_vex | SUSE CVE CVE-2024-43884 | known affected: 457 known not affected: 12 recommended: 775 | 2026-07-25T01:41:13+00:00 | Vulnerability · Source |
| CVE-2024-43886 | suse_vex | SUSE CVE CVE-2024-43886 | known affected: 394 known not affected: 315 recommended: 67 | 2026-07-25T01:41:11+00:00 | Vulnerability · Source |
| CVE-2024-43887 | suse_vex | SUSE CVE CVE-2024-43887 | known not affected: 310 | 2026-07-25T01:41:10+00:00 | Vulnerability · Source |
| CVE-2024-43913 | suse_vex | SUSE CVE CVE-2024-43913 | known affected: 410 known not affected: 378 recommended: 310 | 2026-07-25T01:41:01+00:00 | Vulnerability · Source |
| CVE-2024-44296 | suse_vex | SUSE CVE CVE-2024-44296 | known affected: 111 known not affected: 62 recommended: 680 | 2026-07-25T01:40:58+00:00 | Vulnerability · Source |
| CVE-2024-44309 | suse_vex | SUSE CVE CVE-2024-44309 | known affected: 100 recommended: 767 | 2026-07-25T01:40:56+00:00 | Vulnerability · Source |
| CVE-2024-44934 | suse_vex | SUSE CVE CVE-2024-44934 | known affected: 492 known not affected: 199 recommended: 463 | 2026-07-25T01:40:54+00:00 | Vulnerability · Source |
| CVE-2024-44940 | suse_vex | SUSE CVE CVE-2024-44940 | known not affected: 6 | 2026-07-25T01:40:50+00:00 | Vulnerability · Source |
| CVE-2024-44962 | suse_vex | SUSE CVE CVE-2024-44962 | known affected: 394 known not affected: 268 recommended: 357 | 2026-07-25T01:40:39+00:00 | Vulnerability · Source |
| CVE-2024-44963 | suse_vex | SUSE CVE CVE-2024-44963 | known affected: 760 recommended: 391 | 2026-07-25T01:40:37+00:00 | Vulnerability · Source |
| CVE-2024-44968 | suse_vex | SUSE CVE CVE-2024-44968 | known not affected: 324 | 2026-07-25T01:40:33+00:00 | Vulnerability · Source |
| CVE-2024-44972 | suse_vex | SUSE CVE CVE-2024-44972 | known affected: 340 known not affected: 379 recommended: 273 | 2026-07-25T01:40:29+00:00 | Vulnerability · Source |