VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
97904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-52498 | suse_vex | SUSE CVE CVE-2023-52498 | known affected: 411 known not affected: 344 recommended: 490 | 2026-10-16T13:29:09+00:00 | Vulnerability · Source |
| CVE-2023-52502 | suse_vex | SUSE CVE CVE-2023-52502 | known affected: 375 known not affected: 63 recommended: 1061 | 2026-10-16T13:29:08+00:00 | Vulnerability · Source |
| CVE-2023-52506 | suse_vex | SUSE CVE CVE-2023-52506 | known not affected: 292 | 2026-10-16T13:29:06+00:00 | Vulnerability · Source |
| CVE-2023-52508 | suse_vex | SUSE CVE CVE-2023-52508 | known affected: 254 known not affected: 222 recommended: 764 | 2026-10-16T13:29:05+00:00 | Vulnerability · Source |
| CVE-2023-52509 | suse_vex | SUSE CVE CVE-2023-52509 | known not affected: 216 recommended: 768 | 2026-10-16T13:29:03+00:00 | Vulnerability · Source |
| CVE-2023-52513 | suse_vex | SUSE CVE CVE-2023-52513 | known affected: 327 known not affected: 230 recommended: 693 | 2026-10-16T13:29:01+00:00 | Vulnerability · Source |
| CVE-2023-52514 | suse_vex | SUSE CVE CVE-2023-52514 | No product status | 2026-10-16T13:29:00+00:00 | Vulnerability · Source |
| CVE-2023-52516 | suse_vex | SUSE CVE CVE-2023-52516 | known not affected: 292 | 2026-10-16T13:28:58+00:00 | Vulnerability · Source |
| CVE-2023-52520 | suse_vex | SUSE CVE CVE-2023-52520 | known affected: 260 known not affected: 264 recommended: 693 | 2026-10-16T13:28:56+00:00 | Vulnerability · Source |
| CVE-2023-52522 | suse_vex | SUSE CVE CVE-2023-52522 | known affected: 392 known not affected: 126 recommended: 280 | 2026-10-16T13:28:55+00:00 | Vulnerability · Source |
| CVE-2023-52524 | suse_vex | SUSE CVE CVE-2023-52524 | known affected: 412 known not affected: 71 recommended: 900 | 2026-10-16T13:28:53+00:00 | Vulnerability · Source |
| CVE-2023-52527 | suse_vex | SUSE CVE CVE-2023-52527 | known affected: 773 known not affected: 103 recommended: 272 | 2026-10-16T13:28:52+00:00 | Vulnerability · Source |
| CVE-2023-52530 | suse_vex | SUSE CVE CVE-2023-52530 | known affected: 450 known not affected: 95 recommended: 841 | 2026-10-16T13:28:48+00:00 | Vulnerability · Source |
| CVE-2023-52532 | suse_vex | SUSE CVE CVE-2023-52532 | known affected: 256 known not affected: 207 recommended: 909 | 2026-10-16T13:28:46+00:00 | Vulnerability · Source |
| CVE-2023-52560 | suse_vex | SUSE CVE CVE-2023-52560 | known not affected: 436 recommended: 20 | 2026-10-16T13:28:45+00:00 | Vulnerability · Source |
| CVE-2023-52561 | suse_vex | SUSE CVE CVE-2023-52561 | known affected: 514 known not affected: 223 recommended: 436 | 2026-10-16T13:28:43+00:00 | Vulnerability · Source |
| CVE-2023-52562 | suse_vex | SUSE CVE CVE-2023-52562 | known not affected: 362 recommended: 222 | 2026-10-16T13:28:42+00:00 | Vulnerability · Source |
| CVE-2023-52563 | suse_vex | SUSE CVE CVE-2023-52563 | known affected: 305 known not affected: 279 recommended: 528 | 2026-10-16T13:28:40+00:00 | Vulnerability · Source |
| CVE-2023-52564 | suse_vex | SUSE CVE CVE-2023-52564 | known affected: 260 known not affected: 264 recommended: 673 | 2026-10-16T13:28:38+00:00 | Vulnerability · Source |
| CVE-2023-52566 | suse_vex | SUSE CVE CVE-2023-52566 | known affected: 260 known not affected: 248 recommended: 673 | 2026-10-16T13:28:34+00:00 | Vulnerability · Source |
| CVE-2023-52567 | suse_vex | SUSE CVE CVE-2023-52567 | known affected: 260 known not affected: 264 recommended: 673 | 2026-10-16T13:28:33+00:00 | Vulnerability · Source |
| CVE-2023-52568 | suse_vex | SUSE CVE CVE-2023-52568 | known not affected: 362 recommended: 202 | 2026-10-16T13:28:31+00:00 | Vulnerability · Source |
| CVE-2023-52569 | suse_vex | SUSE CVE CVE-2023-52569 | known affected: 254 known not affected: 223 recommended: 825 | 2026-10-16T13:28:29+00:00 | Vulnerability · Source |
| CVE-2023-52570 | suse_vex | SUSE CVE CVE-2023-52570 | known not affected: 362 recommended: 202 | 2026-10-16T13:28:28+00:00 | Vulnerability · Source |
| CVE-2023-52571 | suse_vex | SUSE CVE CVE-2023-52571 | known not affected: 362 recommended: 202 | 2026-10-16T13:28:26+00:00 | Vulnerability · Source |
| CVE-2023-52573 | suse_vex | SUSE CVE CVE-2023-52573 | known affected: 479 known not affected: 248 recommended: 500 | 2026-10-16T13:28:25+00:00 | Vulnerability · Source |
| CVE-2023-52574 | suse_vex | SUSE CVE CVE-2023-52574 | known affected: 389 known not affected: 59 recommended: 1001 | 2026-10-16T13:28:23+00:00 | Vulnerability · Source |
| CVE-2023-52575 | suse_vex | SUSE CVE CVE-2023-52575 | known affected: 254 known not affected: 164 recommended: 908 | 2026-10-16T13:28:21+00:00 | Vulnerability · Source |
| CVE-2023-52576 | suse_vex | SUSE CVE CVE-2023-52576 | known affected: 260 known not affected: 296 recommended: 673 | 2026-10-16T13:28:19+00:00 | Vulnerability · Source |
| CVE-2023-52579 | suse_vex | SUSE CVE CVE-2023-52579 | known not affected: 292 | 2026-10-16T13:28:17+00:00 | Vulnerability · Source |
| CVE-2023-52581 | suse_vex | SUSE CVE CVE-2023-52581 | known affected: 401 known not affected: 183 recommended: 856 | 2026-10-16T13:28:15+00:00 | Vulnerability · Source |
| CVE-2023-52583 | suse_vex | SUSE CVE CVE-2023-52583 | known affected: 360 known not affected: 87 recommended: 908 | 2026-10-16T13:28:13+00:00 | Vulnerability · Source |
| CVE-2023-52585 | suse_vex | SUSE CVE CVE-2023-52585 | known affected: 310 known not affected: 327 recommended: 520 | 2026-10-16T13:28:10+00:00 | Vulnerability · Source |
| CVE-2023-52589 | suse_vex | SUSE CVE CVE-2023-52589 | known affected: 363 known not affected: 310 recommended: 520 | 2026-10-16T13:28:08+00:00 | Vulnerability · Source |
| CVE-2023-52593 | suse_vex | SUSE CVE CVE-2023-52593 | known affected: 383 known not affected: 350 recommended: 520 | 2026-10-16T13:28:05+00:00 | Vulnerability · Source |
| CVE-2023-52594 | suse_vex | SUSE CVE CVE-2023-52594 | known affected: 485 known not affected: 57 recommended: 632 | 2026-10-16T13:28:03+00:00 | Vulnerability · Source |
| CVE-2023-52595 | suse_vex | SUSE CVE CVE-2023-52595 | known affected: 573 known not affected: 53 recommended: 632 | 2026-10-16T13:28:02+00:00 | Vulnerability · Source |
| CVE-2023-52598 | suse_vex | SUSE CVE CVE-2023-52598 | known affected: 567 known not affected: 59 recommended: 632 | 2026-10-16T13:28:00+00:00 | Vulnerability · Source |
| CVE-2023-52599 | suse_vex | SUSE CVE CVE-2023-52599 | known affected: 305 known not affected: 321 recommended: 528 | 2026-10-16T13:27:58+00:00 | Vulnerability · Source |
| CVE-2023-52601 | suse_vex | SUSE CVE CVE-2023-52601 | known affected: 305 known not affected: 321 recommended: 528 | 2026-10-16T13:27:57+00:00 | Vulnerability · Source |
| CVE-2023-52602 | suse_vex | SUSE CVE CVE-2023-52602 | known affected: 305 known not affected: 321 recommended: 528 | 2026-10-16T13:27:55+00:00 | Vulnerability · Source |
| CVE-2023-52604 | suse_vex | SUSE CVE CVE-2023-52604 | known affected: 305 known not affected: 321 recommended: 528 | 2026-10-16T13:27:53+00:00 | Vulnerability · Source |
| CVE-2023-52606 | suse_vex | SUSE CVE CVE-2023-52606 | known affected: 425 known not affected: 223 recommended: 548 | 2026-10-16T13:27:52+00:00 | Vulnerability · Source |
| CVE-2023-52607 | suse_vex | SUSE CVE CVE-2023-52607 | known affected: 401 known not affected: 57 recommended: 899 | 2026-10-16T13:27:50+00:00 | Vulnerability · Source |
| CVE-2023-52610 | suse_vex | SUSE CVE CVE-2023-52610 | known affected: 514 known not affected: 212 recommended: 710 | 2026-10-16T13:27:48+00:00 | Vulnerability · Source |
| CVE-2023-52612 | suse_vex | SUSE CVE CVE-2023-52612 | known affected: 567 known not affected: 97 recommended: 612 | 2026-10-16T13:27:47+00:00 | Vulnerability · Source |
| CVE-2023-52614 | suse_vex | SUSE CVE CVE-2023-52614 | known affected: 612 known not affected: 69 recommended: 604 | 2026-10-16T13:27:45+00:00 | Vulnerability · Source |
| CVE-2023-52615 | suse_vex | SUSE CVE CVE-2023-52615 | known affected: 485 known not affected: 57 recommended: 632 | 2026-10-16T13:27:43+00:00 | Vulnerability · Source |
| CVE-2023-52616 | suse_vex | SUSE CVE CVE-2023-52616 | known affected: 271 known not affected: 287 recommended: 815 | 2026-10-16T13:27:42+00:00 | Vulnerability · Source |
| CVE-2023-52618 | suse_vex | SUSE CVE CVE-2023-52618 | known affected: 461 known not affected: 265 recommended: 587 | 2026-10-16T13:27:40+00:00 | Vulnerability · Source |