VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
90149 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-3567 | suse_vex | SUSE CVE CVE-2023-3567 | known affected: 284 recommended: 1618 | 2026-10-11T01:22:57+00:00 | Vulnerability · Source |
| CVE-2023-3576 | suse_vex | SUSE CVE CVE-2023-3576 | known affected: 537 recommended: 101 | 2026-10-11T01:22:55+00:00 | Vulnerability · Source |
| CVE-2023-3609 | suse_vex | SUSE CVE CVE-2023-3609 | known affected: 254 known not affected: 126 recommended: 1390 | 2026-10-11T01:22:53+00:00 | Vulnerability · Source |
| CVE-2023-3750 | suse_vex | SUSE CVE CVE-2023-3750 | known affected: 394 known not affected: 1516 recommended: 533 | 2026-10-11T01:22:51+00:00 | Vulnerability · Source |
| CVE-2023-3758 | suse_vex | SUSE CVE CVE-2023-3758 | known affected: 293 known not affected: 19 recommended: 995 | 2026-10-11T01:22:49+00:00 | Vulnerability · Source |
| CVE-2023-3817 | suse_vex | SUSE CVE CVE-2023-3817 | known affected: 393 known not affected: 151 recommended: 874 | 2026-10-11T01:22:47+00:00 | Vulnerability · Source |
| CVE-2023-3824 | suse_vex | SUSE CVE CVE-2023-3824 | recommended: 3102 | 2026-10-11T01:22:45+00:00 | Vulnerability · Source |
| CVE-2023-3863 | suse_vex | SUSE CVE CVE-2023-3863 | known affected: 184 known not affected: 6 recommended: 1300 | 2026-10-11T01:22:43+00:00 | Vulnerability · Source |
| CVE-2023-3867 | suse_vex | SUSE CVE CVE-2023-3867 | known affected: 394 known not affected: 406 recommended: 318 | 2026-10-11T01:22:41+00:00 | Vulnerability · Source |
| CVE-2023-3966 | suse_vex | SUSE CVE CVE-2023-3966 | known affected: 195 known not affected: 62 recommended: 665 | 2026-10-11T01:22:40+00:00 | Vulnerability · Source |
| CVE-2023-4004 | suse_vex | SUSE CVE CVE-2023-4004 | known affected: 179 known not affected: 249 recommended: 1262 | 2026-10-11T01:22:38+00:00 | Vulnerability · Source |
| CVE-2023-4015 | suse_vex | SUSE CVE CVE-2023-4015 | known not affected: 316 recommended: 58 | 2026-10-11T01:22:36+00:00 | Vulnerability · Source |
| CVE-2023-4047 | suse_vex | SUSE CVE CVE-2023-4047 | known affected: 54 recommended: 272 | 2026-10-11T01:22:34+00:00 | Vulnerability · Source |
| CVE-2023-4048 | suse_vex | SUSE CVE CVE-2023-4048 | known affected: 54 recommended: 272 | 2026-10-11T01:22:33+00:00 | Vulnerability · Source |
| CVE-2023-4049 | suse_vex | SUSE CVE CVE-2023-4049 | known affected: 54 recommended: 272 | 2026-10-11T01:22:31+00:00 | Vulnerability · Source |
| CVE-2023-4050 | suse_vex | SUSE CVE CVE-2023-4050 | known affected: 54 recommended: 272 | 2026-10-11T01:22:29+00:00 | Vulnerability · Source |
| CVE-2023-4052 | suse_vex | SUSE CVE CVE-2023-4052 | known affected: 54 recommended: 247 | 2026-10-11T01:22:27+00:00 | Vulnerability · Source |
| CVE-2023-4057 | suse_vex | SUSE CVE CVE-2023-4057 | known affected: 54 recommended: 257 | 2026-10-11T01:22:26+00:00 | Vulnerability · Source |
| CVE-2023-4091 | suse_vex | SUSE CVE CVE-2023-4091 | known affected: 728 recommended: 1376 | 2026-10-11T01:22:24+00:00 | Vulnerability · Source |
| CVE-2023-4128 | suse_vex | SUSE CVE CVE-2023-4128 | known affected: 238 known not affected: 6 recommended: 1352 | 2026-10-11T01:22:22+00:00 | Vulnerability · Source |
| CVE-2023-4130 | suse_vex | SUSE CVE CVE-2023-4130 | known affected: 394 known not affected: 465 recommended: 318 | 2026-10-11T01:22:20+00:00 | Vulnerability · Source |
| CVE-2023-4154 | suse_vex | SUSE CVE CVE-2023-4154 | known affected: 199 known not affected: 763 recommended: 1048 | 2026-10-11T01:22:16+00:00 | Vulnerability · Source |
| CVE-2023-4206 | suse_vex | SUSE CVE CVE-2023-4206 | recommended: 91 | 2026-10-11T01:22:14+00:00 | Vulnerability · Source |
| CVE-2023-4408 | suse_vex | SUSE CVE CVE-2023-4408 | known affected: 511 known not affected: 151 recommended: 570 | 2026-10-11T01:22:11+00:00 | Vulnerability · Source |
| CVE-2023-4511 | suse_vex | SUSE CVE CVE-2023-4511 | known affected: 139 recommended: 180 | 2026-10-11T01:22:06+00:00 | Vulnerability · Source |
| CVE-2023-4512 | suse_vex | SUSE CVE CVE-2023-4512 | known affected: 139 recommended: 180 | 2026-10-11T01:22:03+00:00 | Vulnerability · Source |
| CVE-2023-4527 | suse_vex | SUSE CVE CVE-2023-4527 | known not affected: 687 recommended: 839 | 2026-10-11T01:22:01+00:00 | Vulnerability · Source |
| CVE-2023-4535 | suse_vex | SUSE CVE CVE-2023-4535 | known not affected: 62 recommended: 9 | 2026-10-11T01:22:00+00:00 | Vulnerability · Source |
| CVE-2023-4563 | suse_vex | SUSE CVE CVE-2023-4563 | known affected: 263 known not affected: 204 recommended: 918 | 2026-10-11T01:21:58+00:00 | Vulnerability · Source |
| CVE-2023-4573 | suse_vex | SUSE CVE CVE-2023-4573 | known affected: 57 recommended: 114 | 2026-10-11T01:21:56+00:00 | Vulnerability · Source |
| CVE-2023-4575 | suse_vex | SUSE CVE CVE-2023-4575 | known affected: 57 recommended: 289 | 2026-10-11T01:21:55+00:00 | Vulnerability · Source |
| CVE-2023-4577 | suse_vex | SUSE CVE CVE-2023-4577 | known affected: 57 recommended: 286 | 2026-10-11T01:21:53+00:00 | Vulnerability · Source |
| CVE-2023-4580 | suse_vex | SUSE CVE CVE-2023-4580 | known affected: 57 recommended: 286 | 2026-10-11T01:21:51+00:00 | Vulnerability · Source |
| CVE-2023-4581 | suse_vex | SUSE CVE CVE-2023-4581 | known affected: 57 recommended: 289 | 2026-10-11T01:21:49+00:00 | Vulnerability · Source |
| CVE-2023-4585 | suse_vex | SUSE CVE CVE-2023-4585 | known affected: 57 recommended: 286 | 2026-10-11T01:21:47+00:00 | Vulnerability · Source |
| CVE-2023-4623 | suse_vex | SUSE CVE CVE-2023-4623 | known affected: 233 recommended: 1637 | 2026-10-11T01:21:45+00:00 | Vulnerability · Source |
| CVE-2023-4727 | suse_vex | SUSE CVE CVE-2023-4727 | recommended: 26 | 2026-10-11T01:21:43+00:00 | Vulnerability · Source |
| CVE-2023-4734 | suse_vex | SUSE CVE CVE-2023-4734 | known affected: 277 known not affected: 1 recommended: 438 | 2026-10-11T01:21:41+00:00 | Vulnerability · Source |
| CVE-2023-4735 | suse_vex | SUSE CVE CVE-2023-4735 | known affected: 277 known not affected: 1 recommended: 438 | 2026-10-11T01:21:39+00:00 | Vulnerability · Source |
| CVE-2023-4738 | suse_vex | SUSE CVE CVE-2023-4738 | known affected: 278 recommended: 438 | 2026-10-11T01:21:36+00:00 | Vulnerability · Source |
| CVE-2023-4750 | suse_vex | SUSE CVE CVE-2023-4750 | known affected: 424 recommended: 341 | 2026-10-11T01:21:34+00:00 | Vulnerability · Source |
| CVE-2023-4759 | suse_vex | SUSE CVE CVE-2023-4759 | known not affected: 33 recommended: 66 | 2026-10-11T01:21:31+00:00 | Vulnerability · Source |
| CVE-2023-4781 | suse_vex | SUSE CVE CVE-2023-4781 | known affected: 271 recommended: 432 | 2026-10-11T01:21:29+00:00 | Vulnerability · Source |
| CVE-2023-4806 | suse_vex | SUSE CVE CVE-2023-4806 | known not affected: 687 recommended: 839 | 2026-10-11T01:21:26+00:00 | Vulnerability · Source |
| CVE-2023-4807 | suse_vex | SUSE CVE CVE-2023-4807 | known not affected: 764 recommended: 120 | 2026-10-11T01:21:24+00:00 | Vulnerability · Source |
| CVE-2023-4875 | suse_vex | SUSE CVE CVE-2023-4875 | known affected: 482 recommended: 101 | 2026-10-11T01:21:22+00:00 | Vulnerability · Source |
| CVE-2023-5115 | suse_vex | SUSE CVE CVE-2023-5115 | known affected: 2 known not affected: 13 recommended: 15 | 2026-10-11T01:21:18+00:00 | Vulnerability · Source |
| CVE-2023-5157 | suse_vex | SUSE CVE CVE-2023-5157 | known not affected: 361 recommended: 46 | 2026-10-11T01:21:16+00:00 | Vulnerability · Source |
| CVE-2023-5169 | suse_vex | SUSE CVE CVE-2023-5169 | known affected: 51 recommended: 282 | 2026-10-11T01:21:15+00:00 | Vulnerability · Source |
| CVE-2023-5170 | suse_vex | SUSE CVE CVE-2023-5170 | known affected: 51 recommended: 9 | 2026-10-11T01:21:13+00:00 | Vulnerability · Source |