VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
90134 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-52871 | suse_vex | SUSE CVE CVE-2023-52871 | known affected: 269 known not affected: 164 recommended: 940 | 2026-10-11T01:05:46+00:00 | Vulnerability · Source |
| CVE-2023-52872 | suse_vex | SUSE CVE CVE-2023-52872 | known affected: 275 known not affected: 235 recommended: 805 | 2026-10-11T01:05:44+00:00 | Vulnerability · Source |
| CVE-2023-52877 | suse_vex | SUSE CVE CVE-2023-52877 | known affected: 275 known not affected: 235 recommended: 825 | 2026-10-11T01:05:42+00:00 | Vulnerability · Source |
| CVE-2023-52879 | suse_vex | SUSE CVE CVE-2023-52879 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-11T01:05:40+00:00 | Vulnerability · Source |
| CVE-2023-52881 | suse_vex | SUSE CVE CVE-2023-52881 | known affected: 419 recommended: 1163 | 2026-10-11T01:05:38+00:00 | Vulnerability · Source |
| CVE-2023-52883 | suse_vex | SUSE CVE CVE-2023-52883 | known affected: 394 known not affected: 342 recommended: 353 | 2026-10-11T01:05:36+00:00 | Vulnerability · Source |
| CVE-2023-52884 | suse_vex | SUSE CVE CVE-2023-52884 | known affected: 419 known not affected: 225 recommended: 709 | 2026-10-11T01:05:34+00:00 | Vulnerability · Source |
| CVE-2023-52885 | suse_vex | SUSE CVE CVE-2023-52885 | known affected: 385 known not affected: 16 recommended: 987 | 2026-10-11T01:05:32+00:00 | Vulnerability · Source |
| CVE-2023-52886 | suse_vex | SUSE CVE CVE-2023-52886 | known not affected: 201 recommended: 682 | 2026-10-11T01:05:31+00:00 | Vulnerability · Source |
| CVE-2023-52888 | suse_vex | SUSE CVE CVE-2023-52888 | known affected: 394 known not affected: 320 recommended: 318 | 2026-10-11T01:05:29+00:00 | Vulnerability · Source |
| CVE-2023-52893 | suse_vex | SUSE CVE CVE-2023-52893 | known affected: 493 known not affected: 63 recommended: 495 | 2026-10-11T01:05:27+00:00 | Vulnerability · Source |
| CVE-2023-52896 | suse_vex | SUSE CVE CVE-2023-52896 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-11T01:05:25+00:00 | Vulnerability · Source |
| CVE-2023-52899 | suse_vex | SUSE CVE CVE-2023-52899 | known affected: 483 known not affected: 212 recommended: 288 | 2026-10-11T01:05:23+00:00 | Vulnerability · Source |
| CVE-2023-52905 | suse_vex | SUSE CVE CVE-2023-52905 | known affected: 310 known not affected: 250 recommended: 465 | 2026-10-11T01:05:21+00:00 | Vulnerability · Source |
| CVE-2023-52909 | suse_vex | SUSE CVE CVE-2023-52909 | known affected: 340 known not affected: 309 recommended: 288 | 2026-10-11T01:05:18+00:00 | Vulnerability · Source |
| CVE-2023-52910 | suse_vex | SUSE CVE CVE-2023-52910 | known affected: 340 known not affected: 250 recommended: 288 | 2026-10-11T01:05:16+00:00 | Vulnerability · Source |
| CVE-2023-52916 | suse_vex | SUSE CVE CVE-2023-52916 | known affected: 492 known not affected: 200 recommended: 640 | 2026-10-11T01:05:14+00:00 | Vulnerability · Source |
| CVE-2023-52920 | suse_vex | SUSE CVE CVE-2023-52920 | known affected: 520 known not affected: 327 recommended: 390 | 2026-10-11T01:05:13+00:00 | Vulnerability · Source |
| CVE-2023-52921 | suse_vex | SUSE CVE CVE-2023-52921 | known affected: 361 known not affected: 359 recommended: 549 | 2026-10-11T01:05:11+00:00 | Vulnerability · Source |
| CVE-2023-52923 | suse_vex | SUSE CVE CVE-2023-52923 | known affected: 426 known not affected: 213 recommended: 582 | 2026-10-11T01:05:09+00:00 | Vulnerability · Source |
| CVE-2023-52924 | suse_vex | SUSE CVE CVE-2023-52924 | known affected: 344 known not affected: 438 recommended: 655 | 2026-10-11T01:05:07+00:00 | Vulnerability · Source |
| CVE-2023-52926 | suse_vex | SUSE CVE CVE-2023-52926 | known affected: 394 known not affected: 410 recommended: 279 | 2026-10-11T01:05:06+00:00 | Vulnerability · Source |
| CVE-2023-52928 | suse_vex | SUSE CVE CVE-2023-52928 | known affected: 369 known not affected: 399 recommended: 153 | 2026-10-11T01:05:04+00:00 | Vulnerability · Source |
| CVE-2023-52931 | suse_vex | SUSE CVE CVE-2023-52931 | known affected: 369 known not affected: 398 recommended: 173 | 2026-10-11T01:05:02+00:00 | Vulnerability · Source |
| CVE-2023-52933 | suse_vex | SUSE CVE CVE-2023-52933 | known affected: 403 known not affected: 223 recommended: 334 | 2026-10-11T01:05:00+00:00 | Vulnerability · Source |
| CVE-2023-52934 | suse_vex | SUSE CVE CVE-2023-52934 | known not affected: 459 recommended: 58 | 2026-10-11T01:04:59+00:00 | Vulnerability · Source |
| CVE-2023-52939 | suse_vex | SUSE CVE CVE-2023-52939 | known affected: 403 known not affected: 279 recommended: 280 | 2026-10-11T01:04:57+00:00 | Vulnerability · Source |
| CVE-2023-52941 | suse_vex | SUSE CVE CVE-2023-52941 | known affected: 334 known not affected: 346 recommended: 263 | 2026-10-11T01:04:55+00:00 | Vulnerability · Source |
| CVE-2023-52971 | suse_vex | SUSE CVE CVE-2023-52971 | known not affected: 295 recommended: 90 | 2026-10-11T01:04:53+00:00 | Vulnerability · Source |
| CVE-2023-52973 | suse_vex | SUSE CVE CVE-2023-52973 | known affected: 60 known not affected: 189 recommended: 376 | 2026-10-11T01:04:50+00:00 | Vulnerability · Source |
| CVE-2023-52984 | suse_vex | SUSE CVE CVE-2023-52984 | known affected: 334 known not affected: 348 recommended: 280 | 2026-10-11T01:04:48+00:00 | Vulnerability · Source |
| CVE-2023-52985 | suse_vex | SUSE CVE CVE-2023-52985 | known not affected: 459 recommended: 58 | 2026-10-11T01:04:46+00:00 | Vulnerability · Source |
| CVE-2023-52988 | suse_vex | SUSE CVE CVE-2023-52988 | known affected: 534 known not affected: 124 recommended: 317 | 2026-10-11T01:04:44+00:00 | Vulnerability · Source |
| CVE-2023-52992 | suse_vex | SUSE CVE CVE-2023-52992 | known affected: 403 known not affected: 277 recommended: 280 | 2026-10-11T01:04:41+00:00 | Vulnerability · Source |
| CVE-2023-52994 | suse_vex | SUSE CVE CVE-2023-52994 | known affected: 430 known not affected: 334 recommended: 153 | 2026-10-11T01:04:38+00:00 | Vulnerability · Source |
| CVE-2023-52997 | suse_vex | SUSE CVE CVE-2023-52997 | known affected: 646 known not affected: 148 recommended: 118 | 2026-10-11T01:04:37+00:00 | Vulnerability · Source |
| CVE-2023-53001 | suse_vex | SUSE CVE CVE-2023-53001 | known affected: 369 known not affected: 464 recommended: 95 | 2026-10-11T01:04:34+00:00 | Vulnerability · Source |
| CVE-2023-53002 | suse_vex | SUSE CVE CVE-2023-53002 | known affected: 430 known not affected: 337 recommended: 173 | 2026-10-11T01:04:33+00:00 | Vulnerability · Source |
| CVE-2023-53009 | suse_vex | SUSE CVE CVE-2023-53009 | known affected: 430 known not affected: 338 recommended: 173 | 2026-10-11T01:04:30+00:00 | Vulnerability · Source |
| CVE-2023-53012 | suse_vex | SUSE CVE CVE-2023-53012 | known affected: 61 known not affected: 398 recommended: 58 | 2026-10-11T01:04:29+00:00 | Vulnerability · Source |
| CVE-2023-53017 | suse_vex | SUSE CVE CVE-2023-53017 | known not affected: 459 recommended: 58 | 2026-10-11T01:04:27+00:00 | Vulnerability · Source |
| CVE-2023-53019 | suse_vex | SUSE CVE CVE-2023-53019 | known affected: 500 known not affected: 126 recommended: 320 | 2026-10-11T01:04:25+00:00 | Vulnerability · Source |
| CVE-2023-53020 | suse_vex | SUSE CVE CVE-2023-53020 | known affected: 660 known not affected: 194 recommended: 77 | 2026-10-11T01:04:23+00:00 | Vulnerability · Source |
| CVE-2023-53024 | suse_vex | SUSE CVE CVE-2023-53024 | known affected: 455 known not affected: 133 recommended: 402 | 2026-10-11T01:04:21+00:00 | Vulnerability · Source |
| CVE-2023-53025 | suse_vex | SUSE CVE CVE-2023-53025 | known not affected: 346 recommended: 220 | 2026-10-11T01:04:19+00:00 | Vulnerability · Source |
| CVE-2023-53026 | suse_vex | SUSE CVE CVE-2023-53026 | known affected: 334 known not affected: 310 recommended: 382 | 2026-10-11T01:04:17+00:00 | Vulnerability · Source |
| CVE-2023-53028 | suse_vex | SUSE CVE CVE-2023-53028 | known affected: 334 known not affected: 346 recommended: 300 | 2026-10-11T01:04:15+00:00 | Vulnerability · Source |
| CVE-2023-53029 | suse_vex | SUSE CVE CVE-2023-53029 | known affected: 334 known not affected: 346 recommended: 276 | 2026-10-11T01:04:13+00:00 | Vulnerability · Source |
| CVE-2023-53031 | suse_vex | SUSE CVE CVE-2023-53031 | known affected: 592 known not affected: 122 recommended: 179 | 2026-10-11T01:04:10+00:00 | Vulnerability · Source |
| CVE-2023-53032 | suse_vex | SUSE CVE CVE-2023-53032 | known affected: 649 known not affected: 176 recommended: 54 | 2026-10-11T01:04:08+00:00 | Vulnerability · Source |