VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-52971 | suse_vex | SUSE CVE CVE-2023-52971 | known affected: 0 known not affected: 295 recommended: 90 | 2026-10-16T02:39:30+00:00 | Vulnerability · Source |
| CVE-2023-52976 | suse_vex | SUSE CVE CVE-2023-52976 | known affected: 334 known not affected: 183 recommended: 280 | 2026-10-16T02:39:28+00:00 | Vulnerability · Source |
| CVE-2023-52979 | suse_vex | SUSE CVE CVE-2023-52979 | known affected: 346 known not affected: 303 recommended: 248 | 2026-10-16T02:39:25+00:00 | Vulnerability · Source |
| CVE-2023-52980 | suse_vex | SUSE CVE CVE-2023-52980 | known affected: 0 known not affected: 456 | 2026-10-16T02:39:23+00:00 | Vulnerability · Source |
| CVE-2023-52982 | suse_vex | SUSE CVE CVE-2023-52982 | known affected: 369 known not affected: 443 recommended: 95 | 2026-10-16T02:39:20+00:00 | Vulnerability · Source |
| CVE-2023-52983 | suse_vex | SUSE CVE CVE-2023-52983 | known affected: 334 known not affected: 339 recommended: 226 | 2026-10-16T02:39:18+00:00 | Vulnerability · Source |
| CVE-2023-52987 | suse_vex | SUSE CVE CVE-2023-52987 | known affected: 0 known not affected: 456 | 2026-10-16T02:39:15+00:00 | Vulnerability · Source |
| CVE-2023-52992 | suse_vex | SUSE CVE CVE-2023-52992 | known affected: 403 known not affected: 274 recommended: 280 | 2026-10-16T02:39:13+00:00 | Vulnerability · Source |
| CVE-2023-52993 | suse_vex | SUSE CVE CVE-2023-52993 | known affected: 534 known not affected: 121 recommended: 317 | 2026-10-16T02:39:09+00:00 | Vulnerability · Source |
| CVE-2023-52994 | suse_vex | SUSE CVE CVE-2023-52994 | known affected: 430 known not affected: 331 recommended: 153 | 2026-10-16T02:39:07+00:00 | Vulnerability · Source |
| CVE-2023-52995 | suse_vex | SUSE CVE CVE-2023-52995 | known affected: 61 known not affected: 395 | 2026-10-16T02:39:05+00:00 | Vulnerability · Source |
| CVE-2023-52996 | suse_vex | SUSE CVE CVE-2023-52996 | known affected: 130 known not affected: 326 | 2026-10-16T02:39:03+00:00 | Vulnerability · Source |
| CVE-2023-52998 | suse_vex | SUSE CVE CVE-2023-52998 | known affected: 0 known not affected: 456 | 2026-10-16T02:39:00+00:00 | Vulnerability · Source |
| CVE-2023-53000 | suse_vex | SUSE CVE CVE-2023-53000 | known affected: 32 known not affected: 213 recommended: 298 | 2026-10-16T02:38:58+00:00 | Vulnerability · Source |
| CVE-2023-53001 | suse_vex | SUSE CVE CVE-2023-53001 | known affected: 369 known not affected: 461 recommended: 95 | 2026-10-16T02:38:55+00:00 | Vulnerability · Source |
| CVE-2023-53002 | suse_vex | SUSE CVE CVE-2023-53002 | known affected: 430 known not affected: 334 recommended: 173 | 2026-10-16T02:38:53+00:00 | Vulnerability · Source |
| CVE-2023-53004 | suse_vex | SUSE CVE CVE-2023-53004 | known affected: 0 known not affected: 456 recommended: 58 | 2026-10-16T02:38:52+00:00 | Vulnerability · Source |
| CVE-2023-53005 | suse_vex | SUSE CVE CVE-2023-53005 | known affected: 403 known not affected: 274 recommended: 222 | 2026-10-16T02:38:49+00:00 | Vulnerability · Source |
| CVE-2023-53006 | suse_vex | SUSE CVE CVE-2023-53006 | known affected: 496 known not affected: 127 recommended: 306 | 2026-10-16T02:38:47+00:00 | Vulnerability · Source |
| CVE-2023-53007 | suse_vex | SUSE CVE CVE-2023-53007 | known affected: 496 known not affected: 128 recommended: 248 | 2026-10-16T02:38:44+00:00 | Vulnerability · Source |
| CVE-2023-53010 | suse_vex | SUSE CVE CVE-2023-53010 | known affected: 497 known not affected: 121 recommended: 340 | 2026-10-16T02:38:41+00:00 | Vulnerability · Source |
| CVE-2023-53011 | suse_vex | SUSE CVE CVE-2023-53011 | known affected: 61 known not affected: 395 | 2026-10-16T02:38:39+00:00 | Vulnerability · Source |
| CVE-2023-53012 | suse_vex | SUSE CVE CVE-2023-53012 | known affected: 61 known not affected: 395 recommended: 58 | 2026-10-16T02:38:37+00:00 | Vulnerability · Source |
| CVE-2023-53015 | suse_vex | SUSE CVE CVE-2023-53015 | known affected: 334 known not affected: 251 recommended: 422 | 2026-10-16T02:38:36+00:00 | Vulnerability · Source |
| CVE-2023-53017 | suse_vex | SUSE CVE CVE-2023-53017 | known affected: 0 known not affected: 456 recommended: 58 | 2026-10-16T02:38:34+00:00 | Vulnerability · Source |
| CVE-2023-53019 | suse_vex | SUSE CVE CVE-2023-53019 | known affected: 500 known not affected: 123 recommended: 320 | 2026-10-16T02:38:32+00:00 | Vulnerability · Source |
| CVE-2023-53020 | suse_vex | SUSE CVE CVE-2023-53020 | known affected: 660 known not affected: 191 recommended: 77 | 2026-10-16T02:38:30+00:00 | Vulnerability · Source |
| CVE-2023-53025 | suse_vex | SUSE CVE CVE-2023-53025 | known affected: 0 known not affected: 343 recommended: 220 | 2026-10-16T02:38:28+00:00 | Vulnerability · Source |
| CVE-2023-53027 | suse_vex | SUSE CVE CVE-2023-53027 | known affected: 0 known not affected: 460 | 2026-10-16T02:38:26+00:00 | Vulnerability · Source |
| CVE-2023-53033 | suse_vex | SUSE CVE CVE-2023-53033 | known affected: 0 known not affected: 309 recommended: 286 | 2026-10-16T02:38:24+00:00 | Vulnerability · Source |
| CVE-2023-53034 | suse_vex | SUSE CVE CVE-2023-53034 | known affected: 591 known not affected: 209 recommended: 521 | 2026-10-16T02:38:22+00:00 | Vulnerability · Source |
| CVE-2023-53037 | suse_vex | SUSE CVE CVE-2023-53037 | known affected: 0 known not affected: 502 | 2026-10-16T02:38:20+00:00 | Vulnerability · Source |
| CVE-2023-53038 | suse_vex | SUSE CVE CVE-2023-53038 | known affected: 466 known not affected: 254 recommended: 272 | 2026-10-16T02:38:18+00:00 | Vulnerability · Source |
| CVE-2023-53042 | suse_vex | SUSE CVE CVE-2023-53042 | known affected: 369 known not affected: 438 recommended: 170 | 2026-10-16T02:38:16+00:00 | Vulnerability · Source |
| CVE-2023-53043 | suse_vex | SUSE CVE CVE-2023-53043 | known affected: 0 known not affected: 502 | 2026-10-16T02:38:14+00:00 | Vulnerability · Source |
| CVE-2023-53045 | suse_vex | SUSE CVE CVE-2023-53045 | known affected: 533 known not affected: 148 recommended: 251 | 2026-10-16T02:38:12+00:00 | Vulnerability · Source |
| CVE-2023-53046 | suse_vex | SUSE CVE CVE-2023-53046 | known affected: 369 known not affected: 437 recommended: 150 | 2026-10-16T02:38:10+00:00 | Vulnerability · Source |
| CVE-2023-53050 | suse_vex | SUSE CVE CVE-2023-53050 | known affected: 0 known not affected: 502 recommended: 78 | 2026-10-16T02:38:07+00:00 | Vulnerability · Source |
| CVE-2023-53054 | suse_vex | SUSE CVE CVE-2023-53054 | known affected: 408 known not affected: 312 recommended: 214 | 2026-10-16T02:38:05+00:00 | Vulnerability · Source |
| CVE-2023-53055 | suse_vex | SUSE CVE CVE-2023-53055 | known affected: 0 known not affected: 502 | 2026-10-16T02:38:03+00:00 | Vulnerability · Source |
| CVE-2023-53059 | suse_vex | SUSE CVE CVE-2023-53059 | known affected: 339 known not affected: 381 recommended: 214 | 2026-10-16T02:38:01+00:00 | Vulnerability · Source |
| CVE-2023-53061 | suse_vex | SUSE CVE CVE-2023-53061 | known affected: 0 known not affected: 502 | 2026-10-16T02:37:59+00:00 | Vulnerability · Source |
| CVE-2023-53062 | suse_vex | SUSE CVE CVE-2023-53062 | known affected: 535 known not affected: 144 recommended: 251 | 2026-10-16T02:37:56+00:00 | Vulnerability · Source |
| CVE-2023-53063 | suse_vex | SUSE CVE CVE-2023-53063 | known affected: 394 recommended: 23 | 2026-10-16T02:37:53+00:00 | Vulnerability · Source |
| CVE-2023-53066 | suse_vex | SUSE CVE CVE-2023-53066 | known affected: 505 known not affected: 161 recommended: 337 | 2026-10-16T02:37:50+00:00 | Vulnerability · Source |
| CVE-2023-53067 | suse_vex | SUSE CVE CVE-2023-53067 | known affected: 0 known not affected: 502 | 2026-10-16T02:37:48+00:00 | Vulnerability · Source |
| CVE-2023-53068 | suse_vex | SUSE CVE CVE-2023-53068 | known affected: 529 known not affected: 151 recommended: 251 | 2026-10-16T02:37:46+00:00 | Vulnerability · Source |
| CVE-2023-53069 | suse_vex | SUSE CVE CVE-2023-53069 | known affected: 61 known not affected: 441 | 2026-10-16T02:37:44+00:00 | Vulnerability · Source |
| CVE-2023-53070 | suse_vex | SUSE CVE CVE-2023-53070 | known affected: 369 known not affected: 438 recommended: 170 | 2026-10-16T02:37:42+00:00 | Vulnerability · Source |
| CVE-2023-53071 | suse_vex | SUSE CVE CVE-2023-53071 | known affected: 369 known not affected: 437 recommended: 170 | 2026-10-16T02:37:39+00:00 | Vulnerability · Source |