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-27017 | suse_vex | SUSE CVE CVE-2024-27017 | known affected: 398 known not affected: 387 recommended: 330 | 2026-07-25T01:54:04+00:00 | Vulnerability · Source |
| CVE-2024-27018 | suse_vex | SUSE CVE CVE-2024-27018 | known not affected: 270 recommended: 365 | 2026-07-25T01:54:03+00:00 | Vulnerability · Source |
| CVE-2024-27021 | suse_vex | SUSE CVE CVE-2024-27021 | known not affected: 330 | 2026-07-25T01:54:02+00:00 | Vulnerability · Source |
| CVE-2024-27033 | suse_vex | SUSE CVE CVE-2024-27033 | known not affected: 330 | 2026-07-25T01:53:54+00:00 | Vulnerability · Source |
| CVE-2024-27041 | suse_vex | SUSE CVE CVE-2024-27041 | known affected: 371 known not affected: 257 recommended: 531 | 2026-07-25T01:53:49+00:00 | Vulnerability · Source |
| CVE-2024-27042 | suse_vex | SUSE CVE CVE-2024-27042 | known affected: 394 known not affected: 268 recommended: 467 | 2026-07-25T01:53:47+00:00 | Vulnerability · Source |
| CVE-2024-27045 | suse_vex | SUSE CVE CVE-2024-27045 | known affected: 315 known not affected: 217 recommended: 526 | 2026-07-25T01:53:41+00:00 | Vulnerability · Source |
| CVE-2024-27063 | suse_vex | SUSE CVE CVE-2024-27063 | known not affected: 330 | 2026-07-25T01:53:37+00:00 | Vulnerability · Source |
| CVE-2024-27066 | suse_vex | SUSE CVE CVE-2024-27066 | known not affected: 330 | 2026-07-25T01:53:34+00:00 | Vulnerability · Source |
| CVE-2024-27071 | suse_vex | SUSE CVE CVE-2024-27071 | known affected: 394 known not affected: 330 recommended: 213 | 2026-07-25T01:53:30+00:00 | Vulnerability · Source |
| CVE-2024-27280 | suse_vex | SUSE CVE CVE-2024-27280 | known not affected: 237 recommended: 68 | 2026-07-25T01:53:25+00:00 | Vulnerability · Source |
| CVE-2024-27281 | suse_vex | SUSE CVE CVE-2024-27281 | known not affected: 313 recommended: 68 | 2026-07-25T01:53:23+00:00 | Vulnerability · Source |
| CVE-2024-27316 | suse_vex | SUSE CVE CVE-2024-27316 | known affected: 394 known not affected: 25 recommended: 315 | 2026-07-25T01:53:19+00:00 | Vulnerability · Source |
| CVE-2024-27390 | suse_vex | SUSE CVE CVE-2024-27390 | known not affected: 157 | 2026-07-25T01:53:17+00:00 | Vulnerability · Source |
| CVE-2024-27394 | suse_vex | SUSE CVE CVE-2024-27394 | known not affected: 330 | 2026-07-25T01:53:15+00:00 | Vulnerability · Source |
| CVE-2024-27401 | suse_vex | SUSE CVE CVE-2024-27401 | known affected: 394 recommended: 676 | 2026-07-25T01:53:06+00:00 | Vulnerability · Source |
| CVE-2024-27404 | suse_vex | SUSE CVE CVE-2024-27404 | known affected: 394 known not affected: 312 recommended: 358 | 2026-07-25T01:53:03+00:00 | Vulnerability · Source |
| CVE-2024-27407 | suse_vex | SUSE CVE CVE-2024-27407 | known affected: 394 known not affected: 312 recommended: 310 | 2026-07-25T01:53:01+00:00 | Vulnerability · Source |
| CVE-2024-27408 | suse_vex | SUSE CVE CVE-2024-27408 | known affected: 394 known not affected: 312 recommended: 358 | 2026-07-25T01:52:58+00:00 | Vulnerability · Source |
| CVE-2024-27409 | suse_vex | SUSE CVE CVE-2024-27409 | known not affected: 330 | 2026-07-25T01:52:56+00:00 | Vulnerability · Source |
| CVE-2024-27414 | suse_vex | SUSE CVE CVE-2024-27414 | known affected: 421 known not affected: 312 recommended: 358 | 2026-07-25T01:52:50+00:00 | Vulnerability · Source |
| CVE-2024-27415 | suse_vex | SUSE CVE CVE-2024-27415 | known affected: 675 known not affected: 111 recommended: 398 | 2026-07-25T01:52:48+00:00 | Vulnerability · Source |
| CVE-2024-27830 | suse_vex | SUSE CVE CVE-2024-27830 | known not affected: 196 | 2026-07-25T01:52:38+00:00 | Vulnerability · Source |
| CVE-2024-27838 | suse_vex | SUSE CVE CVE-2024-27838 | known affected: 97 recommended: 678 | 2026-07-25T01:52:33+00:00 | Vulnerability · Source |
| CVE-2024-27850 | suse_vex | SUSE CVE CVE-2024-27850 | known not affected: 196 | 2026-07-25T01:52:31+00:00 | Vulnerability · Source |
| CVE-2024-28182 | suse_vex | SUSE CVE CVE-2024-28182 | known affected: 278 known not affected: 37 recommended: 354 | 2026-07-25T01:52:29+00:00 | Vulnerability · Source |
| CVE-2024-29040 | suse_vex | SUSE CVE CVE-2024-29040 | known affected: 514 known not affected: 162 recommended: 454 | 2026-07-25T01:52:22+00:00 | Vulnerability · Source |
| CVE-2024-29510 | suse_vex | SUSE CVE CVE-2024-29510 | known affected: 23 recommended: 133 | 2026-07-25T01:52:19+00:00 | Vulnerability · Source |
| CVE-2024-30203 | suse_vex | SUSE CVE CVE-2024-30203 | known affected: 128 recommended: 179 | 2026-07-25T01:52:16+00:00 | Vulnerability · Source |
| CVE-2024-31142 | suse_vex | SUSE CVE CVE-2024-31142 | known affected: 389 known not affected: 36 recommended: 272 | 2026-07-25T01:52:14+00:00 | Vulnerability · Source |
| CVE-2024-31949 | suse_vex | SUSE CVE CVE-2024-31949 | known not affected: 403 | 2026-07-25T01:52:11+00:00 | Vulnerability · Source |
| CVE-2024-31951 | suse_vex | SUSE CVE CVE-2024-31951 | known not affected: 405 recommended: 175 | 2026-07-25T01:52:09+00:00 | Vulnerability · Source |
| CVE-2024-32004 | suse_vex | SUSE CVE CVE-2024-32004 | known affected: 151 known not affected: 119 recommended: 472 | 2026-07-25T01:52:06+00:00 | Vulnerability · Source |
| CVE-2024-32021 | suse_vex | SUSE CVE CVE-2024-32021 | known affected: 151 known not affected: 119 recommended: 472 | 2026-07-25T01:52:04+00:00 | Vulnerability · Source |
| CVE-2024-32936 | suse_vex | SUSE CVE CVE-2024-32936 | known not affected: 318 | 2026-07-25T01:51:58+00:00 | Vulnerability · Source |
| CVE-2024-33427 | suse_vex | SUSE CVE CVE-2024-33427 | known affected: 418 recommended: 28 | 2026-07-25T01:51:55+00:00 | Vulnerability · Source |
| CVE-2024-35176 | suse_vex | SUSE CVE CVE-2024-35176 | known affected: 428 known not affected: 117 recommended: 202 | 2026-07-25T01:51:38+00:00 | Vulnerability · Source |
| CVE-2024-35367 | suse_vex | SUSE CVE CVE-2024-35367 | known affected: 466 known not affected: 158 | 2026-07-25T01:51:37+00:00 | Vulnerability · Source |
| CVE-2024-35793 | suse_vex | SUSE CVE CVE-2024-35793 | known not affected: 330 | 2026-07-25T01:51:28+00:00 | Vulnerability · Source |
| CVE-2024-35798 | suse_vex | SUSE CVE CVE-2024-35798 | known not affected: 330 | 2026-07-25T01:51:22+00:00 | Vulnerability · Source |
| CVE-2024-35816 | suse_vex | SUSE CVE CVE-2024-35816 | known not affected: 330 | 2026-07-25T01:51:16+00:00 | Vulnerability · Source |
| CVE-2024-35818 | suse_vex | SUSE CVE CVE-2024-35818 | known not affected: 330 | 2026-07-25T01:51:15+00:00 | Vulnerability · Source |
| CVE-2024-35826 | suse_vex | SUSE CVE CVE-2024-35826 | known affected: 394 known not affected: 270 recommended: 309 | 2026-07-25T01:51:13+00:00 | Vulnerability · Source |
| CVE-2024-35859 | suse_vex | SUSE CVE CVE-2024-35859 | known not affected: 330 | 2026-07-25T01:51:03+00:00 | Vulnerability · Source |
| CVE-2024-35866 | suse_vex | SUSE CVE CVE-2024-35866 | known affected: 446 known not affected: 111 recommended: 671 | 2026-07-25T01:50:56+00:00 | Vulnerability · Source |
| CVE-2024-35873 | suse_vex | SUSE CVE CVE-2024-35873 | known not affected: 330 | 2026-07-25T01:50:51+00:00 | Vulnerability · Source |
| CVE-2024-35875 | suse_vex | SUSE CVE CVE-2024-35875 | known affected: 362 known not affected: 157 recommended: 704 | 2026-07-25T01:50:49+00:00 | Vulnerability · Source |
| CVE-2024-35883 | suse_vex | SUSE CVE CVE-2024-35883 | known affected: 394 known not affected: 270 recommended: 362 | 2026-07-25T01:50:44+00:00 | Vulnerability · Source |
| CVE-2024-35893 | suse_vex | SUSE CVE CVE-2024-35893 | known affected: 526 known not affected: 10 recommended: 746 | 2026-07-25T01:50:39+00:00 | Vulnerability · Source |
| CVE-2024-35904 | suse_vex | SUSE CVE CVE-2024-35904 | known affected: 334 known not affected: 98 recommended: 814 | 2026-07-25T01:50:36+00:00 | Vulnerability · Source |