VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292116 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53714 | suse_vex | SUSE CVE CVE-2023-53714 | known affected: 374 known not affected: 260 recommended: 317 | 2026-07-23T02:13:55+00:00 | Vulnerability · Source |
| CVE-2023-53719 | suse_vex | SUSE CVE CVE-2023-53719 | known affected: 415 known not affected: 234 recommended: 196 | 2026-07-23T02:13:53+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-53742 | suse_vex | SUSE CVE CVE-2023-53742 | known not affected: 408 | 2026-07-23T02:13:47+00:00 | Vulnerability · Source |
| CVE-2023-53747 | suse_vex | SUSE CVE CVE-2023-53747 | known affected: 476 known not affected: 184 recommended: 233 | 2026-07-23T02:13:44+00:00 | Vulnerability · Source |
| CVE-2023-53763 | suse_vex | SUSE CVE CVE-2023-53763 | known not affected: 453 | 2026-07-23T02:13:43+00:00 | Vulnerability · Source |
| CVE-2023-53780 | suse_vex | SUSE CVE CVE-2023-53780 | known affected: 374 known not affected: 351 recommended: 136 | 2026-07-23T02:13:41+00:00 | Vulnerability · Source |
| CVE-2023-53800 | suse_vex | SUSE CVE CVE-2023-53800 | known not affected: 448 | 2026-07-23T02:13:40+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-53809 | suse_vex | SUSE CVE CVE-2023-53809 | known not affected: 378 recommended: 50 | 2026-07-23T02:13:37+00:00 | Vulnerability · Source |
| CVE-2023-53816 | suse_vex | SUSE CVE CVE-2023-53816 | known affected: 501 known not affected: 236 recommended: 159 | 2026-07-23T02:13:35+00:00 | Vulnerability · Source |
| CVE-2023-53817 | suse_vex | SUSE CVE CVE-2023-53817 | known affected: 687 known not affected: 17 recommended: 255 | 2026-07-23T02:13:34+00:00 | Vulnerability · Source |
| CVE-2023-53825 | suse_vex | SUSE CVE CVE-2023-53825 | known affected: 608 known not affected: 94 recommended: 253 | 2026-07-23T02:13:32+00:00 | Vulnerability · Source |
| CVE-2023-53829 | suse_vex | SUSE CVE CVE-2023-53829 | known not affected: 453 | 2026-07-23T02:13:31+00:00 | Vulnerability · Source |
| CVE-2023-53836 | suse_vex | SUSE CVE CVE-2023-53836 | known affected: 506 known not affected: 206 recommended: 230 | 2026-07-23T02:13:30+00:00 | Vulnerability · Source |
| CVE-2023-53854 | suse_vex | SUSE CVE CVE-2023-53854 | known not affected: 408 | 2026-07-23T02:13:28+00:00 | Vulnerability · Source |
| CVE-2023-53856 | suse_vex | SUSE CVE CVE-2023-53856 | known affected: 555 known not affected: 157 recommended: 230 | 2026-07-23T02:13:27+00:00 | Vulnerability · Source |
| CVE-2023-53866 | suse_vex | SUSE CVE CVE-2023-53866 | known affected: 354 known not affected: 341 recommended: 245 | 2026-07-23T02:13:25+00:00 | Vulnerability · Source |
| CVE-2023-53988 | suse_vex | SUSE CVE CVE-2023-53988 | known not affected: 453 | 2026-07-23T02:13:24+00:00 | Vulnerability · Source |
| CVE-2023-54002 | suse_vex | SUSE CVE CVE-2023-54002 | known not affected: 453 | 2026-07-23T02:13:22+00:00 | Vulnerability · Source |
| CVE-2023-54006 | suse_vex | SUSE CVE CVE-2023-54006 | known affected: 394 known not affected: 311 recommended: 259 | 2026-07-23T02:13:21+00:00 | Vulnerability · Source |
| CVE-2023-54034 | suse_vex | SUSE CVE CVE-2023-54034 | known not affected: 453 recommended: 29 | 2026-07-23T02:13:19+00:00 | Vulnerability · Source |
| CVE-2023-54045 | suse_vex | SUSE CVE CVE-2023-54045 | known affected: 476 known not affected: 77 recommended: 463 | 2026-07-23T02:13:18+00:00 | Vulnerability · Source |
| CVE-2023-54046 | suse_vex | SUSE CVE CVE-2023-54046 | known affected: 395 known not affected: 268 recommended: 196 | 2026-07-23T02:13:16+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-54077 | suse_vex | SUSE CVE CVE-2023-54077 | known not affected: 421 | 2026-07-23T02:13:12+00:00 | Vulnerability · Source |
| CVE-2023-54085 | suse_vex | SUSE CVE CVE-2023-54085 | known not affected: 453 recommended: 29 | 2026-07-23T02:13:11+00:00 | Vulnerability · Source |
| CVE-2023-54089 | suse_vex | SUSE CVE CVE-2023-54089 | known affected: 394 known not affected: 327 recommended: 273 | 2026-07-23T02:13:09+00:00 | Vulnerability · Source |
| CVE-2023-54092 | suse_vex | SUSE CVE CVE-2023-54092 | known affected: 395 known not affected: 158 recommended: 455 | 2026-07-23T02:13:08+00:00 | Vulnerability · Source |
| CVE-2023-54093 | suse_vex | SUSE CVE CVE-2023-54093 | known affected: 628 known not affected: 77 recommended: 230 | 2026-07-23T02:13:07+00:00 | Vulnerability · Source |
| CVE-2023-54101 | suse_vex | SUSE CVE CVE-2023-54101 | known affected: 394 known not affected: 323 recommended: 230 | 2026-07-23T02:13:05+00:00 | Vulnerability · Source |
| CVE-2023-54107 | suse_vex | SUSE CVE CVE-2023-54107 | known affected: 374 known not affected: 396 recommended: 87 | 2026-07-23T02:13:04+00:00 | Vulnerability · Source |
| CVE-2023-54108 | suse_vex | SUSE CVE CVE-2023-54108 | known affected: 395 known not affected: 270 recommended: 268 | 2026-07-23T02:13:02+00:00 | Vulnerability · Source |
| CVE-2023-54110 | suse_vex | SUSE CVE CVE-2023-54110 | known not affected: 298 recommended: 212 | 2026-07-23T02:13:01+00:00 | Vulnerability · Source |
| CVE-2023-54141 | suse_vex | SUSE CVE CVE-2023-54141 | known affected: 394 known not affected: 343 recommended: 259 | 2026-07-23T02:12:59+00:00 | Vulnerability · Source |
| CVE-2023-54147 | suse_vex | SUSE CVE CVE-2023-54147 | known not affected: 453 | 2026-07-23T02:12:58+00:00 | Vulnerability · Source |
| CVE-2023-54150 | suse_vex | SUSE CVE CVE-2023-54150 | known affected: 426 known not affected: 239 recommended: 196 | 2026-07-23T02:12:57+00:00 | Vulnerability · Source |
| CVE-2023-54153 | suse_vex | SUSE CVE CVE-2023-54153 | known affected: 409 known not affected: 156 recommended: 455 | 2026-07-23T02:12:55+00:00 | Vulnerability · Source |
| CVE-2023-54166 | suse_vex | SUSE CVE CVE-2023-54166 | known affected: 354 known not affected: 211 recommended: 455 | 2026-07-23T02:12:54+00:00 | Vulnerability · Source |
| CVE-2023-54175 | suse_vex | SUSE CVE CVE-2023-54175 | known affected: 374 known not affected: 396 recommended: 87 | 2026-07-23T02:12:52+00:00 | Vulnerability · Source |
| CVE-2023-54176 | suse_vex | SUSE CVE CVE-2023-54176 | known affected: 112 known not affected: 341 recommended: 29 | 2026-07-23T02:12:51+00:00 | Vulnerability · Source |
| CVE-2023-54182 | suse_vex | SUSE CVE CVE-2023-54182 | known affected: 167 known not affected: 286 | 2026-07-23T02:12:50+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-54204 | suse_vex | SUSE CVE CVE-2023-54204 | known affected: 394 known not affected: 343 recommended: 230 | 2026-07-23T02:12:45+00:00 | Vulnerability · Source |
| CVE-2023-54219 | suse_vex | SUSE CVE CVE-2023-54219 | known affected: 354 known not affected: 199 recommended: 426 | 2026-07-23T02:12:44+00:00 | Vulnerability · Source |
| CVE-2023-54221 | suse_vex | SUSE CVE CVE-2023-54221 | known affected: 394 known not affected: 343 recommended: 259 | 2026-07-23T02:12:42+00:00 | Vulnerability · Source |
| CVE-2023-54225 | suse_vex | SUSE CVE CVE-2023-54225 | known affected: 394 known not affected: 311 recommended: 230 | 2026-07-23T02:12:41+00:00 | Vulnerability · Source |
| CVE-2023-54238 | suse_vex | SUSE CVE CVE-2023-54238 | known affected: 374 known not affected: 396 recommended: 136 | 2026-07-23T02:12:39+00:00 | Vulnerability · Source |