VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286739 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-3301 | suse_vex | SUSE CVE CVE-2023-3301 | known affected: 394 known not affected: 454 recommended: 1488 | 2026-07-28T23:49:21+00:00 | Vulnerability · Source |
| CVE-2023-3576 | suse_vex | SUSE CVE CVE-2023-3576 | known affected: 515 recommended: 102 | 2026-07-28T23:49:19+00:00 | Vulnerability · Source |
| CVE-2023-3648 | suse_vex | SUSE CVE CVE-2023-3648 | known affected: 1 known not affected: 91 recommended: 192 | 2026-07-28T23:49:18+00:00 | Vulnerability · Source |
| CVE-2023-3772 | suse_vex | SUSE CVE CVE-2023-3772 | known affected: 206 recommended: 1717 | 2026-07-28T23:49:16+00:00 | Vulnerability · Source |
| CVE-2023-4244 | suse_vex | SUSE CVE CVE-2023-4244 | known affected: 320 known not affected: 70 recommended: 1196 | 2026-07-28T23:49:14+00:00 | Vulnerability · Source |
| CVE-2023-4255 | suse_vex | SUSE CVE CVE-2023-4255 | known affected: 406 known not affected: 38 recommended: 5 | 2026-07-28T23:49:13+00:00 | Vulnerability · Source |
| CVE-2023-4575 | suse_vex | SUSE CVE CVE-2023-4575 | known affected: 49 recommended: 292 | 2026-07-28T23:49:11+00:00 | Vulnerability · Source |
| CVE-2023-4732 | suse_vex | SUSE CVE CVE-2023-4732 | known not affected: 363 recommended: 20 | 2026-07-28T23:49:09+00:00 | Vulnerability · Source |
| CVE-2023-5717 | suse_vex | SUSE CVE CVE-2023-5717 | known affected: 260 known not affected: 6 recommended: 1395 | 2026-07-28T23:49:07+00:00 | Vulnerability · Source |
| CVE-2023-6208 | suse_vex | SUSE CVE CVE-2023-6208 | known affected: 38 recommended: 278 | 2026-07-28T23:49:05+00:00 | Vulnerability · Source |
| CVE-2023-6349 | suse_vex | SUSE CVE CVE-2023-6349 | known affected: 110 known not affected: 7 recommended: 96 | 2026-07-28T23:49:04+00:00 | Vulnerability · Source |
| CVE-2023-22025 | suse_vex | SUSE CVE CVE-2023-22025 | known affected: 394 known not affected: 417 recommended: 467 | 2026-07-28T23:49:01+00:00 | Vulnerability · Source |
| CVE-2023-23002 | suse_vex | SUSE CVE CVE-2023-23002 | known not affected: 288 | 2026-07-28T23:48:59+00:00 | Vulnerability · Source |
| CVE-2023-23517 | suse_vex | SUSE CVE CVE-2023-23517 | known affected: 1 recommended: 794 | 2026-07-28T23:48:58+00:00 | Vulnerability · Source |
| CVE-2023-25139 | suse_vex | SUSE CVE CVE-2023-25139 | known not affected: 449 recommended: 216 | 2026-07-28T23:48:55+00:00 | Vulnerability · Source |
| CVE-2023-25434 | suse_vex | SUSE CVE CVE-2023-25434 | known not affected: 191 | 2026-07-28T23:48:54+00:00 | Vulnerability · Source |
| CVE-2023-25743 | suse_vex | SUSE CVE CVE-2023-25743 | known affected: 1 recommended: 245 | 2026-07-28T23:48:52+00:00 | Vulnerability · Source |
| CVE-2023-26463 | suse_vex | SUSE CVE CVE-2023-26463 | known not affected: 202 recommended: 22 | 2026-07-28T23:48:51+00:00 | Vulnerability · Source |
| CVE-2023-26464 | suse_vex | SUSE CVE CVE-2023-26464 | known not affected: 225 | 2026-07-28T23:48:49+00:00 | Vulnerability · Source |
| CVE-2023-27478 | suse_vex | SUSE CVE CVE-2023-27478 | known not affected: 171 | 2026-07-28T23:48:48+00:00 | Vulnerability · Source |
| CVE-2023-28319 | suse_vex | SUSE CVE CVE-2023-28319 | known affected: 280 known not affected: 169 recommended: 266 | 2026-07-28T23:48:46+00:00 | Vulnerability · Source |
| CVE-2023-29935 | suse_vex | SUSE CVE CVE-2023-29935 | known not affected: 1268 | 2026-07-28T23:48:43+00:00 | Vulnerability · Source |
| CVE-2023-34416 | suse_vex | SUSE CVE CVE-2023-34416 | known affected: 16 known not affected: 3 recommended: 306 | 2026-07-28T23:48:41+00:00 | Vulnerability · Source |
| CVE-2023-38429 | suse_vex | SUSE CVE CVE-2023-38429 | known not affected: 361 | 2026-07-28T23:48:39+00:00 | Vulnerability · Source |
| CVE-2023-39191 | suse_vex | SUSE CVE CVE-2023-39191 | known affected: 275 known not affected: 282 recommended: 417 | 2026-07-28T23:48:37+00:00 | Vulnerability · Source |
| CVE-2023-42752 | suse_vex | SUSE CVE CVE-2023-42752 | known affected: 394 known not affected: 388 recommended: 364 | 2026-07-28T23:48:35+00:00 | Vulnerability · Source |
| CVE-2023-42843 | suse_vex | SUSE CVE CVE-2023-42843 | known affected: 63 recommended: 816 | 2026-07-28T23:48:33+00:00 | Vulnerability · Source |
| CVE-2023-42875 | suse_vex | SUSE CVE CVE-2023-42875 | known not affected: 140 recommended: 592 | 2026-07-28T23:48:32+00:00 | Vulnerability · Source |
| CVE-2023-46218 | suse_vex | SUSE CVE CVE-2023-46218 | known affected: 299 known not affected: 38 recommended: 362 | 2026-07-28T23:48:29+00:00 | Vulnerability · Source |
| CVE-2023-46813 | suse_vex | SUSE CVE CVE-2023-46813 | known affected: 215 known not affected: 267 recommended: 828 | 2026-07-28T23:48:27+00:00 | Vulnerability · Source |
| CVE-2023-51767 | suse_vex | SUSE CVE CVE-2023-51767 | known affected: 84 | 2026-07-28T23:48:25+00:00 | Vulnerability · Source |
| CVE-2023-52451 | suse_vex | SUSE CVE CVE-2023-52451 | known affected: 339 known not affected: 66 recommended: 953 | 2026-07-28T23:48:23+00:00 | Vulnerability · Source |
| CVE-2023-52524 | suse_vex | SUSE CVE CVE-2023-52524 | known affected: 362 known not affected: 78 recommended: 904 | 2026-07-28T23:48:20+00:00 | Vulnerability · Source |
| CVE-2023-52680 | suse_vex | SUSE CVE CVE-2023-52680 | known affected: 446 known not affected: 111 recommended: 671 | 2026-07-28T23:48:13+00:00 | Vulnerability · Source |
| CVE-2023-52689 | suse_vex | SUSE CVE CVE-2023-52689 | known not affected: 330 recommended: 59 | 2026-07-28T23:48:11+00:00 | Vulnerability · Source |
| CVE-2023-52804 | suse_vex | SUSE CVE CVE-2023-52804 | known affected: 282 known not affected: 376 recommended: 810 | 2026-07-28T23:48:07+00:00 | Vulnerability · Source |
| CVE-2023-52851 | suse_vex | SUSE CVE CVE-2023-52851 | known affected: 315 known not affected: 235 recommended: 671 | 2026-07-28T23:48:05+00:00 | Vulnerability · Source |
| CVE-2023-52895 | suse_vex | SUSE CVE CVE-2023-52895 | known not affected: 311 | 2026-07-28T23:48:03+00:00 | Vulnerability · Source |
| CVE-2023-52897 | suse_vex | SUSE CVE CVE-2023-52897 | known not affected: 310 | 2026-07-28T23:48:01+00:00 | Vulnerability · Source |
| CVE-2023-52905 | suse_vex | SUSE CVE CVE-2023-52905 | known affected: 310 known not affected: 195 recommended: 438 | 2026-07-28T23:48:00+00:00 | Vulnerability · Source |
| CVE-2023-53003 | suse_vex | SUSE CVE CVE-2023-53003 | known affected: 106 known not affected: 238 | 2026-07-28T23:47:58+00:00 | Vulnerability · Source |
| CVE-2023-53039 | suse_vex | SUSE CVE CVE-2023-53039 | known affected: 377 known not affected: 200 recommended: 365 | 2026-07-28T23:47:56+00:00 | Vulnerability · Source |
| CVE-2023-53124 | suse_vex | SUSE CVE CVE-2023-53124 | known affected: 376 known not affected: 230 recommended: 300 | 2026-07-28T23:47:54+00:00 | Vulnerability · Source |
| CVE-2023-53236 | suse_vex | SUSE CVE CVE-2023-53236 | known not affected: 416 | 2026-07-28T23:47:52+00:00 | Vulnerability · Source |
| CVE-2023-53241 | suse_vex | SUSE CVE CVE-2023-53241 | known affected: 395 known not affected: 253 recommended: 255 | 2026-07-28T23:47:50+00:00 | Vulnerability · Source |
| CVE-2023-53294 | suse_vex | SUSE CVE CVE-2023-53294 | known not affected: 416 | 2026-07-28T23:47:48+00:00 | Vulnerability · Source |
| CVE-2023-53407 | suse_vex | SUSE CVE CVE-2023-53407 | known affected: 354 known not affected: 306 recommended: 196 | 2026-07-28T23:47:46+00:00 | Vulnerability · Source |
| CVE-2023-53716 | suse_vex | SUSE CVE CVE-2023-53716 | known affected: 374 known not affected: 350 recommended: 116 | 2026-07-28T23:47:42+00:00 | Vulnerability · Source |
| CVE-2023-53720 | suse_vex | SUSE CVE CVE-2023-53720 | known not affected: 407 | 2026-07-28T23:47:40+00:00 | Vulnerability · Source |
| CVE-2023-53760 | suse_vex | SUSE CVE CVE-2023-53760 | known not affected: 408 recommended: 29 | 2026-07-28T23:47:38+00:00 | Vulnerability · Source |