VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292260 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-54060 | suse_vex | SUSE CVE CVE-2023-54060 | known affected: 394 known not affected: 343 recommended: 259 | 2026-07-25T02:08:41+00:00 | Vulnerability · Source |
| CVE-2023-54061 | suse_vex | SUSE CVE CVE-2023-54061 | known not affected: 453 | 2026-07-25T02:08:39+00:00 | Vulnerability · Source |
| CVE-2023-54066 | suse_vex | SUSE CVE CVE-2023-54066 | known affected: 506 known not affected: 231 recommended: 230 | 2026-07-25T02:08:34+00:00 | Vulnerability · Source |
| CVE-2023-54067 | suse_vex | SUSE CVE CVE-2023-54067 | known affected: 608 known not affected: 99 recommended: 253 | 2026-07-25T02:08:32+00:00 | Vulnerability · Source |
| CVE-2023-54069 | suse_vex | SUSE CVE CVE-2023-54069 | known affected: 394 known not affected: 343 recommended: 259 | 2026-07-25T02:08:29+00:00 | Vulnerability · Source |
| CVE-2023-54070 | suse_vex | SUSE CVE CVE-2023-54070 | known affected: 429 known not affected: 201 recommended: 369 | 2026-07-25T02:08:26+00:00 | Vulnerability · Source |
| CVE-2023-54072 | suse_vex | SUSE CVE CVE-2023-54072 | known affected: 395 known not affected: 170 recommended: 455 | 2026-07-25T02:08:23+00:00 | Vulnerability · Source |
| CVE-2023-54074 | suse_vex | SUSE CVE CVE-2023-54074 | known affected: 374 known not affected: 396 recommended: 136 | 2026-07-25T02:08:21+00:00 | Vulnerability · Source |
| CVE-2023-54075 | suse_vex | SUSE CVE CVE-2023-54075 | known not affected: 453 | 2026-07-25T02:08:18+00:00 | Vulnerability · Source |
| CVE-2023-54076 | suse_vex | SUSE CVE CVE-2023-54076 | known affected: 354 known not affected: 199 recommended: 455 | 2026-07-25T02:08:16+00:00 | Vulnerability · Source |
| CVE-2023-54078 | suse_vex | SUSE CVE CVE-2023-54078 | known affected: 354 known not affected: 309 recommended: 196 | 2026-07-25T02:08:13+00:00 | Vulnerability · Source |
| CVE-2023-54080 | suse_vex | SUSE CVE CVE-2023-54080 | known not affected: 311 recommended: 230 | 2026-07-25T02:08:10+00:00 | Vulnerability · Source |
| CVE-2023-54081 | suse_vex | SUSE CVE CVE-2023-54081 | known affected: 654 known not affected: 83 recommended: 230 | 2026-07-25T02:08:07+00:00 | Vulnerability · Source |
| CVE-2023-54083 | suse_vex | SUSE CVE CVE-2023-54083 | known affected: 395 known not affected: 158 recommended: 426 | 2026-07-25T02:08:05+00:00 | Vulnerability · Source |
| CVE-2023-54084 | suse_vex | SUSE CVE CVE-2023-54084 | known affected: 395 known not affected: 300 recommended: 196 | 2026-07-25T02:08:02+00:00 | Vulnerability · Source |
| CVE-2023-54087 | suse_vex | SUSE CVE CVE-2023-54087 | known affected: 234 known not affected: 187 | 2026-07-25T02:07:59+00:00 | Vulnerability · Source |
| CVE-2023-54088 | suse_vex | SUSE CVE CVE-2023-54088 | known affected: 433 known not affected: 283 recommended: 259 | 2026-07-25T02:07:56+00:00 | Vulnerability · Source |
| CVE-2023-54091 | suse_vex | SUSE CVE CVE-2023-54091 | known affected: 462 known not affected: 71 recommended: 512 | 2026-07-25T02:07:53+00:00 | Vulnerability · Source |
| CVE-2023-54094 | suse_vex | SUSE CVE CVE-2023-54094 | known affected: 547 known not affected: 170 recommended: 230 | 2026-07-25T02:07:49+00:00 | Vulnerability · Source |
| CVE-2023-54095 | suse_vex | SUSE CVE CVE-2023-54095 | known affected: 472 known not affected: 83 recommended: 449 | 2026-07-25T02:07:46+00:00 | Vulnerability · Source |
| CVE-2023-54096 | suse_vex | SUSE CVE CVE-2023-54096 | known affected: 395 known not affected: 170 recommended: 455 | 2026-07-25T02:07:43+00:00 | Vulnerability · Source |
| CVE-2023-54099 | suse_vex | SUSE CVE CVE-2023-54099 | known affected: 561 known not affected: 156 recommended: 230 | 2026-07-25T02:07:41+00:00 | Vulnerability · Source |
| CVE-2023-54102 | suse_vex | SUSE CVE CVE-2023-54102 | known affected: 456 known not affected: 241 recommended: 245 | 2026-07-25T02:07:38+00:00 | Vulnerability · Source |
| CVE-2023-54104 | suse_vex | SUSE CVE CVE-2023-54104 | known affected: 354 known not affected: 231 recommended: 426 | 2026-07-25T02:07:36+00:00 | Vulnerability · Source |
| CVE-2023-54106 | suse_vex | SUSE CVE CVE-2023-54106 | known affected: 374 known not affected: 286 recommended: 346 | 2026-07-25T02:07:34+00:00 | Vulnerability · Source |
| CVE-2023-54111 | suse_vex | SUSE CVE CVE-2023-54111 | known affected: 470 known not affected: 195 recommended: 219 | 2026-07-25T02:07:31+00:00 | Vulnerability · Source |
| CVE-2023-54112 | suse_vex | SUSE CVE CVE-2023-54112 | known affected: 608 known not affected: 99 recommended: 253 | 2026-07-25T02:07:28+00:00 | Vulnerability · Source |
| CVE-2023-54113 | suse_vex | SUSE CVE CVE-2023-54113 | known affected: 506 known not affected: 231 recommended: 230 | 2026-07-25T02:07:26+00:00 | Vulnerability · Source |
| CVE-2023-54114 | suse_vex | SUSE CVE CVE-2023-54114 | known affected: 110 known not affected: 286 recommended: 87 | 2026-07-25T02:07:23+00:00 | Vulnerability · Source |
| CVE-2023-54115 | suse_vex | SUSE CVE CVE-2023-54115 | known affected: 354 known not affected: 199 recommended: 426 | 2026-07-25T02:07:21+00:00 | Vulnerability · Source |
| CVE-2023-54116 | suse_vex | SUSE CVE CVE-2023-54116 | known affected: 374 known not affected: 396 recommended: 87 | 2026-07-25T02:07:18+00:00 | Vulnerability · Source |
| CVE-2023-54117 | suse_vex | SUSE CVE CVE-2023-54117 | known affected: 394 known not affected: 343 recommended: 273 | 2026-07-25T02:07:15+00:00 | Vulnerability · Source |
| CVE-2023-54120 | suse_vex | SUSE CVE CVE-2023-54120 | known affected: 460 known not affected: 171 recommended: 262 | 2026-07-25T02:07:13+00:00 | Vulnerability · Source |
| CVE-2023-54121 | suse_vex | SUSE CVE CVE-2023-54121 | known affected: 628 known not affected: 77 recommended: 267 | 2026-07-25T02:07:11+00:00 | Vulnerability · Source |
| CVE-2023-54125 | suse_vex | SUSE CVE CVE-2023-54125 | known affected: 394 known not affected: 343 recommended: 230 | 2026-07-25T02:07:08+00:00 | Vulnerability · Source |
| CVE-2023-54126 | suse_vex | SUSE CVE CVE-2023-54126 | known affected: 456 known not affected: 239 recommended: 196 | 2026-07-25T02:07:06+00:00 | Vulnerability · Source |
| CVE-2023-54127 | suse_vex | SUSE CVE CVE-2023-54127 | known affected: 354 known not affected: 199 recommended: 426 | 2026-07-25T02:07:03+00:00 | Vulnerability · Source |
| CVE-2023-54128 | suse_vex | SUSE CVE CVE-2023-54128 | known affected: 429 known not affected: 341 recommended: 87 | 2026-07-25T02:07:01+00:00 | Vulnerability · Source |
| CVE-2023-54129 | suse_vex | SUSE CVE CVE-2023-54129 | known affected: 167 known not affected: 286 recommended: 29 | 2026-07-25T02:06:58+00:00 | Vulnerability · Source |
| CVE-2023-54130 | suse_vex | SUSE CVE CVE-2023-54130 | known affected: 354 known not affected: 311 recommended: 219 | 2026-07-25T02:06:56+00:00 | Vulnerability · Source |
| CVE-2023-54133 | suse_vex | SUSE CVE CVE-2023-54133 | known affected: 394 known not affected: 323 recommended: 230 | 2026-07-25T02:06:53+00:00 | Vulnerability · Source |
| CVE-2023-54134 | suse_vex | SUSE CVE CVE-2023-54134 | known affected: 551 known not affected: 77 recommended: 354 | 2026-07-25T02:06:51+00:00 | Vulnerability · Source |
| CVE-2023-54135 | suse_vex | SUSE CVE CVE-2023-54135 | known affected: 394 known not affected: 323 recommended: 259 | 2026-07-25T02:06:48+00:00 | Vulnerability · Source |
| CVE-2023-54136 | suse_vex | SUSE CVE CVE-2023-54136 | known affected: 409 known not affected: 156 recommended: 426 | 2026-07-25T02:06:45+00:00 | Vulnerability · Source |
| CVE-2023-54137 | suse_vex | SUSE CVE CVE-2023-54137 | known affected: 547 known not affected: 170 recommended: 259 | 2026-07-25T02:06:43+00:00 | Vulnerability · Source |
| CVE-2023-54138 | suse_vex | SUSE CVE CVE-2023-54138 | known affected: 374 known not affected: 396 recommended: 87 | 2026-07-25T02:06:41+00:00 | Vulnerability · Source |
| CVE-2023-54142 | suse_vex | SUSE CVE CVE-2023-54142 | known affected: 402 known not affected: 176 recommended: 454 | 2026-07-25T02:06:37+00:00 | Vulnerability · Source |
| CVE-2023-54143 | suse_vex | SUSE CVE CVE-2023-54143 | known affected: 394 known not affected: 343 recommended: 230 | 2026-07-25T02:06:35+00:00 | Vulnerability · Source |
| CVE-2023-54144 | suse_vex | SUSE CVE CVE-2023-54144 | known affected: 374 known not affected: 396 recommended: 136 | 2026-07-25T02:06:33+00:00 | Vulnerability · Source |
| CVE-2023-54145 | suse_vex | SUSE CVE CVE-2023-54145 | known affected: 638 known not affected: 99 recommended: 259 | 2026-07-25T02:06:30+00:00 | Vulnerability · Source |