VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292115 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-3354 | suse_vex | SUSE CVE CVE-2023-3354 | known affected: 429 known not affected: 220 recommended: 1788 | 2026-07-25T02:45:31+00:00 | Vulnerability · Source |
| CVE-2023-3439 | suse_vex | SUSE CVE CVE-2023-3439 | known not affected: 361 | 2026-07-25T02:45:23+00:00 | Vulnerability · Source |
| CVE-2023-3600 | suse_vex | SUSE CVE CVE-2023-3600 | known affected: 18 recommended: 291 | 2026-07-25T02:45:19+00:00 | Vulnerability · Source |
| CVE-2023-3603 | suse_vex | SUSE CVE CVE-2023-3603 | known not affected: 213 | 2026-07-25T02:45:16+00:00 | Vulnerability · Source |
| CVE-2023-3649 | suse_vex | SUSE CVE CVE-2023-3649 | known not affected: 318 recommended: 84 | 2026-07-25T02:45:11+00:00 | Vulnerability · Source |
| CVE-2023-4010 | suse_vex | SUSE CVE CVE-2023-4010 | known not affected: 6 | 2026-07-25T02:44:58+00:00 | Vulnerability · Source |
| CVE-2023-4042 | suse_vex | SUSE CVE CVE-2023-4042 | known not affected: 149 recommended: 8 | 2026-07-25T02:44:55+00:00 | Vulnerability · Source |
| CVE-2023-4052 | suse_vex | SUSE CVE CVE-2023-4052 | known affected: 43 recommended: 253 | 2026-07-25T02:44:44+00:00 | Vulnerability · Source |
| CVE-2023-4054 | suse_vex | SUSE CVE CVE-2023-4054 | known affected: 43 recommended: 264 | 2026-07-25T02:44:42+00:00 | Vulnerability · Source |
| CVE-2023-4058 | suse_vex | SUSE CVE CVE-2023-4058 | known affected: 43 recommended: 9 | 2026-07-25T02:44:38+00:00 | Vulnerability · Source |
| CVE-2023-4091 | suse_vex | SUSE CVE CVE-2023-4091 | known affected: 552 recommended: 1360 | 2026-07-25T02:44:35+00:00 | Vulnerability · Source |
| CVE-2023-4385 | suse_vex | SUSE CVE CVE-2023-4385 | known affected: 420 known not affected: 96 recommended: 374 | 2026-07-25T02:44:24+00:00 | Vulnerability · Source |
| CVE-2023-4579 | suse_vex | SUSE CVE CVE-2023-4579 | known affected: 49 recommended: 9 | 2026-07-25T02:44:04+00:00 | Vulnerability · Source |
| CVE-2023-4581 | suse_vex | SUSE CVE CVE-2023-4581 | known affected: 49 recommended: 292 | 2026-07-25T02:44:02+00:00 | Vulnerability · Source |
| CVE-2023-4583 | suse_vex | SUSE CVE CVE-2023-4583 | known affected: 49 recommended: 289 | 2026-07-25T02:44:00+00:00 | Vulnerability · Source |
| CVE-2023-4641 | suse_vex | SUSE CVE CVE-2023-4641 | known affected: 214 recommended: 323 | 2026-07-25T02:43:53+00:00 | Vulnerability · Source |
| CVE-2023-4736 | suse_vex | SUSE CVE CVE-2023-4736 | known not affected: 259 | 2026-07-25T02:43:45+00:00 | Vulnerability · Source |
| CVE-2023-4781 | suse_vex | SUSE CVE CVE-2023-4781 | known affected: 263 recommended: 436 | 2026-07-25T02:43:34+00:00 | Vulnerability · Source |
| CVE-2023-4900 | suse_vex | SUSE CVE CVE-2023-4900 | known affected: 51 known not affected: 1172 recommended: 12 | 2026-07-25T02:43:25+00:00 | Vulnerability · Source |
| CVE-2023-4902 | suse_vex | SUSE CVE CVE-2023-4902 | known affected: 51 known not affected: 1172 recommended: 12 | 2026-07-25T02:43:22+00:00 | Vulnerability · Source |
| CVE-2023-4903 | suse_vex | SUSE CVE CVE-2023-4903 | known affected: 51 known not affected: 1172 recommended: 12 | 2026-07-25T02:43:20+00:00 | Vulnerability · Source |
| CVE-2023-4909 | suse_vex | SUSE CVE CVE-2023-4909 | known affected: 51 known not affected: 1172 recommended: 12 | 2026-07-25T02:43:18+00:00 | Vulnerability · Source |
| CVE-2023-5344 | suse_vex | SUSE CVE CVE-2023-5344 | known affected: 273 known not affected: 1 recommended: 419 | 2026-07-25T02:43:10+00:00 | Vulnerability · Source |
| CVE-2023-5535 | suse_vex | SUSE CVE CVE-2023-5535 | known affected: 274 recommended: 419 | 2026-07-25T02:43:02+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-5723 | suse_vex | SUSE CVE CVE-2023-5723 | known affected: 38 recommended: 174 | 2026-07-25T02:42:53+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-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-6111 | suse_vex | SUSE CVE CVE-2023-6111 | known not affected: 362 | 2026-07-25T02:42:30+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-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-6857 | suse_vex | SUSE CVE CVE-2023-6857 | known affected: 28 recommended: 260 | 2026-07-25T02:41:54+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-7256 | suse_vex | SUSE CVE CVE-2023-7256 | known affected: 360 recommended: 166 | 2026-07-25T02:41:32+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-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-21967 | suse_vex | SUSE CVE CVE-2023-21967 | known affected: 439 recommended: 947 | 2026-07-25T02:40:57+00:00 | Vulnerability · Source |
| CVE-2023-22024 | suse_vex | SUSE CVE CVE-2023-22024 | known not affected: 337 | 2026-07-25T02:40:52+00:00 | Vulnerability · Source |
| CVE-2023-22997 | suse_vex | SUSE CVE CVE-2023-22997 | known not affected: 288 | 2026-07-25T02:40:38+00:00 | Vulnerability · Source |
| CVE-2023-22999 | suse_vex | SUSE CVE CVE-2023-22999 | known not affected: 288 | 2026-07-25T02:40:33+00:00 | Vulnerability · Source |
| CVE-2023-23003 | suse_vex | SUSE CVE CVE-2023-23003 | known not affected: 288 | 2026-07-25T02:40:31+00:00 | Vulnerability · Source |
| CVE-2023-23599 | suse_vex | SUSE CVE CVE-2023-23599 | known affected: 36 recommended: 158 | 2026-07-25T02:40:20+00:00 | Vulnerability · Source |
| CVE-2023-23605 | suse_vex | SUSE CVE CVE-2023-23605 | known affected: 36 recommended: 320 | 2026-07-25T02:40:16+00:00 | Vulnerability · Source |