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-31084 | suse_vex | SUSE CVE CVE-2023-31084 | known affected: 224 known not affected: 67 recommended: 1278 | 2026-10-11T01:16:14+00:00 | Vulnerability · Source |
| CVE-2023-31147 | suse_vex | SUSE CVE CVE-2023-31147 | known affected: 295 recommended: 496 | 2026-10-11T01:16:10+00:00 | Vulnerability · Source |
| CVE-2023-31248 | suse_vex | SUSE CVE CVE-2023-31248 | known affected: 174 known not affected: 249 recommended: 1568 | 2026-10-11T01:16:07+00:00 | Vulnerability · Source |
| CVE-2023-31315 | suse_vex | SUSE CVE CVE-2023-31315 | known affected: 26 known not affected: 36 recommended: 1292 | 2026-10-11T01:16:05+00:00 | Vulnerability · Source |
| CVE-2023-31346 | suse_vex | SUSE CVE CVE-2023-31346 | known affected: 2 recommended: 55 | 2026-10-11T01:16:03+00:00 | Vulnerability · Source |
| CVE-2023-31486 | suse_vex | SUSE CVE CVE-2023-31486 | recommended: 8 | 2026-10-11T01:16:02+00:00 | Vulnerability · Source |
| CVE-2023-32067 | suse_vex | SUSE CVE CVE-2023-32067 | known affected: 295 recommended: 502 | 2026-10-11T01:16:00+00:00 | Vulnerability · Source |
| CVE-2023-32207 | suse_vex | SUSE CVE CVE-2023-32207 | known affected: 78 recommended: 307 | 2026-10-11T01:15:58+00:00 | Vulnerability · Source |
| CVE-2023-32393 | suse_vex | SUSE CVE CVE-2023-32393 | recommended: 739 | 2026-10-11T01:15:56+00:00 | Vulnerability · Source |
| CVE-2023-32435 | suse_vex | SUSE CVE CVE-2023-32435 | known affected: 138 recommended: 747 | 2026-10-11T01:15:54+00:00 | Vulnerability · Source |
| CVE-2023-32439 | suse_vex | SUSE CVE CVE-2023-32439 | known affected: 138 recommended: 747 | 2026-10-11T01:15:53+00:00 | Vulnerability · Source |
| CVE-2023-32573 | suse_vex | SUSE CVE CVE-2023-32573 | known affected: 400 recommended: 494 | 2026-10-11T01:15:51+00:00 | Vulnerability · Source |
| CVE-2023-32636 | suse_vex | SUSE CVE CVE-2023-32636 | known not affected: 626 recommended: 68 | 2026-10-11T01:15:49+00:00 | Vulnerability · Source |
| CVE-2023-32681 | suse_vex | SUSE CVE CVE-2023-32681 | known affected: 332 known not affected: 2 recommended: 405 | 2026-10-11T01:15:47+00:00 | Vulnerability · Source |
| CVE-2023-32762 | suse_vex | SUSE CVE CVE-2023-32762 | known affected: 394 known not affected: 780 recommended: 2279 | 2026-10-11T01:15:44+00:00 | Vulnerability · Source |
| CVE-2023-32763 | suse_vex | SUSE CVE CVE-2023-32763 | known affected: 530 known not affected: 2 recommended: 2717 | 2026-10-11T01:15:42+00:00 | Vulnerability · Source |
| CVE-2023-33170 | suse_vex | SUSE CVE CVE-2023-33170 | recommended: 61 | 2026-10-11T01:15:39+00:00 | Vulnerability · Source |
| CVE-2023-33204 | suse_vex | SUSE CVE CVE-2023-33204 | known affected: 520 known not affected: 1 recommended: 40 | 2026-10-11T01:15:37+00:00 | Vulnerability · Source |
| CVE-2023-33285 | suse_vex | SUSE CVE CVE-2023-33285 | known affected: 466 known not affected: 210 recommended: 2683 | 2026-10-11T01:15:34+00:00 | Vulnerability · Source |
| CVE-2023-33951 | suse_vex | SUSE CVE CVE-2023-33951 | known affected: 283 known not affected: 431 recommended: 595 | 2026-10-11T01:15:32+00:00 | Vulnerability · Source |
| CVE-2023-34059 | suse_vex | SUSE CVE CVE-2023-34059 | recommended: 333 | 2026-10-11T01:15:30+00:00 | Vulnerability · Source |
| CVE-2023-34151 | suse_vex | SUSE CVE CVE-2023-34151 | known not affected: 221 recommended: 420 | 2026-10-11T01:15:28+00:00 | Vulnerability · Source |
| CVE-2023-34241 | suse_vex | SUSE CVE CVE-2023-34241 | known affected: 347 known not affected: 18 recommended: 691 | 2026-10-11T01:15:26+00:00 | Vulnerability · Source |
| CVE-2023-34319 | suse_vex | SUSE CVE CVE-2023-34319 | known affected: 254 known not affected: 328 recommended: 1284 | 2026-10-11T01:15:25+00:00 | Vulnerability · Source |
| CVE-2023-34966 | suse_vex | SUSE CVE CVE-2023-34966 | known affected: 174 known not affected: 1574 recommended: 1296 | 2026-10-11T01:15:20+00:00 | Vulnerability · Source |
| CVE-2023-34967 | suse_vex | SUSE CVE CVE-2023-34967 | known affected: 434 known not affected: 1314 recommended: 1296 | 2026-10-11T01:15:18+00:00 | Vulnerability · Source |
| CVE-2023-34969 | suse_vex | SUSE CVE CVE-2023-34969 | known affected: 298 known not affected: 1 recommended: 446 | 2026-10-11T01:15:16+00:00 | Vulnerability · Source |
| CVE-2023-35001 | suse_vex | SUSE CVE CVE-2023-35001 | known affected: 174 known not affected: 6 recommended: 1607 | 2026-10-11T01:15:14+00:00 | Vulnerability · Source |
| CVE-2023-35788 | suse_vex | SUSE CVE CVE-2023-35788 | known affected: 197 known not affected: 191 recommended: 1282 | 2026-10-11T01:15:12+00:00 | Vulnerability · Source |
| CVE-2023-35945 | suse_vex | SUSE CVE CVE-2023-35945 | known affected: 256 recommended: 436 | 2026-10-11T01:15:10+00:00 | Vulnerability · Source |
| CVE-2023-35946 | suse_vex | SUSE CVE CVE-2023-35946 | known affected: 16 recommended: 16 | 2026-10-11T01:15:09+00:00 | Vulnerability · Source |
| CVE-2023-36617 | suse_vex | SUSE CVE CVE-2023-36617 | known not affected: 349 recommended: 93 | 2026-10-11T01:15:07+00:00 | Vulnerability · Source |
| CVE-2023-36660 | suse_vex | SUSE CVE CVE-2023-36660 | known not affected: 348 recommended: 71 | 2026-10-11T01:15:05+00:00 | Vulnerability · Source |
| CVE-2023-37207 | suse_vex | SUSE CVE CVE-2023-37207 | recommended: 280 | 2026-10-11T01:15:03+00:00 | Vulnerability · Source |
| CVE-2023-37208 | suse_vex | SUSE CVE CVE-2023-37208 | recommended: 280 | 2026-10-11T01:15:01+00:00 | Vulnerability · Source |
| CVE-2023-37210 | suse_vex | SUSE CVE CVE-2023-37210 | recommended: 264 | 2026-10-11T01:14:59+00:00 | Vulnerability · Source |
| CVE-2023-37212 | suse_vex | SUSE CVE CVE-2023-37212 | recommended: 264 | 2026-10-11T01:14:57+00:00 | Vulnerability · Source |
| CVE-2023-37328 | suse_vex | SUSE CVE CVE-2023-37328 | known not affected: 1871 recommended: 1489 | 2026-10-11T01:14:54+00:00 | Vulnerability · Source |
| CVE-2023-37369 | suse_vex | SUSE CVE CVE-2023-37369 | known affected: 1235 known not affected: 550 recommended: 2214 | 2026-10-11T01:14:51+00:00 | Vulnerability · Source |
| CVE-2023-37920 | suse_vex | SUSE CVE CVE-2023-37920 | known not affected: 162 recommended: 154 | 2026-10-11T01:14:45+00:00 | Vulnerability · Source |
| CVE-2023-38133 | suse_vex | SUSE CVE CVE-2023-38133 | known affected: 147 known not affected: 143 recommended: 747 | 2026-10-11T01:14:43+00:00 | Vulnerability · Source |
| CVE-2023-38180 | suse_vex | SUSE CVE CVE-2023-38180 | recommended: 61 | 2026-10-11T01:14:41+00:00 | Vulnerability · Source |
| CVE-2023-38253 | suse_vex | SUSE CVE CVE-2023-38253 | known not affected: 46 recommended: 34 | 2026-10-11T01:14:39+00:00 | Vulnerability · Source |
| CVE-2023-38409 | suse_vex | SUSE CVE CVE-2023-38409 | known affected: 260 known not affected: 367 recommended: 566 | 2026-10-11T01:14:37+00:00 | Vulnerability · Source |
| CVE-2023-38417 | suse_vex | SUSE CVE CVE-2023-38417 | known not affected: 101 recommended: 845 | 2026-10-11T01:14:35+00:00 | Vulnerability · Source |
| CVE-2023-38545 | suse_vex | SUSE CVE CVE-2023-38545 | known affected: 206 known not affected: 143 recommended: 382 | 2026-10-11T01:14:33+00:00 | Vulnerability · Source |
| CVE-2023-38552 | suse_vex | SUSE CVE CVE-2023-38552 | known not affected: 314 recommended: 414 | 2026-10-11T01:14:32+00:00 | Vulnerability · Source |
| CVE-2023-38559 | suse_vex | SUSE CVE CVE-2023-38559 | known affected: 107 recommended: 136 | 2026-10-11T01:14:30+00:00 | Vulnerability · Source |
| CVE-2023-38600 | suse_vex | SUSE CVE CVE-2023-38600 | known affected: 147 known not affected: 143 recommended: 747 | 2026-10-11T01:14:27+00:00 | Vulnerability · Source |
| CVE-2023-39189 | suse_vex | SUSE CVE CVE-2023-39189 | known affected: 269 recommended: 1359 | 2026-10-11T01:14:22+00:00 | Vulnerability · Source |