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-5981 | suse_vex | SUSE CVE CVE-2023-5981 | known affected: 389 known not affected: 31 recommended: 524 | 2026-10-16T13:55:24+00:00 | Vulnerability · Source |
| CVE-2023-5992 | suse_vex | SUSE CVE CVE-2023-5992 | known affected: 412 known not affected: 1 recommended: 41 | 2026-10-16T13:55:22+00:00 | Vulnerability · Source |
| CVE-2023-6039 | suse_vex | SUSE CVE CVE-2023-6039 | known affected: 230 known not affected: 300 recommended: 923 | 2026-10-16T13:55:20+00:00 | Vulnerability · Source |
| CVE-2023-6121 | suse_vex | SUSE CVE CVE-2023-6121 | known affected: 270 known not affected: 82 recommended: 1112 | 2026-10-16T13:55:17+00:00 | Vulnerability · Source |
| CVE-2023-6129 | suse_vex | SUSE CVE CVE-2023-6129 | known not affected: 753 recommended: 150 | 2026-10-16T13:42:19+00:00 | Vulnerability · Source |
| CVE-2023-6208 | suse_vex | SUSE CVE CVE-2023-6208 | known affected: 52 recommended: 283 | 2026-10-16T13:42:17+00:00 | Vulnerability · Source |
| CVE-2023-6209 | suse_vex | SUSE CVE CVE-2023-6209 | known affected: 52 recommended: 283 | 2026-10-16T13:42:16+00:00 | Vulnerability · Source |
| CVE-2023-6237 | suse_vex | SUSE CVE CVE-2023-6237 | known affected: 27 known not affected: 753 recommended: 150 | 2026-10-16T13:42:14+00:00 | Vulnerability · Source |
| CVE-2023-6238 | suse_vex | SUSE CVE CVE-2023-6238 | known affected: 394 known not affected: 422 recommended: 384 | 2026-10-16T13:42:12+00:00 | Vulnerability · Source |
| CVE-2023-6240 | suse_vex | SUSE CVE CVE-2023-6240 | recommended: 78 | 2026-10-16T13:42:11+00:00 | Vulnerability · Source |
| CVE-2023-6246 | suse_vex | SUSE CVE CVE-2023-6246 | known not affected: 709 recommended: 196 | 2026-10-16T13:42:09+00:00 | Vulnerability · Source |
| CVE-2023-6270 | suse_vex | SUSE CVE CVE-2023-6270 | known affected: 402 known not affected: 26 recommended: 1137 | 2026-10-16T13:42:08+00:00 | Vulnerability · Source |
| CVE-2023-6377 | suse_vex | SUSE CVE CVE-2023-6377 | known affected: 403 known not affected: 24 recommended: 232 | 2026-10-16T13:42:06+00:00 | Vulnerability · Source |
| CVE-2023-6478 | suse_vex | SUSE CVE CVE-2023-6478 | known affected: 416 recommended: 232 | 2026-10-16T13:42:04+00:00 | Vulnerability · Source |
| CVE-2023-6507 | suse_vex | SUSE CVE CVE-2023-6507 | known affected: 0 known not affected: 593 recommended: 42 | 2026-10-16T13:42:02+00:00 | Vulnerability · Source |
| CVE-2023-6516 | suse_vex | SUSE CVE CVE-2023-6516 | known affected: 388 known not affected: 147 recommended: 451 | 2026-10-16T13:42:00+00:00 | Vulnerability · Source |
| CVE-2023-6536 | suse_vex | SUSE CVE CVE-2023-6536 | known affected: 253 known not affected: 210 recommended: 1040 | 2026-10-16T13:41:55+00:00 | Vulnerability · Source |
| CVE-2023-6601 | suse_vex | SUSE CVE CVE-2023-6601 | known affected: 117 known not affected: 826 recommended: 200 | 2026-10-16T13:41:51+00:00 | Vulnerability · Source |
| CVE-2023-6602 | suse_vex | SUSE CVE CVE-2023-6602 | known affected: 1057 recommended: 74 | 2026-10-16T13:41:50+00:00 | Vulnerability · Source |
| CVE-2023-6603 | suse_vex | SUSE CVE CVE-2023-6603 | known affected: 1058 | 2026-10-16T13:41:48+00:00 | Vulnerability · Source |
| CVE-2023-6604 | suse_vex | SUSE CVE CVE-2023-6604 | known affected: 806 known not affected: 270 recommended: 35 | 2026-10-16T13:41:46+00:00 | Vulnerability · Source |
| CVE-2023-6606 | suse_vex | SUSE CVE CVE-2023-6606 | known affected: 382 known not affected: 23 recommended: 1184 | 2026-10-16T13:41:45+00:00 | Vulnerability · Source |
| CVE-2023-6679 | suse_vex | SUSE CVE CVE-2023-6679 | known affected: 0 known not affected: 406 recommended: 291 | 2026-10-16T13:41:43+00:00 | Vulnerability · Source |
| CVE-2023-6704 | suse_vex | SUSE CVE CVE-2023-6704 | known affected: 18 recommended: 60 | 2026-10-16T13:41:42+00:00 | Vulnerability · Source |
| CVE-2023-6779 | suse_vex | SUSE CVE CVE-2023-6779 | known not affected: 709 recommended: 183 | 2026-10-16T13:41:40+00:00 | Vulnerability · Source |
| CVE-2023-6780 | suse_vex | SUSE CVE CVE-2023-6780 | known not affected: 709 recommended: 183 | 2026-10-16T13:41:38+00:00 | Vulnerability · Source |
| CVE-2023-6817 | suse_vex | SUSE CVE CVE-2023-6817 | known affected: 300 known not affected: 308 recommended: 894 | 2026-10-16T13:41:37+00:00 | Vulnerability · Source |
| CVE-2023-6859 | suse_vex | SUSE CVE CVE-2023-6859 | known affected: 36 recommended: 265 | 2026-10-16T13:41:35+00:00 | Vulnerability · Source |
| CVE-2023-6860 | suse_vex | SUSE CVE CVE-2023-6860 | known affected: 36 recommended: 265 | 2026-10-16T13:41:34+00:00 | Vulnerability · Source |
| CVE-2023-6861 | suse_vex | SUSE CVE CVE-2023-6861 | known affected: 36 recommended: 265 | 2026-10-16T13:41:32+00:00 | Vulnerability · Source |
| CVE-2023-6862 | suse_vex | SUSE CVE CVE-2023-6862 | known affected: 36 recommended: 256 | 2026-10-16T13:41:31+00:00 | Vulnerability · Source |
| CVE-2023-6863 | suse_vex | SUSE CVE CVE-2023-6863 | known affected: 36 recommended: 265 | 2026-10-16T13:41:29+00:00 | Vulnerability · Source |
| CVE-2023-6866 | suse_vex | SUSE CVE CVE-2023-6866 | known affected: 36 recommended: 9 | 2026-10-16T13:41:28+00:00 | Vulnerability · Source |
| CVE-2023-6869 | suse_vex | SUSE CVE CVE-2023-6869 | known affected: 36 recommended: 9 | 2026-10-16T13:41:27+00:00 | Vulnerability · Source |
| CVE-2023-6870 | suse_vex | SUSE CVE CVE-2023-6870 | known affected: 36 recommended: 9 | 2026-10-16T13:41:25+00:00 | Vulnerability · Source |
| CVE-2023-6872 | suse_vex | SUSE CVE CVE-2023-6872 | known affected: 36 recommended: 9 | 2026-10-16T13:41:24+00:00 | Vulnerability · Source |
| CVE-2023-6915 | suse_vex | SUSE CVE CVE-2023-6915 | known affected: 320 known not affected: 236 recommended: 910 | 2026-10-16T13:41:22+00:00 | Vulnerability · Source |
| CVE-2023-6918 | suse_vex | SUSE CVE CVE-2023-6918 | known affected: 234 known not affected: 180 recommended: 338 | 2026-10-16T13:41:20+00:00 | Vulnerability · Source |
| CVE-2023-6931 | suse_vex | SUSE CVE CVE-2023-6931 | known affected: 266 known not affected: 6 recommended: 1246 | 2026-10-16T13:41:18+00:00 | Vulnerability · Source |
| CVE-2023-6932 | suse_vex | SUSE CVE CVE-2023-6932 | known affected: 296 recommended: 1407 | 2026-10-16T13:41:16+00:00 | Vulnerability · Source |
| CVE-2023-7008 | suse_vex | SUSE CVE CVE-2023-7008 | known affected: 500 known not affected: 516 recommended: 361 | 2026-10-16T13:41:14+00:00 | Vulnerability · Source |
| CVE-2023-7042 | suse_vex | SUSE CVE CVE-2023-7042 | known affected: 335 known not affected: 160 recommended: 1065 | 2026-10-16T13:41:12+00:00 | Vulnerability · Source |
| CVE-2023-7101 | suse_vex | SUSE CVE CVE-2023-7101 | known affected: 13 recommended: 40 | 2026-10-16T13:41:10+00:00 | Vulnerability · Source |
| CVE-2023-7216 | suse_vex | SUSE CVE CVE-2023-7216 | known affected: 3 known not affected: 95 | 2026-10-16T13:41:07+00:00 | Vulnerability · Source |
| CVE-2023-7256 | suse_vex | SUSE CVE CVE-2023-7256 | known affected: 388 recommended: 164 | 2026-10-16T13:41:05+00:00 | Vulnerability · Source |
| CVE-2023-7324 | suse_vex | SUSE CVE CVE-2023-7324 | known affected: 556 known not affected: 147 recommended: 219 | 2026-10-16T13:41:02+00:00 | Vulnerability · Source |
| CVE-2023-20032 | suse_vex | SUSE CVE CVE-2023-20032 | known affected: 1 recommended: 224 | 2026-10-16T13:41:00+00:00 | Vulnerability · Source |
| CVE-2023-20526 | suse_vex | SUSE CVE CVE-2023-20526 | known affected: 30 recommended: 1381 | 2026-10-16T13:40:58+00:00 | Vulnerability · Source |
| CVE-2023-20533 | suse_vex | SUSE CVE CVE-2023-20533 | known affected: 30 recommended: 1346 | 2026-10-16T13:40:56+00:00 | Vulnerability · Source |
| CVE-2023-20566 | suse_vex | SUSE CVE CVE-2023-20566 | known affected: 30 recommended: 1346 | 2026-10-16T13:40:55+00:00 | Vulnerability · Source |