VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50299 | suse_vex | SUSE CVE CVE-2022-50299 | known affected: 391 known not affected: 186 recommended: 369 | 2026-07-26T23:37:51+00:00 | Vulnerability · Source |
| CVE-2022-50369 | suse_vex | SUSE CVE CVE-2022-50369 | known affected: 401 known not affected: 286 recommended: 255 | 2026-07-26T23:37:46+00:00 | Vulnerability · Source |
| CVE-2022-50486 | suse_vex | SUSE CVE CVE-2022-50486 | known not affected: 416 | 2026-07-26T23:37:42+00:00 | Vulnerability · Source |
| CVE-2022-50669 | suse_vex | SUSE CVE CVE-2022-50669 | known affected: 403 known not affected: 247 recommended: 196 | 2026-07-26T23:37:37+00:00 | Vulnerability · Source |
| CVE-2022-50738 | suse_vex | SUSE CVE CVE-2022-50738 | known affected: 374 known not affected: 391 recommended: 114 | 2026-07-26T23:37:34+00:00 | Vulnerability · Source |
| CVE-2022-50832 | suse_vex | SUSE CVE CVE-2022-50832 | known affected: 502 known not affected: 195 recommended: 225 | 2026-07-26T23:37:32+00:00 | Vulnerability · Source |
| CVE-2022-50835 | suse_vex | SUSE CVE CVE-2022-50835 | known affected: 354 known not affected: 341 recommended: 223 | 2026-07-26T23:37:31+00:00 | Vulnerability · Source |
| CVE-2023-0615 | suse_vex | SUSE CVE CVE-2023-0615 | known not affected: 272 | 2026-07-26T23:37:28+00:00 | Vulnerability · Source |
| CVE-2023-25363 | suse_vex | SUSE CVE CVE-2023-25363 | known not affected: 122 recommended: 851 | 2026-07-26T23:37:10+00:00 | Vulnerability · Source |
| CVE-2023-26931 | suse_vex | SUSE CVE CVE-2023-26931 | known not affected: 351 | 2026-07-26T23:37:08+00:00 | Vulnerability · Source |
| CVE-2023-26935 | suse_vex | SUSE CVE CVE-2023-26935 | known not affected: 351 | 2026-07-26T23:37:07+00:00 | Vulnerability · Source |
| CVE-2023-32257 | suse_vex | SUSE CVE CVE-2023-32257 | known not affected: 416 | 2026-07-26T23:37:03+00:00 | Vulnerability · Source |
| CVE-2023-43010 | suse_vex | SUSE CVE CVE-2023-43010 | known affected: 88 recommended: 524 | 2026-07-26T23:36:59+00:00 | Vulnerability · Source |
| CVE-2023-52706 | suse_vex | SUSE CVE CVE-2023-52706 | known not affected: 330 | 2026-07-26T23:36:46+00:00 | Vulnerability · Source |
| CVE-2023-52802 | suse_vex | SUSE CVE CVE-2023-52802 | known not affected: 324 recommended: 42 | 2026-07-26T23:36:44+00:00 | Vulnerability · Source |
| CVE-2023-52909 | suse_vex | SUSE CVE CVE-2023-52909 | known affected: 340 known not affected: 248 recommended: 288 | 2026-07-26T23:36:40+00:00 | Vulnerability · Source |
| CVE-2023-52983 | suse_vex | SUSE CVE CVE-2023-52983 | known affected: 334 known not affected: 243 recommended: 226 | 2026-07-26T23:36:38+00:00 | Vulnerability · Source |
| CVE-2023-53186 | suse_vex | SUSE CVE CVE-2023-53186 | known affected: 55 known not affected: 361 | 2026-07-26T23:36:34+00:00 | Vulnerability · Source |
| CVE-2023-53202 | suse_vex | SUSE CVE CVE-2023-53202 | known affected: 112 known not affected: 304 recommended: 49 | 2026-07-26T23:36:32+00:00 | Vulnerability · Source |
| CVE-2023-53203 | suse_vex | SUSE CVE CVE-2023-53203 | known not affected: 416 | 2026-07-26T23:36:31+00:00 | Vulnerability · Source |
| CVE-2023-53381 | suse_vex | SUSE CVE CVE-2023-53381 | known affected: 344 known not affected: 304 recommended: 233 | 2026-07-26T23:36:28+00:00 | Vulnerability · Source |
| CVE-2023-53439 | suse_vex | SUSE CVE CVE-2023-53439 | known not affected: 416 | 2026-07-26T23:36:27+00:00 | Vulnerability · Source |
| CVE-2023-53473 | suse_vex | SUSE CVE CVE-2023-53473 | known affected: 395 known not affected: 253 recommended: 235 | 2026-07-26T23:36:25+00:00 | Vulnerability · Source |
| CVE-2023-53498 | suse_vex | SUSE CVE CVE-2023-53498 | known affected: 381 known not affected: 267 recommended: 206 | 2026-07-26T23:36:23+00:00 | Vulnerability · Source |
| CVE-2023-53535 | suse_vex | SUSE CVE CVE-2023-53535 | known affected: 185 known not affected: 231 | 2026-07-26T23:36:21+00:00 | Vulnerability · Source |
| CVE-2023-53629 | suse_vex | SUSE CVE CVE-2023-53629 | known affected: 112 known not affected: 304 | 2026-07-26T23:36:19+00:00 | Vulnerability · Source |
| CVE-2023-53637 | suse_vex | SUSE CVE CVE-2023-53637 | known affected: 405 known not affected: 253 recommended: 196 | 2026-07-26T23:36:17+00:00 | Vulnerability · Source |
| CVE-2023-53684 | suse_vex | SUSE CVE CVE-2023-53684 | known affected: 224 known not affected: 160 | 2026-07-26T23:36:16+00:00 | Vulnerability · Source |
| CVE-2023-54248 | suse_vex | SUSE CVE CVE-2023-54248 | known not affected: 453 | 2026-07-26T23:36:11+00:00 | Vulnerability · Source |
| CVE-2024-8388 | suse_vex | SUSE CVE CVE-2024-8388 | known not affected: 170 recommended: 9 | 2026-07-26T23:36:03+00:00 | Vulnerability · Source |
| CVE-2024-9956 | suse_vex | SUSE CVE CVE-2024-9956 | recommended: 21 | 2026-07-26T23:36:00+00:00 | Vulnerability · Source |
| CVE-2024-11695 | suse_vex | SUSE CVE CVE-2024-11695 | known affected: 29 recommended: 235 | 2026-07-26T23:35:57+00:00 | Vulnerability · Source |
| CVE-2024-11831 | suse_vex | SUSE CVE CVE-2024-11831 | known affected: 105 known not affected: 407 recommended: 24 | 2026-07-26T23:35:56+00:00 | Vulnerability · Source |
| CVE-2024-26597 | suse_vex | SUSE CVE CVE-2024-26597 | known affected: 417 known not affected: 198 recommended: 519 | 2026-07-26T23:35:50+00:00 | Vulnerability · Source |
| CVE-2024-26686 | suse_vex | SUSE CVE CVE-2024-26686 | recommended: 20 | 2026-07-26T23:35:47+00:00 | Vulnerability · Source |
| CVE-2024-26769 | suse_vex | SUSE CVE CVE-2024-26769 | known affected: 394 known not affected: 237 recommended: 610 | 2026-07-26T23:35:45+00:00 | Vulnerability · Source |
| CVE-2024-26789 | suse_vex | SUSE CVE CVE-2024-26789 | known not affected: 353 recommended: 206 | 2026-07-26T23:35:44+00:00 | Vulnerability · Source |
| CVE-2024-27000 | suse_vex | SUSE CVE CVE-2024-27000 | known affected: 572 known not affected: 50 recommended: 675 | 2026-07-26T23:35:36+00:00 | Vulnerability · Source |
| CVE-2024-29018 | suse_vex | SUSE CVE CVE-2024-29018 | known not affected: 85 recommended: 183 | 2026-07-26T23:35:33+00:00 | Vulnerability · Source |
| CVE-2024-32473 | suse_vex | SUSE CVE CVE-2024-32473 | known not affected: 127 | 2026-07-26T23:35:32+00:00 | Vulnerability · Source |
| CVE-2024-40996 | suse_vex | SUSE CVE CVE-2024-40996 | known not affected: 318 recommended: 59 | 2026-07-26T23:35:20+00:00 | Vulnerability · Source |
| CVE-2024-43374 | suse_vex | SUSE CVE CVE-2024-43374 | known affected: 386 known not affected: 121 recommended: 167 | 2026-07-26T23:35:13+00:00 | Vulnerability · Source |
| CVE-2024-43835 | suse_vex | SUSE CVE CVE-2024-43835 | known affected: 532 known not affected: 145 recommended: 610 | 2026-07-26T23:35:12+00:00 | Vulnerability · Source |
| CVE-2024-43901 | suse_vex | SUSE CVE CVE-2024-43901 | known not affected: 311 recommended: 59 | 2026-07-26T23:35:10+00:00 | Vulnerability · Source |
| CVE-2024-46696 | suse_vex | SUSE CVE CVE-2024-46696 | known not affected: 325 | 2026-07-26T23:35:03+00:00 | Vulnerability · Source |
| CVE-2024-46711 | suse_vex | SUSE CVE CVE-2024-46711 | known affected: 394 known not affected: 314 recommended: 51 | 2026-07-26T23:35:01+00:00 | Vulnerability · Source |
| CVE-2024-50094 | suse_vex | SUSE CVE CVE-2024-50094 | known not affected: 370 recommended: 65 | 2026-07-26T23:34:53+00:00 | Vulnerability · Source |
| CVE-2024-50291 | suse_vex | SUSE CVE CVE-2024-50291 | known not affected: 372 recommended: 59 | 2026-07-26T23:34:49+00:00 | Vulnerability · Source |
| CVE-2024-53077 | suse_vex | SUSE CVE CVE-2024-53077 | known not affected: 372 | 2026-07-26T23:34:47+00:00 | Vulnerability · Source |
| CVE-2024-53145 | suse_vex | SUSE CVE CVE-2024-53145 | known not affected: 438 | 2026-07-26T23:34:44+00:00 | Vulnerability · Source |