VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283485 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-4056 | suse_vex | SUSE CVE CVE-2023-4056 | known affected: 43 recommended: 271 | 2026-07-25T02:44:40+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-4130 | suse_vex | SUSE CVE CVE-2023-4130 | known affected: 394 known not affected: 349 recommended: 354 | 2026-07-25T02:44:32+00:00 | Vulnerability · Source |
| CVE-2023-4133 | suse_vex | SUSE CVE CVE-2023-4133 | known affected: 228 known not affected: 42 recommended: 1241 | 2026-07-25T02:44:30+00:00 | Vulnerability · Source |
| CVE-2023-4194 | suse_vex | SUSE CVE CVE-2023-4194 | known affected: 390 known not affected: 42 recommended: 1101 | 2026-07-25T02:44:27+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-4387 | suse_vex | SUSE CVE CVE-2023-4387 | known affected: 210 known not affected: 8 recommended: 1124 | 2026-07-25T02:44:21+00:00 | Vulnerability · Source |
| CVE-2023-4408 | suse_vex | SUSE CVE CVE-2023-4408 | known affected: 442 known not affected: 141 recommended: 565 | 2026-07-25T02:44:20+00:00 | Vulnerability · Source |
| CVE-2023-4513 | suse_vex | SUSE CVE CVE-2023-4513 | known affected: 109 recommended: 186 | 2026-07-25T02:44:17+00:00 | Vulnerability · Source |
| CVE-2023-4515 | suse_vex | SUSE CVE CVE-2023-4515 | known affected: 394 known not affected: 337 recommended: 354 | 2026-07-25T02:44:15+00:00 | Vulnerability · Source |
| CVE-2023-4527 | suse_vex | SUSE CVE CVE-2023-4527 | known not affected: 612 recommended: 645 | 2026-07-25T02:44:12+00:00 | Vulnerability · Source |
| CVE-2023-4563 | suse_vex | SUSE CVE CVE-2023-4563 | known affected: 247 known not affected: 169 recommended: 922 | 2026-07-25T02:44:09+00:00 | Vulnerability · Source |
| CVE-2023-4578 | suse_vex | SUSE CVE CVE-2023-4578 | known affected: 49 recommended: 289 | 2026-07-25T02:44:06+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-4584 | suse_vex | SUSE CVE CVE-2023-4584 | known affected: 49 recommended: 292 | 2026-07-25T02:43:57+00:00 | Vulnerability · Source |
| CVE-2023-4622 | suse_vex | SUSE CVE CVE-2023-4622 | known affected: 215 known not affected: 6 recommended: 1570 | 2026-07-25T02:43:55+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-4733 | suse_vex | SUSE CVE CVE-2023-4733 | known affected: 270 recommended: 436 | 2026-07-25T02:43:50+00:00 | Vulnerability · Source |
| CVE-2023-4734 | suse_vex | SUSE CVE CVE-2023-4734 | known affected: 269 known not affected: 1 recommended: 442 | 2026-07-25T02:43:48+00:00 | Vulnerability · Source |
| CVE-2023-4735 | suse_vex | SUSE CVE CVE-2023-4735 | known affected: 269 known not affected: 1 recommended: 442 | 2026-07-25T02:43:46+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-4738 | suse_vex | SUSE CVE CVE-2023-4738 | known affected: 270 recommended: 442 | 2026-07-25T02:43:42+00:00 | Vulnerability · Source |
| CVE-2023-4750 | suse_vex | SUSE CVE CVE-2023-4750 | known affected: 411 recommended: 345 | 2026-07-25T02:43:40+00:00 | Vulnerability · Source |
| CVE-2023-4751 | suse_vex | SUSE CVE CVE-2023-4751 | known affected: 1 known not affected: 316 recommended: 22 | 2026-07-25T02:43:38+00:00 | Vulnerability · Source |
| CVE-2023-4752 | suse_vex | SUSE CVE CVE-2023-4752 | known affected: 270 recommended: 441 | 2026-07-25T02:43:36+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-4874 | suse_vex | SUSE CVE CVE-2023-4874 | known affected: 464 known not affected: 1 recommended: 103 | 2026-07-25T02:43:31+00:00 | Vulnerability · Source |
| CVE-2023-4875 | suse_vex | SUSE CVE CVE-2023-4875 | known affected: 465 recommended: 103 | 2026-07-25T02:43:29+00:00 | Vulnerability · Source |
| CVE-2023-4881 | suse_vex | SUSE CVE CVE-2023-4881 | known affected: 199 known not affected: 41 recommended: 1363 | 2026-07-25T02:43:27+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-4911 | suse_vex | SUSE CVE CVE-2023-4911 | known not affected: 608 recommended: 645 | 2026-07-25T02:43:16+00:00 | Vulnerability · Source |
| CVE-2023-5158 | suse_vex | SUSE CVE CVE-2023-5158 | known affected: 230 known not affected: 241 recommended: 896 | 2026-07-25T02:43:13+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-5367 | suse_vex | SUSE CVE CVE-2023-5367 | known affected: 415 known not affected: 28 recommended: 219 | 2026-07-25T02:43:08+00:00 | Vulnerability · Source |
| CVE-2023-5371 | suse_vex | SUSE CVE CVE-2023-5371 | known affected: 108 known not affected: 68 recommended: 207 | 2026-07-25T02:43:05+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-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 |