VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-45468 | suse_vex | SUSE CVE CVE-2023-45468 | recommended: 18 | 2026-07-25T17:01:17+00:00 | Vulnerability · Source |
| CVE-2023-45896 | suse_vex | SUSE CVE CVE-2023-45896 | known not affected: 518 | 2026-07-25T17:01:14+00:00 | Vulnerability · Source |
| CVE-2023-45918 | suse_vex | SUSE CVE CVE-2023-45918 | known affected: 616 known not affected: 92 recommended: 425 | 2026-07-25T17:01:13+00:00 | Vulnerability · Source |
| CVE-2023-46839 | suse_vex | SUSE CVE CVE-2023-46839 | known affected: 361 recommended: 390 | 2026-07-25T17:01:07+00:00 | Vulnerability · Source |
| CVE-2023-47248 | suse_vex | SUSE CVE CVE-2023-47248 | known not affected: 51 recommended: 111 | 2026-07-25T17:01:05+00:00 | Vulnerability · Source |
| CVE-2023-52444 | suse_vex | SUSE CVE CVE-2023-52444 | known not affected: 312 | 2026-07-25T17:00:56+00:00 | Vulnerability · Source |
| CVE-2023-52468 | suse_vex | SUSE CVE CVE-2023-52468 | known not affected: 312 recommended: 206 | 2026-07-25T17:00:50+00:00 | Vulnerability · Source |
| CVE-2023-52516 | suse_vex | SUSE CVE CVE-2023-52516 | known not affected: 292 | 2026-07-25T17:00:41+00:00 | Vulnerability · Source |
| CVE-2023-52521 | suse_vex | SUSE CVE CVE-2023-52521 | known not affected: 292 | 2026-07-25T17:00:38+00:00 | Vulnerability · Source |
| CVE-2023-52609 | suse_vex | SUSE CVE CVE-2023-52609 | known not affected: 292 | 2026-07-25T17:00:34+00:00 | Vulnerability · Source |
| CVE-2023-52762 | suse_vex | SUSE CVE CVE-2023-52762 | known affected: 417 known not affected: 80 recommended: 874 | 2026-07-25T17:00:03+00:00 | Vulnerability · Source |
| CVE-2023-52795 | suse_vex | SUSE CVE CVE-2023-52795 | known affected: 315 known not affected: 235 recommended: 671 | 2026-07-25T17:00:01+00:00 | Vulnerability · Source |
| CVE-2023-52812 | suse_vex | SUSE CVE CVE-2023-52812 | known affected: 330 known not affected: 237 recommended: 656 | 2026-07-25T16:59:58+00:00 | Vulnerability · Source |
| CVE-2023-52843 | suse_vex | SUSE CVE CVE-2023-52843 | known affected: 569 recommended: 740 | 2026-07-25T16:59:56+00:00 | Vulnerability · Source |
| CVE-2023-52903 | suse_vex | SUSE CVE CVE-2023-52903 | known affected: 66 known not affected: 120 | 2026-07-25T16:59:52+00:00 | Vulnerability · Source |
| CVE-2023-52910 | suse_vex | SUSE CVE CVE-2023-52910 | known affected: 340 known not affected: 195 recommended: 288 | 2026-07-25T16:59:51+00:00 | Vulnerability · Source |
| CVE-2023-52996 | suse_vex | SUSE CVE CVE-2023-52996 | known affected: 106 known not affected: 238 | 2026-07-25T16:59:46+00:00 | Vulnerability · Source |
| CVE-2023-53027 | suse_vex | SUSE CVE CVE-2023-53027 | known not affected: 348 | 2026-07-25T16:59:44+00:00 | Vulnerability · Source |
| CVE-2023-53036 | suse_vex | SUSE CVE CVE-2023-53036 | known affected: 369 known not affected: 343 recommended: 141 | 2026-07-25T16:59:43+00:00 | Vulnerability · Source |
| CVE-2023-53050 | suse_vex | SUSE CVE CVE-2023-53050 | known not affected: 397 recommended: 49 | 2026-07-25T16:59:41+00:00 | Vulnerability · Source |
| CVE-2023-53110 | suse_vex | SUSE CVE CVE-2023-53110 | known affected: 106 known not affected: 291 recommended: 49 | 2026-07-25T16:59:36+00:00 | Vulnerability · Source |
| CVE-2023-53144 | suse_vex | SUSE CVE CVE-2023-53144 | known not affected: 397 | 2026-07-25T16:59:33+00:00 | Vulnerability · Source |
| CVE-2023-53168 | suse_vex | SUSE CVE CVE-2023-53168 | known affected: 369 known not affected: 359 recommended: 121 | 2026-07-25T16:59:31+00:00 | Vulnerability · Source |
| CVE-2023-53259 | suse_vex | SUSE CVE CVE-2023-53259 | known affected: 494 known not affected: 195 recommended: 206 | 2026-07-25T16:59:29+00:00 | Vulnerability · Source |
| CVE-2023-53310 | suse_vex | SUSE CVE CVE-2023-53310 | known not affected: 416 | 2026-07-25T16:59:27+00:00 | Vulnerability · Source |
| CVE-2023-53318 | suse_vex | SUSE CVE CVE-2023-53318 | known affected: 224 known not affected: 160 | 2026-07-25T16:59:25+00:00 | Vulnerability · Source |
| CVE-2023-53346 | suse_vex | SUSE CVE CVE-2023-53346 | known affected: 163 known not affected: 253 | 2026-07-25T16:59:24+00:00 | Vulnerability · Source |
| CVE-2023-53347 | suse_vex | SUSE CVE CVE-2023-53347 | known affected: 475 known not affected: 253 recommended: 92 | 2026-07-25T16:59:23+00:00 | Vulnerability · Source |
| CVE-2023-53349 | suse_vex | SUSE CVE CVE-2023-53349 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-25T16:59:21+00:00 | Vulnerability · Source |
| CVE-2023-53358 | suse_vex | SUSE CVE CVE-2023-53358 | known not affected: 416 | 2026-07-25T16:59:20+00:00 | Vulnerability · Source |
| CVE-2023-53389 | suse_vex | SUSE CVE CVE-2023-53389 | known not affected: 416 | 2026-07-25T16:59:18+00:00 | Vulnerability · Source |
| CVE-2023-53396 | suse_vex | SUSE CVE CVE-2023-53396 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-25T16:59:16+00:00 | Vulnerability · Source |
| CVE-2023-53400 | suse_vex | SUSE CVE CVE-2023-53400 | known affected: 462 known not affected: 187 recommended: 292 | 2026-07-25T16:59:15+00:00 | Vulnerability · Source |
| CVE-2023-53410 | suse_vex | SUSE CVE CVE-2023-53410 | known affected: 57 known not affected: 359 recommended: 49 | 2026-07-25T16:59:14+00:00 | Vulnerability · Source |
| CVE-2023-53411 | suse_vex | SUSE CVE CVE-2023-53411 | known affected: 112 known not affected: 304 | 2026-07-25T16:59:12+00:00 | Vulnerability · Source |
| CVE-2023-53413 | suse_vex | SUSE CVE CVE-2023-53413 | known affected: 462 known not affected: 186 recommended: 206 | 2026-07-25T16:59:11+00:00 | Vulnerability · Source |
| CVE-2023-53416 | suse_vex | SUSE CVE CVE-2023-53416 | known affected: 456 known not affected: 160 recommended: 206 | 2026-07-25T16:59:09+00:00 | Vulnerability · Source |
| CVE-2023-53435 | suse_vex | SUSE CVE CVE-2023-53435 | known affected: 462 known not affected: 154 recommended: 206 | 2026-07-25T16:59:08+00:00 | Vulnerability · Source |
| CVE-2023-53450 | suse_vex | SUSE CVE CVE-2023-53450 | known affected: 230 known not affected: 154 | 2026-07-25T16:59:07+00:00 | Vulnerability · Source |
| CVE-2023-53455 | suse_vex | SUSE CVE CVE-2023-53455 | known not affected: 416 | 2026-07-25T16:59:05+00:00 | Vulnerability · Source |
| CVE-2023-53477 | suse_vex | SUSE CVE CVE-2023-53477 | known affected: 547 known not affected: 233 recommended: 52 | 2026-07-25T16:59:04+00:00 | Vulnerability · Source |
| CVE-2023-53506 | suse_vex | SUSE CVE CVE-2023-53506 | known affected: 468 known not affected: 181 recommended: 243 | 2026-07-25T16:59:02+00:00 | Vulnerability · Source |
| CVE-2023-53509 | suse_vex | SUSE CVE CVE-2023-53509 | known affected: 472 known not affected: 174 recommended: 206 | 2026-07-25T16:59:01+00:00 | Vulnerability · Source |
| CVE-2023-53521 | suse_vex | SUSE CVE CVE-2023-53521 | known affected: 468 known not affected: 181 recommended: 292 | 2026-07-25T16:58:59+00:00 | Vulnerability · Source |
| CVE-2023-53529 | suse_vex | SUSE CVE CVE-2023-53529 | known affected: 163 known not affected: 253 | 2026-07-25T16:58:58+00:00 | Vulnerability · Source |
| CVE-2023-53534 | suse_vex | SUSE CVE CVE-2023-53534 | known affected: 391 known not affected: 267 recommended: 196 | 2026-07-25T16:58:56+00:00 | Vulnerability · Source |
| CVE-2023-53567 | suse_vex | SUSE CVE CVE-2023-53567 | known affected: 354 known not affected: 304 recommended: 196 | 2026-07-25T16:58:54+00:00 | Vulnerability · Source |
| CVE-2023-53594 | suse_vex | SUSE CVE CVE-2023-53594 | known affected: 472 known not affected: 187 recommended: 282 | 2026-07-25T16:58:52+00:00 | Vulnerability · Source |
| CVE-2023-53605 | suse_vex | SUSE CVE CVE-2023-53605 | known affected: 452 known not affected: 206 recommended: 245 | 2026-07-25T16:58:51+00:00 | Vulnerability · Source |
| CVE-2023-53607 | suse_vex | SUSE CVE CVE-2023-53607 | known affected: 354 known not affected: 304 recommended: 245 | 2026-07-25T16:58:49+00:00 | Vulnerability · Source |