VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294018 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50778 | suse_vex | SUSE CVE CVE-2022-50778 | known not affected: 421 recommended: 47 | 2026-07-23T02:24:38+00:00 | Vulnerability · Source |
| CVE-2022-50837 | suse_vex | SUSE CVE CVE-2022-50837 | known not affected: 453 | 2026-07-23T02:24:34+00:00 | Vulnerability · Source |
| CVE-2023-0950 | suse_vex | SUSE CVE CVE-2023-0950 | known affected: 163 recommended: 1819 | 2026-07-23T02:24:07+00:00 | Vulnerability · Source |
| CVE-2023-1194 | suse_vex | SUSE CVE CVE-2023-1194 | known not affected: 327 | 2026-07-23T02:24:03+00:00 | Vulnerability · Source |
| CVE-2023-1350 | suse_vex | SUSE CVE CVE-2023-1350 | known not affected: 25 recommended: 6 | 2026-07-23T02:23:59+00:00 | Vulnerability · Source |
| CVE-2023-2137 | suse_vex | SUSE CVE CVE-2023-2137 | known affected: 219 known not affected: 2 recommended: 434 | 2026-07-23T02:23:45+00:00 | Vulnerability · Source |
| CVE-2023-2610 | suse_vex | SUSE CVE CVE-2023-2610 | known affected: 205 known not affected: 3 recommended: 470 | 2026-07-23T02:23:32+00:00 | Vulnerability · Source |
| CVE-2023-3108 | suse_vex | SUSE CVE CVE-2023-3108 | known not affected: 361 | 2026-07-23T02:23:23+00:00 | Vulnerability · Source |
| CVE-2023-4015 | suse_vex | SUSE CVE CVE-2023-4015 | known not affected: 271 recommended: 29 | 2026-07-23T02:23:08+00:00 | Vulnerability · Source |
| CVE-2023-4207 | suse_vex | SUSE CVE CVE-2023-4207 | recommended: 62 | 2026-07-23T02:22:57+00:00 | Vulnerability · Source |
| CVE-2023-5680 | suse_vex | SUSE CVE CVE-2023-5680 | known not affected: 416 | 2026-07-23T02:22:33+00:00 | Vulnerability · Source |
| CVE-2023-21264 | suse_vex | SUSE CVE CVE-2023-21264 | known not affected: 361 | 2026-07-23T02:21:54+00:00 | Vulnerability · Source |
| CVE-2023-25180 | suse_vex | SUSE CVE CVE-2023-25180 | recommended: 486 | 2026-07-23T02:21:41+00:00 | Vulnerability · Source |
| CVE-2023-26544 | suse_vex | SUSE CVE CVE-2023-26544 | known not affected: 284 | 2026-07-23T02:21:30+00:00 | Vulnerability · Source |
| CVE-2023-26934 | suse_vex | SUSE CVE CVE-2023-26934 | known not affected: 351 | 2026-07-23T02:21:29+00:00 | Vulnerability · Source |
| CVE-2023-26937 | suse_vex | SUSE CVE CVE-2023-26937 | known not affected: 351 | 2026-07-23T02:21:26+00:00 | Vulnerability · Source |
| CVE-2023-26938 | suse_vex | SUSE CVE CVE-2023-26938 | known not affected: 350 | 2026-07-23T02:21:25+00:00 | Vulnerability · Source |
| CVE-2023-29455 | suse_vex | SUSE CVE CVE-2023-29455 | known not affected: 21 | 2026-07-23T02:21:09+00:00 | Vulnerability · Source |
| CVE-2023-29457 | suse_vex | SUSE CVE CVE-2023-29457 | known not affected: 21 | 2026-07-23T02:21:08+00:00 | Vulnerability · Source |
| CVE-2023-31484 | suse_vex | SUSE CVE CVE-2023-31484 | known affected: 200 recommended: 481 | 2026-07-23T02:20:50+00:00 | Vulnerability · Source |
| CVE-2023-32190 | suse_vex | SUSE CVE CVE-2023-32190 | known not affected: 89 recommended: 2 | 2026-07-23T02:20:48+00:00 | Vulnerability · Source |
| CVE-2023-32251 | suse_vex | SUSE CVE CVE-2023-32251 | known not affected: 416 | 2026-07-23T02:20:44+00:00 | Vulnerability · Source |
| CVE-2023-32721 | suse_vex | SUSE CVE CVE-2023-32721 | known not affected: 17 | 2026-07-23T02:20:36+00:00 | Vulnerability · Source |
| CVE-2023-32724 | suse_vex | SUSE CVE CVE-2023-32724 | known not affected: 17 | 2026-07-23T02:20:35+00:00 | Vulnerability · Source |
| CVE-2023-34255 | suse_vex | SUSE CVE CVE-2023-34255 | known not affected: 389 | 2026-07-23T02:20:28+00:00 | Vulnerability · Source |
| CVE-2023-34325 | suse_vex | SUSE CVE CVE-2023-34325 | known affected: 250 recommended: 459 | 2026-07-23T02:20:26+00:00 | Vulnerability · Source |
| CVE-2023-38409 | suse_vex | SUSE CVE CVE-2023-38409 | known affected: 260 known not affected: 322 recommended: 566 | 2026-07-23T02:20:14+00:00 | Vulnerability · Source |
| CVE-2023-39978 | suse_vex | SUSE CVE CVE-2023-39978 | known not affected: 388 | 2026-07-23T02:20:01+00:00 | Vulnerability · Source |
| CVE-2023-42670 | suse_vex | SUSE CVE CVE-2023-42670 | known affected: 270 known not affected: 1641 recommended: 535 | 2026-07-23T02:19:54+00:00 | Vulnerability · Source |
| CVE-2023-45931 | suse_vex | SUSE CVE CVE-2023-45931 | known not affected: 1161 | 2026-07-23T02:19:42+00:00 | Vulnerability · Source |
| CVE-2023-47100 | suse_vex | SUSE CVE CVE-2023-47100 | known not affected: 258 | 2026-07-23T02:19:34+00:00 | Vulnerability · Source |
| CVE-2023-47466 | suse_vex | SUSE CVE CVE-2023-47466 | known affected: 146 recommended: 30 | 2026-07-23T02:19:31+00:00 | Vulnerability · Source |
| CVE-2023-50495 | suse_vex | SUSE CVE CVE-2023-50495 | known affected: 583 recommended: 578 | 2026-07-23T02:19:23+00:00 | Vulnerability · Source |
| CVE-2023-52459 | suse_vex | SUSE CVE CVE-2023-52459 | known not affected: 312 recommended: 65 | 2026-07-23T02:19:06+00:00 | Vulnerability · Source |
| CVE-2023-52630 | suse_vex | SUSE CVE CVE-2023-52630 | known affected: 7 known not affected: 173 | 2026-07-23T02:18:32+00:00 | Vulnerability · Source |
| CVE-2023-52906 | suse_vex | SUSE CVE CVE-2023-52906 | known affected: 465 known not affected: 169 recommended: 288 | 2026-07-23T02:17:27+00:00 | Vulnerability · Source |
| CVE-2023-53178 | suse_vex | SUSE CVE CVE-2023-53178 | known affected: 417 known not affected: 187 recommended: 355 | 2026-07-23T02:15:53+00:00 | Vulnerability · Source |
| CVE-2023-53299 | suse_vex | SUSE CVE CVE-2023-53299 | known affected: 462 known not affected: 187 recommended: 292 | 2026-07-23T02:15:25+00:00 | Vulnerability · Source |
| CVE-2023-53308 | suse_vex | SUSE CVE CVE-2023-53308 | known affected: 500 known not affected: 280 recommended: 23 | 2026-07-23T02:15:22+00:00 | Vulnerability · Source |
| CVE-2023-53459 | suse_vex | SUSE CVE CVE-2023-53459 | known not affected: 416 | 2026-07-23T02:15:00+00:00 | Vulnerability · Source |
| CVE-2023-53463 | suse_vex | SUSE CVE CVE-2023-53463 | known affected: 395 known not affected: 108 recommended: 552 | 2026-07-23T02:14:58+00:00 | Vulnerability · Source |
| CVE-2023-53581 | suse_vex | SUSE CVE CVE-2023-53581 | known affected: 480 known not affected: 108 recommended: 483 | 2026-07-23T02:14:26+00:00 | Vulnerability · Source |
| CVE-2023-53727 | suse_vex | SUSE CVE CVE-2023-53727 | known affected: 543 known not affected: 113 recommended: 346 | 2026-07-23T02:13:49+00:00 | Vulnerability · Source |
| CVE-2023-53801 | suse_vex | SUSE CVE CVE-2023-53801 | known affected: 429 known not affected: 296 recommended: 87 | 2026-07-23T02:13:38+00:00 | Vulnerability · Source |
| CVE-2023-54047 | suse_vex | SUSE CVE CVE-2023-54047 | known affected: 531 known not affected: 209 recommended: 110 | 2026-07-23T02:13:15+00:00 | Vulnerability · Source |
| CVE-2023-54063 | suse_vex | SUSE CVE CVE-2023-54063 | known not affected: 453 | 2026-07-23T02:13:13+00:00 | Vulnerability · Source |
| CVE-2023-54190 | suse_vex | SUSE CVE CVE-2023-54190 | known affected: 354 known not affected: 309 recommended: 196 | 2026-07-23T02:12:48+00:00 | Vulnerability · Source |
| CVE-2023-54198 | suse_vex | SUSE CVE CVE-2023-54198 | known affected: 476 known not affected: 187 recommended: 233 | 2026-07-23T02:12:47+00:00 | Vulnerability · Source |
| CVE-2023-54305 | suse_vex | SUSE CVE CVE-2023-54305 | known affected: 409 known not affected: 286 recommended: 196 | 2026-07-23T02:12:23+00:00 | Vulnerability · Source |
| CVE-2023-54310 | suse_vex | SUSE CVE CVE-2023-54310 | known affected: 234 known not affected: 187 | 2026-07-23T02:12:20+00:00 | Vulnerability · Source |