VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
90092 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53293 | suse_vex | SUSE CVE CVE-2023-53293 | known not affected: 523 recommended: 58 | 2026-10-11T01:01:24+00:00 | Vulnerability · Source |
| CVE-2023-53302 | suse_vex | SUSE CVE CVE-2023-53302 | known affected: 546 known not affected: 170 recommended: 243 | 2026-10-11T01:01:21+00:00 | Vulnerability · Source |
| CVE-2023-53303 | suse_vex | SUSE CVE CVE-2023-53303 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-11T01:01:19+00:00 | Vulnerability · Source |
| CVE-2023-53305 | suse_vex | SUSE CVE CVE-2023-53305 | known affected: 344 known not affected: 205 recommended: 586 | 2026-10-11T01:01:17+00:00 | Vulnerability · Source |
| CVE-2023-53311 | suse_vex | SUSE CVE CVE-2023-53311 | known affected: 415 known not affected: 194 recommended: 516 | 2026-10-11T01:01:14+00:00 | Vulnerability · Source |
| CVE-2023-53313 | suse_vex | SUSE CVE CVE-2023-53313 | known affected: 540 known not affected: 9 recommended: 539 | 2026-10-11T01:01:13+00:00 | Vulnerability · Source |
| CVE-2023-53315 | suse_vex | SUSE CVE CVE-2023-53315 | known affected: 344 known not affected: 395 recommended: 206 | 2026-10-11T01:01:11+00:00 | Vulnerability · Source |
| CVE-2023-53316 | suse_vex | SUSE CVE CVE-2023-53316 | known affected: 344 known not affected: 265 recommended: 516 | 2026-10-11T01:01:09+00:00 | Vulnerability · Source |
| CVE-2023-53319 | suse_vex | SUSE CVE CVE-2023-53319 | known affected: 394 known not affected: 393 recommended: 339 | 2026-10-11T01:01:07+00:00 | Vulnerability · Source |
| CVE-2023-53324 | suse_vex | SUSE CVE CVE-2023-53324 | known affected: 564 known not affected: 45 recommended: 516 | 2026-10-11T01:01:05+00:00 | Vulnerability · Source |
| CVE-2023-53325 | suse_vex | SUSE CVE CVE-2023-53325 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-11T01:01:03+00:00 | Vulnerability · Source |
| CVE-2023-53337 | suse_vex | SUSE CVE CVE-2023-53337 | known affected: 387 known not affected: 352 recommended: 206 | 2026-10-11T01:01:01+00:00 | Vulnerability · Source |
| CVE-2023-53338 | suse_vex | SUSE CVE CVE-2023-53338 | known affected: 684 known not affected: 45 recommended: 362 | 2026-10-11T01:00:59+00:00 | Vulnerability · Source |
| CVE-2023-53340 | suse_vex | SUSE CVE CVE-2023-53340 | known affected: 369 known not affected: 456 recommended: 92 | 2026-10-11T01:00:57+00:00 | Vulnerability · Source |
| CVE-2023-53342 | suse_vex | SUSE CVE CVE-2023-53342 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-11T01:00:55+00:00 | Vulnerability · Source |
| CVE-2023-53343 | suse_vex | SUSE CVE CVE-2023-53343 | known affected: 524 known not affected: 263 recommended: 388 | 2026-10-11T01:00:53+00:00 | Vulnerability · Source |
| CVE-2023-53347 | suse_vex | SUSE CVE CVE-2023-53347 | known affected: 499 known not affected: 326 recommended: 92 | 2026-10-11T01:00:51+00:00 | Vulnerability · Source |
| CVE-2023-53349 | suse_vex | SUSE CVE CVE-2023-53349 | known affected: 344 known not affected: 395 recommended: 206 | 2026-10-11T01:00:49+00:00 | Vulnerability · Source |
| CVE-2023-53350 | suse_vex | SUSE CVE CVE-2023-53350 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-11T01:00:47+00:00 | Vulnerability · Source |
| CVE-2023-53354 | suse_vex | SUSE CVE CVE-2023-53354 | known affected: 524 known not affected: 263 recommended: 388 | 2026-10-11T01:00:45+00:00 | Vulnerability · Source |
| CVE-2023-53356 | suse_vex | SUSE CVE CVE-2023-53356 | known affected: 344 known not affected: 265 recommended: 516 | 2026-10-11T01:00:43+00:00 | Vulnerability · Source |
| CVE-2023-53359 | suse_vex | SUSE CVE CVE-2023-53359 | known affected: 540 known not affected: 139 recommended: 284 | 2026-10-11T01:00:41+00:00 | Vulnerability · Source |
| CVE-2023-53360 | suse_vex | SUSE CVE CVE-2023-53360 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-11T01:00:39+00:00 | Vulnerability · Source |
| CVE-2023-53362 | suse_vex | SUSE CVE CVE-2023-53362 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-11T01:00:36+00:00 | Vulnerability · Source |
| CVE-2023-53369 | suse_vex | SUSE CVE CVE-2023-53369 | known affected: 657 known not affected: 87 recommended: 347 | 2026-10-11T01:00:34+00:00 | Vulnerability · Source |
| CVE-2023-53370 | suse_vex | SUSE CVE CVE-2023-53370 | known affected: 369 known not affected: 326 recommended: 460 | 2026-10-11T01:00:32+00:00 | Vulnerability · Source |
| CVE-2023-53372 | suse_vex | SUSE CVE CVE-2023-53372 | known affected: 130 known not affected: 393 recommended: 49 | 2026-10-11T01:00:30+00:00 | Vulnerability · Source |
| CVE-2023-53375 | suse_vex | SUSE CVE CVE-2023-53375 | known affected: 413 known not affected: 326 recommended: 206 | 2026-10-11T01:00:28+00:00 | Vulnerability · Source |
| CVE-2023-53376 | suse_vex | SUSE CVE CVE-2023-53376 | known affected: 104 known not affected: 419 recommended: 78 | 2026-10-11T01:00:27+00:00 | Vulnerability · Source |
| CVE-2023-53381 | suse_vex | SUSE CVE CVE-2023-53381 | known affected: 344 known not affected: 395 recommended: 260 | 2026-10-11T01:00:25+00:00 | Vulnerability · Source |
| CVE-2023-53386 | suse_vex | SUSE CVE CVE-2023-53386 | known affected: 387 known not affected: 222 recommended: 536 | 2026-10-11T01:00:22+00:00 | Vulnerability · Source |
| CVE-2023-53387 | suse_vex | SUSE CVE CVE-2023-53387 | known affected: 330 known not affected: 155 recommended: 29 | 2026-10-11T01:00:21+00:00 | Vulnerability · Source |
| CVE-2023-53388 | suse_vex | SUSE CVE CVE-2023-53388 | known affected: 480 known not affected: 201 recommended: 206 | 2026-10-11T01:00:19+00:00 | Vulnerability · Source |
| CVE-2023-53391 | suse_vex | SUSE CVE CVE-2023-53391 | known affected: 692 known not affected: 22 recommended: 402 | 2026-10-11T01:00:17+00:00 | Vulnerability · Source |
| CVE-2023-53397 | suse_vex | SUSE CVE CVE-2023-53397 | known affected: 651 known not affected: 93 recommended: 347 | 2026-10-11T01:00:15+00:00 | Vulnerability · Source |
| CVE-2023-53405 | suse_vex | SUSE CVE CVE-2023-53405 | known affected: 344 known not affected: 395 recommended: 206 | 2026-10-11T01:00:13+00:00 | Vulnerability · Source |
| CVE-2023-53407 | suse_vex | SUSE CVE CVE-2023-53407 | known affected: 354 known not affected: 397 recommended: 196 | 2026-10-11T01:00:11+00:00 | Vulnerability · Source |
| CVE-2023-53409 | suse_vex | SUSE CVE CVE-2023-53409 | known affected: 344 known not affected: 395 recommended: 284 | 2026-10-11T01:00:09+00:00 | Vulnerability · Source |
| CVE-2023-53410 | suse_vex | SUSE CVE CVE-2023-53410 | known affected: 67 known not affected: 456 recommended: 78 | 2026-10-11T01:00:08+00:00 | Vulnerability · Source |
| CVE-2023-53412 | suse_vex | SUSE CVE CVE-2023-53412 | known affected: 354 known not affected: 395 recommended: 196 | 2026-10-11T01:00:06+00:00 | Vulnerability · Source |
| CVE-2023-53415 | suse_vex | SUSE CVE CVE-2023-53415 | known affected: 344 known not affected: 395 recommended: 264 | 2026-10-11T01:00:04+00:00 | Vulnerability · Source |
| CVE-2023-53417 | suse_vex | SUSE CVE CVE-2023-53417 | known affected: 354 known not affected: 389 recommended: 196 | 2026-10-11T01:00:02+00:00 | Vulnerability · Source |
| CVE-2023-53418 | suse_vex | SUSE CVE CVE-2023-53418 | known affected: 354 known not affected: 389 recommended: 196 | 2026-10-11T01:00:00+00:00 | Vulnerability · Source |
| CVE-2023-53422 | suse_vex | SUSE CVE CVE-2023-53422 | known affected: 387 known not affected: 352 recommended: 284 | 2026-10-11T00:59:58+00:00 | Vulnerability · Source |
| CVE-2023-53426 | suse_vex | SUSE CVE CVE-2023-53426 | known affected: 394 known not affected: 393 recommended: 351 | 2026-10-11T00:59:56+00:00 | Vulnerability · Source |
| CVE-2023-53429 | suse_vex | SUSE CVE CVE-2023-53429 | known affected: 651 known not affected: 76 recommended: 310 | 2026-10-11T00:59:54+00:00 | Vulnerability · Source |
| CVE-2023-53433 | suse_vex | SUSE CVE CVE-2023-53433 | known affected: 557 known not affected: 302 recommended: 81 | 2026-10-11T00:59:52+00:00 | Vulnerability · Source |
| CVE-2023-53436 | suse_vex | SUSE CVE CVE-2023-53436 | known affected: 540 known not affected: 26 recommended: 553 | 2026-10-11T00:59:50+00:00 | Vulnerability · Source |
| CVE-2023-53443 | suse_vex | SUSE CVE CVE-2023-53443 | known affected: 348 known not affected: 391 recommended: 284 | 2026-10-11T00:59:48+00:00 | Vulnerability · Source |
| CVE-2023-53444 | suse_vex | SUSE CVE CVE-2023-53444 | known affected: 369 known not affected: 326 recommended: 460 | 2026-10-11T00:59:45+00:00 | Vulnerability · Source |