VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
90082 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53723 | suse_vex | SUSE CVE CVE-2023-53723 | known affected: 397 known not affected: 343 recommended: 196 | 2026-10-11T00:55:32+00:00 | Vulnerability · Source |
| CVE-2023-53726 | suse_vex | SUSE CVE CVE-2023-53726 | known affected: 397 known not affected: 213 recommended: 564 | 2026-10-11T00:55:30+00:00 | Vulnerability · Source |
| CVE-2023-53727 | suse_vex | SUSE CVE CVE-2023-53727 | known affected: 565 known not affected: 213 recommended: 310 | 2026-10-11T00:55:27+00:00 | Vulnerability · Source |
| CVE-2023-53729 | suse_vex | SUSE CVE CVE-2023-53729 | known affected: 591 known not affected: 187 recommended: 310 | 2026-10-11T00:55:25+00:00 | Vulnerability · Source |
| CVE-2023-53730 | suse_vex | SUSE CVE CVE-2023-53730 | known affected: 354 known not affected: 256 recommended: 535 | 2026-10-11T00:55:22+00:00 | Vulnerability · Source |
| CVE-2023-53750 | suse_vex | SUSE CVE CVE-2023-53750 | known affected: 394 known not affected: 432 recommended: 212 | 2026-10-11T00:55:19+00:00 | Vulnerability · Source |
| CVE-2023-53759 | suse_vex | SUSE CVE CVE-2023-53759 | known affected: 394 known not affected: 444 recommended: 212 | 2026-10-11T00:55:17+00:00 | Vulnerability · Source |
| CVE-2023-53761 | suse_vex | SUSE CVE CVE-2023-53761 | known affected: 420 known not affected: 356 recommended: 249 | 2026-10-11T00:55:14+00:00 | Vulnerability · Source |
| CVE-2023-53766 | suse_vex | SUSE CVE CVE-2023-53766 | known affected: 354 known not affected: 336 recommended: 408 | 2026-10-11T00:55:11+00:00 | Vulnerability · Source |
| CVE-2023-53768 | suse_vex | SUSE CVE CVE-2023-53768 | known affected: 394 known not affected: 432 recommended: 212 | 2026-10-11T00:55:09+00:00 | Vulnerability · Source |
| CVE-2023-53782 | suse_vex | SUSE CVE CVE-2023-53782 | known affected: 776 known not affected: 70 recommended: 212 | 2026-10-11T00:55:06+00:00 | Vulnerability · Source |
| CVE-2023-53783 | suse_vex | SUSE CVE CVE-2023-53783 | known affected: 427 known not affected: 356 recommended: 196 | 2026-10-11T00:55:03+00:00 | Vulnerability · Source |
| CVE-2023-53784 | suse_vex | SUSE CVE CVE-2023-53784 | known affected: 394 known not affected: 432 recommended: 241 | 2026-10-11T00:55:01+00:00 | Vulnerability · Source |
| CVE-2023-53785 | suse_vex | SUSE CVE CVE-2023-53785 | known affected: 522 known not affected: 304 recommended: 212 | 2026-10-11T00:54:58+00:00 | Vulnerability · Source |
| CVE-2023-53787 | suse_vex | SUSE CVE CVE-2023-53787 | known affected: 394 known not affected: 432 recommended: 212 | 2026-10-11T00:54:55+00:00 | Vulnerability · Source |
| CVE-2023-53793 | suse_vex | SUSE CVE CVE-2023-53793 | known affected: 394 known not affected: 432 recommended: 232 | 2026-10-11T00:54:53+00:00 | Vulnerability · Source |
| CVE-2023-53797 | suse_vex | SUSE CVE CVE-2023-53797 | known affected: 394 known not affected: 432 recommended: 212 | 2026-10-11T00:54:50+00:00 | Vulnerability · Source |
| CVE-2023-53799 | suse_vex | SUSE CVE CVE-2023-53799 | known affected: 782 known not affected: 64 recommended: 212 | 2026-10-11T00:54:47+00:00 | Vulnerability · Source |
| CVE-2023-53807 | suse_vex | SUSE CVE CVE-2023-53807 | known affected: 522 known not affected: 304 recommended: 212 | 2026-10-11T00:54:43+00:00 | Vulnerability · Source |
| CVE-2023-53817 | suse_vex | SUSE CVE CVE-2023-53817 | known affected: 772 known not affected: 17 recommended: 240 | 2026-10-11T00:54:40+00:00 | Vulnerability · Source |
| CVE-2023-53834 | suse_vex | SUSE CVE CVE-2023-53834 | known affected: 354 known not affected: 329 recommended: 408 | 2026-10-11T00:54:37+00:00 | Vulnerability · Source |
| CVE-2023-53843 | suse_vex | SUSE CVE CVE-2023-53843 | known affected: 394 known not affected: 432 recommended: 261 | 2026-10-11T00:54:34+00:00 | Vulnerability · Source |
| CVE-2023-53846 | suse_vex | SUSE CVE CVE-2023-53846 | known affected: 589 known not affected: 237 recommended: 212 | 2026-10-11T00:54:31+00:00 | Vulnerability · Source |
| CVE-2023-53848 | suse_vex | SUSE CVE CVE-2023-53848 | known affected: 374 known not affected: 365 recommended: 348 | 2026-10-11T00:54:28+00:00 | Vulnerability · Source |
| CVE-2023-53852 | suse_vex | SUSE CVE CVE-2023-53852 | known affected: 354 known not affected: 304 recommended: 437 | 2026-10-11T00:54:25+00:00 | Vulnerability · Source |
| CVE-2023-53863 | suse_vex | SUSE CVE CVE-2023-53863 | known affected: 722 known not affected: 64 recommended: 278 | 2026-10-11T00:54:22+00:00 | Vulnerability · Source |
| CVE-2023-53864 | suse_vex | SUSE CVE CVE-2023-53864 | known affected: 374 known not affected: 365 recommended: 299 | 2026-10-11T00:54:19+00:00 | Vulnerability · Source |
| CVE-2023-53992 | suse_vex | SUSE CVE CVE-2023-53992 | known affected: 726 known not affected: 51 recommended: 278 | 2026-10-11T00:54:16+00:00 | Vulnerability · Source |
| CVE-2023-54016 | suse_vex | SUSE CVE CVE-2023-54016 | known affected: 394 known not affected: 451 recommended: 241 | 2026-10-11T00:54:12+00:00 | Vulnerability · Source |
| CVE-2023-54017 | suse_vex | SUSE CVE CVE-2023-54017 | known affected: 495 known not affected: 211 recommended: 322 | 2026-10-11T00:54:09+00:00 | Vulnerability · Source |
| CVE-2023-54022 | suse_vex | SUSE CVE CVE-2023-54022 | known affected: 394 known not affected: 457 recommended: 241 | 2026-10-11T00:54:06+00:00 | Vulnerability · Source |
| CVE-2023-54023 | suse_vex | SUSE CVE CVE-2023-54023 | known affected: 690 known not affected: 55 recommended: 212 | 2026-10-11T00:54:03+00:00 | Vulnerability · Source |
| CVE-2023-54025 | suse_vex | SUSE CVE CVE-2023-54025 | known affected: 401 known not affected: 282 recommended: 408 | 2026-10-11T00:54:00+00:00 | Vulnerability · Source |
| CVE-2023-54026 | suse_vex | SUSE CVE CVE-2023-54026 | known affected: 354 known not affected: 329 recommended: 437 | 2026-10-11T00:53:57+00:00 | Vulnerability · Source |
| CVE-2023-54032 | suse_vex | SUSE CVE CVE-2023-54032 | known affected: 716 known not affected: 75 recommended: 249 | 2026-10-11T00:53:54+00:00 | Vulnerability · Source |
| CVE-2023-54037 | suse_vex | SUSE CVE CVE-2023-54037 | known affected: 394 known not affected: 457 recommended: 261 | 2026-10-11T00:53:51+00:00 | Vulnerability · Source |
| CVE-2023-54045 | suse_vex | SUSE CVE CVE-2023-54045 | known affected: 554 known not affected: 69 recommended: 445 | 2026-10-11T00:53:48+00:00 | Vulnerability · Source |
| CVE-2023-54049 | suse_vex | SUSE CVE CVE-2023-54049 | known affected: 427 known not affected: 256 recommended: 408 | 2026-10-11T00:53:46+00:00 | Vulnerability · Source |
| CVE-2023-54051 | suse_vex | SUSE CVE CVE-2023-54051 | known affected: 520 known not affected: 105 recommended: 431 | 2026-10-11T00:53:43+00:00 | Vulnerability · Source |
| CVE-2023-54066 | suse_vex | SUSE CVE CVE-2023-54066 | known affected: 522 known not affected: 329 recommended: 212 | 2026-10-11T00:53:41+00:00 | Vulnerability · Source |
| CVE-2023-54069 | suse_vex | SUSE CVE CVE-2023-54069 | known affected: 394 known not affected: 457 recommended: 241 | 2026-10-11T00:53:37+00:00 | Vulnerability · Source |
| CVE-2023-54070 | suse_vex | SUSE CVE CVE-2023-54070 | known affected: 435 known not affected: 271 recommended: 371 | 2026-10-11T00:53:35+00:00 | Vulnerability · Source |
| CVE-2023-54076 | suse_vex | SUSE CVE CVE-2023-54076 | known affected: 354 known not affected: 283 recommended: 437 | 2026-10-11T00:53:32+00:00 | Vulnerability · Source |
| CVE-2023-54083 | suse_vex | SUSE CVE CVE-2023-54083 | known affected: 401 known not affected: 236 recommended: 408 | 2026-10-11T00:53:29+00:00 | Vulnerability · Source |
| CVE-2023-54092 | suse_vex | SUSE CVE CVE-2023-54092 | known affected: 401 known not affected: 236 recommended: 437 | 2026-10-11T00:53:27+00:00 | Vulnerability · Source |
| CVE-2023-54095 | suse_vex | SUSE CVE CVE-2023-54095 | known affected: 550 known not affected: 75 recommended: 431 | 2026-10-11T00:53:24+00:00 | Vulnerability · Source |
| CVE-2023-54096 | suse_vex | SUSE CVE CVE-2023-54096 | known affected: 401 known not affected: 248 recommended: 457 | 2026-10-11T00:53:22+00:00 | Vulnerability · Source |
| CVE-2023-54099 | suse_vex | SUSE CVE CVE-2023-54099 | known affected: 595 known not affected: 222 recommended: 212 | 2026-10-11T00:53:19+00:00 | Vulnerability · Source |
| CVE-2023-54101 | suse_vex | SUSE CVE CVE-2023-54101 | known affected: 394 known not affected: 423 recommended: 212 | 2026-10-11T00:53:16+00:00 | Vulnerability · Source |
| CVE-2023-54112 | suse_vex | SUSE CVE CVE-2023-54112 | known affected: 688 known not affected: 105 recommended: 235 | 2026-10-11T00:53:13+00:00 | Vulnerability · Source |