VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283447 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-5568 | suse_vex | SUSE CVE CVE-2023-5568 | known not affected: 1745 recommended: 286 | 2026-07-25T02:43:00+00:00 | Vulnerability · Source |
| CVE-2023-5616 | suse_vex | SUSE CVE CVE-2023-5616 | known not affected: 161 | 2026-07-25T02:42:58+00:00 | Vulnerability · Source |
| CVE-2023-5721 | suse_vex | SUSE CVE CVE-2023-5721 | known affected: 38 recommended: 287 | 2026-07-25T02:42:55+00:00 | Vulnerability · Source |
| CVE-2023-5723 | suse_vex | SUSE CVE CVE-2023-5723 | known affected: 38 recommended: 174 | 2026-07-25T02:42:53+00:00 | Vulnerability · Source |
| CVE-2023-5724 | suse_vex | SUSE CVE CVE-2023-5724 | known affected: 38 recommended: 287 | 2026-07-25T02:42:51+00:00 | Vulnerability · Source |
| CVE-2023-5725 | suse_vex | SUSE CVE CVE-2023-5725 | known affected: 38 recommended: 287 | 2026-07-25T02:42:49+00:00 | Vulnerability · Source |
| CVE-2023-5726 | suse_vex | SUSE CVE CVE-2023-5726 | known affected: 38 recommended: 281 | 2026-07-25T02:42:46+00:00 | Vulnerability · Source |
| CVE-2023-5731 | suse_vex | SUSE CVE CVE-2023-5731 | known affected: 38 recommended: 174 | 2026-07-25T02:42:44+00:00 | Vulnerability · Source |
| CVE-2023-5752 | suse_vex | SUSE CVE CVE-2023-5752 | known affected: 422 known not affected: 5 recommended: 56 | 2026-07-25T02:42:42+00:00 | Vulnerability · Source |
| CVE-2023-5869 | suse_vex | SUSE CVE CVE-2023-5869 | known affected: 551 recommended: 1839 | 2026-07-25T02:42:39+00:00 | Vulnerability · Source |
| CVE-2023-5950 | suse_vex | SUSE CVE CVE-2023-5950 | recommended: 17 | 2026-07-25T02:42:37+00:00 | Vulnerability · Source |
| CVE-2023-5992 | suse_vex | SUSE CVE CVE-2023-5992 | known affected: 408 known not affected: 1 recommended: 41 | 2026-07-25T02:42:35+00:00 | Vulnerability · Source |
| CVE-2023-6039 | suse_vex | SUSE CVE CVE-2023-6039 | known affected: 230 known not affected: 243 recommended: 896 | 2026-07-25T02:42:32+00:00 | Vulnerability · Source |
| CVE-2023-6111 | suse_vex | SUSE CVE CVE-2023-6111 | known not affected: 362 | 2026-07-25T02:42:30+00:00 | Vulnerability · Source |
| CVE-2023-6204 | suse_vex | SUSE CVE CVE-2023-6204 | known affected: 38 recommended: 278 | 2026-07-25T02:42:27+00:00 | Vulnerability · Source |
| CVE-2023-6240 | suse_vex | SUSE CVE CVE-2023-6240 | recommended: 49 | 2026-07-25T02:42:25+00:00 | Vulnerability · Source |
| CVE-2023-6277 | suse_vex | SUSE CVE CVE-2023-6277 | known not affected: 235 | 2026-07-25T02:42:23+00:00 | Vulnerability · Source |
| CVE-2023-6478 | suse_vex | SUSE CVE CVE-2023-6478 | known affected: 408 recommended: 220 | 2026-07-25T02:42:21+00:00 | Vulnerability · Source |
| CVE-2023-6516 | suse_vex | SUSE CVE CVE-2023-6516 | known affected: 344 known not affected: 128 recommended: 457 | 2026-07-25T02:42:18+00:00 | Vulnerability · Source |
| CVE-2023-6536 | suse_vex | SUSE CVE CVE-2023-6536 | known affected: 253 known not affected: 175 recommended: 984 | 2026-07-25T02:42:16+00:00 | Vulnerability · Source |
| CVE-2023-6597 | suse_vex | SUSE CVE CVE-2023-6597 | known affected: 306 known not affected: 182 recommended: 1046 | 2026-07-25T02:42:13+00:00 | Vulnerability · Source |
| CVE-2023-6602 | suse_vex | SUSE CVE CVE-2023-6602 | known affected: 966 | 2026-07-25T02:42:11+00:00 | Vulnerability · Source |
| CVE-2023-6603 | suse_vex | SUSE CVE CVE-2023-6603 | known affected: 966 | 2026-07-25T02:42:09+00:00 | Vulnerability · Source |
| CVE-2023-6604 | suse_vex | SUSE CVE CVE-2023-6604 | known affected: 703 known not affected: 263 | 2026-07-25T02:42:06+00:00 | Vulnerability · Source |
| CVE-2023-6606 | suse_vex | SUSE CVE CVE-2023-6606 | known affected: 358 known not affected: 23 recommended: 1128 | 2026-07-25T02:42:04+00:00 | Vulnerability · Source |
| CVE-2023-6610 | suse_vex | SUSE CVE CVE-2023-6610 | known affected: 282 known not affected: 30 recommended: 1063 | 2026-07-25T02:42:01+00:00 | Vulnerability · Source |
| CVE-2023-6679 | suse_vex | SUSE CVE CVE-2023-6679 | known not affected: 352 recommended: 235 | 2026-07-25T02:41:59+00:00 | Vulnerability · Source |
| CVE-2023-6856 | suse_vex | SUSE CVE CVE-2023-6856 | known affected: 28 recommended: 260 | 2026-07-25T02:41:56+00:00 | Vulnerability · Source |
| CVE-2023-6857 | suse_vex | SUSE CVE CVE-2023-6857 | known affected: 28 recommended: 260 | 2026-07-25T02:41:54+00:00 | Vulnerability · Source |
| CVE-2023-6859 | suse_vex | SUSE CVE CVE-2023-6859 | known affected: 28 recommended: 260 | 2026-07-25T02:41:52+00:00 | Vulnerability · Source |
| CVE-2023-6861 | suse_vex | SUSE CVE CVE-2023-6861 | known affected: 28 recommended: 260 | 2026-07-25T02:41:49+00:00 | Vulnerability · Source |
| CVE-2023-6863 | suse_vex | SUSE CVE CVE-2023-6863 | known affected: 28 recommended: 260 | 2026-07-25T02:41:47+00:00 | Vulnerability · Source |
| CVE-2023-6865 | suse_vex | SUSE CVE CVE-2023-6865 | known affected: 28 recommended: 202 | 2026-07-25T02:41:45+00:00 | Vulnerability · Source |
| CVE-2023-6915 | suse_vex | SUSE CVE CVE-2023-6915 | known affected: 320 known not affected: 198 recommended: 885 | 2026-07-25T02:41:41+00:00 | Vulnerability · Source |
| CVE-2023-7008 | suse_vex | SUSE CVE CVE-2023-7008 | known affected: 500 known not affected: 425 recommended: 350 | 2026-07-25T02:41:39+00:00 | Vulnerability · Source |
| CVE-2023-7104 | suse_vex | SUSE CVE CVE-2023-7104 | known affected: 394 known not affected: 264 recommended: 8 | 2026-07-25T02:41:37+00:00 | Vulnerability · Source |
| CVE-2023-7192 | suse_vex | SUSE CVE CVE-2023-7192 | known affected: 425 known not affected: 66 recommended: 705 | 2026-07-25T02:41:34+00:00 | Vulnerability · Source |
| CVE-2023-7256 | suse_vex | SUSE CVE CVE-2023-7256 | known affected: 360 recommended: 166 | 2026-07-25T02:41:32+00:00 | Vulnerability · Source |
| CVE-2023-7324 | suse_vex | SUSE CVE CVE-2023-7324 | known affected: 478 known not affected: 165 recommended: 219 | 2026-07-25T02:41:30+00:00 | Vulnerability · Source |
| CVE-2023-20032 | suse_vex | SUSE CVE CVE-2023-20032 | known affected: 1 recommended: 219 | 2026-07-25T02:41:27+00:00 | Vulnerability · Source |
| CVE-2023-20197 | suse_vex | SUSE CVE CVE-2023-20197 | recommended: 383 | 2026-07-25T02:41:25+00:00 | Vulnerability · Source |
| CVE-2023-20533 | suse_vex | SUSE CVE CVE-2023-20533 | known affected: 22 recommended: 1346 | 2026-07-25T02:41:23+00:00 | Vulnerability · Source |
| CVE-2023-20569 | suse_vex | SUSE CVE CVE-2023-20569 | known affected: 247 recommended: 3046 | 2026-07-25T02:41:20+00:00 | Vulnerability · Source |
| CVE-2023-20573 | suse_vex | SUSE CVE CVE-2023-20573 | recommended: 6 | 2026-07-25T02:41:17+00:00 | Vulnerability · Source |
| CVE-2023-20867 | suse_vex | SUSE CVE CVE-2023-20867 | known not affected: 15 recommended: 323 | 2026-07-25T02:41:13+00:00 | Vulnerability · Source |
| CVE-2023-20941 | suse_vex | SUSE CVE CVE-2023-20941 | known not affected: 327 | 2026-07-25T02:41:11+00:00 | Vulnerability · Source |
| CVE-2023-21830 | suse_vex | SUSE CVE CVE-2023-21830 | known affected: 396 known not affected: 395 recommended: 494 | 2026-07-25T02:41:08+00:00 | Vulnerability · Source |
| CVE-2023-21843 | suse_vex | SUSE CVE CVE-2023-21843 | known affected: 398 recommended: 981 | 2026-07-25T02:41:06+00:00 | Vulnerability · Source |
| CVE-2023-21930 | suse_vex | SUSE CVE CVE-2023-21930 | known affected: 438 known not affected: 1 recommended: 968 | 2026-07-25T02:41:04+00:00 | Vulnerability · Source |
| CVE-2023-21937 | suse_vex | SUSE CVE CVE-2023-21937 | known affected: 439 recommended: 947 | 2026-07-25T02:41:01+00:00 | Vulnerability · Source |