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-53167 | suse_vex | SUSE CVE CVE-2023-53167 | known affected: 395 known not affected: 108 recommended: 552 | 2026-07-25T02:24:33+00:00 | Vulnerability · Source |
| CVE-2023-53170 | suse_vex | SUSE CVE CVE-2023-53170 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T02:24:31+00:00 | Vulnerability · Source |
| CVE-2023-53172 | suse_vex | SUSE CVE CVE-2023-53172 | known not affected: 416 | 2026-07-25T02:24:29+00:00 | Vulnerability · Source |
| CVE-2023-53175 | suse_vex | SUSE CVE CVE-2023-53175 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T02:24:26+00:00 | Vulnerability · Source |
| CVE-2023-53176 | suse_vex | SUSE CVE CVE-2023-53176 | known affected: 462 known not affected: 193 recommended: 243 | 2026-07-25T02:24:24+00:00 | Vulnerability · Source |
| CVE-2023-53177 | suse_vex | SUSE CVE CVE-2023-53177 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T02:24:21+00:00 | Vulnerability · Source |
| CVE-2023-53180 | suse_vex | SUSE CVE CVE-2023-53180 | known affected: 394 known not affected: 271 recommended: 375 | 2026-07-25T02:24:18+00:00 | Vulnerability · Source |
| CVE-2023-53183 | suse_vex | SUSE CVE CVE-2023-53183 | known affected: 506 known not affected: 129 recommended: 369 | 2026-07-25T02:24:15+00:00 | Vulnerability · Source |
| CVE-2023-53184 | suse_vex | SUSE CVE CVE-2023-53184 | known affected: 394 known not affected: 271 recommended: 375 | 2026-07-25T02:24:13+00:00 | Vulnerability · Source |
| CVE-2023-53185 | suse_vex | SUSE CVE CVE-2023-53185 | known affected: 470 known not affected: 20 recommended: 624 | 2026-07-25T02:24:11+00:00 | Vulnerability · Source |
| CVE-2023-53187 | suse_vex | SUSE CVE CVE-2023-53187 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T02:24:09+00:00 | Vulnerability · Source |
| CVE-2023-53189 | suse_vex | SUSE CVE CVE-2023-53189 | known affected: 542 known not affected: 26 recommended: 475 | 2026-07-25T02:24:07+00:00 | Vulnerability · Source |
| CVE-2023-53192 | suse_vex | SUSE CVE CVE-2023-53192 | known affected: 486 known not affected: 179 recommended: 375 | 2026-07-25T02:24:05+00:00 | Vulnerability · Source |
| CVE-2023-53194 | suse_vex | SUSE CVE CVE-2023-53194 | known not affected: 416 | 2026-07-25T02:24:03+00:00 | Vulnerability · Source |
| CVE-2023-53195 | suse_vex | SUSE CVE CVE-2023-53195 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T02:24:01+00:00 | Vulnerability · Source |
| CVE-2023-53196 | suse_vex | SUSE CVE CVE-2023-53196 | known affected: 395 known not affected: 108 recommended: 595 | 2026-07-25T02:23:59+00:00 | Vulnerability · Source |
| CVE-2023-53200 | suse_vex | SUSE CVE CVE-2023-53200 | known affected: 224 known not affected: 160 | 2026-07-25T02:23:57+00:00 | Vulnerability · Source |
| CVE-2023-53201 | suse_vex | SUSE CVE CVE-2023-53201 | known affected: 448 known not affected: 40 recommended: 589 | 2026-07-25T02:23:54+00:00 | Vulnerability · Source |
| CVE-2023-53205 | suse_vex | SUSE CVE CVE-2023-53205 | known affected: 344 known not affected: 159 recommended: 581 | 2026-07-25T02:23:49+00:00 | Vulnerability · Source |
| CVE-2023-53208 | suse_vex | SUSE CVE CVE-2023-53208 | known affected: 394 known not affected: 271 recommended: 375 | 2026-07-25T02:23:46+00:00 | Vulnerability · Source |
| CVE-2023-53209 | suse_vex | SUSE CVE CVE-2023-53209 | known affected: 394 known not affected: 271 recommended: 375 | 2026-07-25T02:23:43+00:00 | Vulnerability · Source |
| CVE-2023-53210 | suse_vex | SUSE CVE CVE-2023-53210 | known affected: 369 known not affected: 214 recommended: 487 | 2026-07-25T02:23:41+00:00 | Vulnerability · Source |
| CVE-2023-53213 | suse_vex | SUSE CVE CVE-2023-53213 | known not affected: 233 recommended: 321 | 2026-07-25T02:23:38+00:00 | Vulnerability · Source |
| CVE-2023-53215 | suse_vex | SUSE CVE CVE-2023-53215 | known affected: 441 known not affected: 31 recommended: 574 | 2026-07-25T02:23:36+00:00 | Vulnerability · Source |
| CVE-2023-53216 | suse_vex | SUSE CVE CVE-2023-53216 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-25T02:23:34+00:00 | Vulnerability · Source |
| CVE-2023-53217 | suse_vex | SUSE CVE CVE-2023-53217 | known affected: 500 known not affected: 165 recommended: 346 | 2026-07-25T02:23:32+00:00 | Vulnerability · Source |
| CVE-2023-53220 | suse_vex | SUSE CVE CVE-2023-53220 | known affected: 569 known not affected: 43 recommended: 413 | 2026-07-25T02:23:29+00:00 | Vulnerability · Source |
| CVE-2023-53221 | suse_vex | SUSE CVE CVE-2023-53221 | known affected: 449 known not affected: 216 recommended: 375 | 2026-07-25T02:23:27+00:00 | Vulnerability · Source |
| CVE-2023-53222 | suse_vex | SUSE CVE CVE-2023-53222 | known affected: 344 known not affected: 159 recommended: 552 | 2026-07-25T02:23:25+00:00 | Vulnerability · Source |
| CVE-2023-53226 | suse_vex | SUSE CVE CVE-2023-53226 | known affected: 462 known not affected: 26 recommended: 609 | 2026-07-25T02:23:22+00:00 | Vulnerability · Source |
| CVE-2023-53228 | suse_vex | SUSE CVE CVE-2023-53228 | known not affected: 416 recommended: 29 | 2026-07-25T02:23:20+00:00 | Vulnerability · Source |
| CVE-2023-53230 | suse_vex | SUSE CVE CVE-2023-53230 | known affected: 344 known not affected: 159 recommended: 572 | 2026-07-25T02:23:17+00:00 | Vulnerability · Source |
| CVE-2023-53231 | suse_vex | SUSE CVE CVE-2023-53231 | known affected: 500 known not affected: 165 recommended: 346 | 2026-07-25T02:23:15+00:00 | Vulnerability · Source |
| CVE-2023-53232 | suse_vex | SUSE CVE CVE-2023-53232 | known affected: 369 known not affected: 359 recommended: 141 | 2026-07-25T02:23:13+00:00 | Vulnerability · Source |
| CVE-2023-53233 | suse_vex | SUSE CVE CVE-2023-53233 | known affected: 92 known not affected: 324 recommended: 49 | 2026-07-25T02:23:11+00:00 | Vulnerability · Source |
| CVE-2023-53235 | suse_vex | SUSE CVE CVE-2023-53235 | known affected: 394 known not affected: 271 recommended: 375 | 2026-07-25T02:23:09+00:00 | Vulnerability · Source |
| CVE-2023-53237 | suse_vex | SUSE CVE CVE-2023-53237 | known affected: 369 known not affected: 359 recommended: 121 | 2026-07-25T02:23:06+00:00 | Vulnerability · Source |
| CVE-2023-53238 | suse_vex | SUSE CVE CVE-2023-53238 | known affected: 395 known not affected: 108 recommended: 552 | 2026-07-25T02:23:04+00:00 | Vulnerability · Source |
| CVE-2023-53239 | suse_vex | SUSE CVE CVE-2023-53239 | known affected: 395 known not affected: 253 recommended: 206 | 2026-07-25T02:23:02+00:00 | Vulnerability · Source |
| CVE-2023-53242 | suse_vex | SUSE CVE CVE-2023-53242 | known affected: 395 known not affected: 253 recommended: 206 | 2026-07-25T02:23:00+00:00 | Vulnerability · Source |
| CVE-2023-53244 | suse_vex | SUSE CVE CVE-2023-53244 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-25T02:22:55+00:00 | Vulnerability · Source |
| CVE-2023-53247 | suse_vex | SUSE CVE CVE-2023-53247 | known affected: 506 known not affected: 159 recommended: 346 | 2026-07-25T02:22:51+00:00 | Vulnerability · Source |
| CVE-2023-53248 | suse_vex | SUSE CVE CVE-2023-53248 | known affected: 512 known not affected: 140 recommended: 398 | 2026-07-25T02:22:49+00:00 | Vulnerability · Source |
| CVE-2023-53249 | suse_vex | SUSE CVE CVE-2023-53249 | known affected: 381 known not affected: 122 recommended: 552 | 2026-07-25T02:22:46+00:00 | Vulnerability · Source |
| CVE-2023-53250 | suse_vex | SUSE CVE CVE-2023-53250 | known affected: 381 known not affected: 235 recommended: 243 | 2026-07-25T02:22:43+00:00 | Vulnerability · Source |
| CVE-2023-53252 | suse_vex | SUSE CVE CVE-2023-53252 | known affected: 369 known not affected: 214 recommended: 467 | 2026-07-25T02:22:40+00:00 | Vulnerability · Source |
| CVE-2023-53255 | suse_vex | SUSE CVE CVE-2023-53255 | known affected: 381 known not affected: 122 recommended: 552 | 2026-07-25T02:22:34+00:00 | Vulnerability · Source |
| CVE-2023-53257 | suse_vex | SUSE CVE CVE-2023-53257 | known affected: 369 known not affected: 214 recommended: 466 | 2026-07-25T02:22:32+00:00 | Vulnerability · Source |
| CVE-2023-53258 | suse_vex | SUSE CVE CVE-2023-53258 | known affected: 369 known not affected: 214 recommended: 467 | 2026-07-25T02:22:30+00:00 | Vulnerability · Source |
| CVE-2023-53260 | suse_vex | SUSE CVE CVE-2023-53260 | known affected: 394 known not affected: 271 recommended: 389 | 2026-07-25T02:22:28+00:00 | Vulnerability · Source |