VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
90149 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-52631 | suse_vex | SUSE CVE CVE-2023-52631 | known not affected: 397 recommended: 351 | 2026-10-11T01:08:43+00:00 | Vulnerability · Source |
| CVE-2023-52635 | suse_vex | SUSE CVE CVE-2023-52635 | known affected: 456 known not affected: 6 recommended: 755 | 2026-10-11T01:08:39+00:00 | Vulnerability · Source |
| CVE-2023-52647 | suse_vex | SUSE CVE CVE-2023-52647 | known affected: 394 known not affected: 385 recommended: 209 | 2026-10-11T01:08:34+00:00 | Vulnerability · Source |
| CVE-2023-52649 | suse_vex | SUSE CVE CVE-2023-52649 | known affected: 394 known not affected: 385 recommended: 209 | 2026-10-11T01:08:32+00:00 | Vulnerability · Source |
| CVE-2023-52651 | suse_vex | SUSE CVE CVE-2023-52651 | known not affected: 385 recommended: 58 | 2026-10-11T01:08:30+00:00 | Vulnerability · Source |
| CVE-2023-52653 | suse_vex | SUSE CVE CVE-2023-52653 | known affected: 575 known not affected: 7 recommended: 799 | 2026-10-11T01:08:28+00:00 | Vulnerability · Source |
| CVE-2023-52658 | suse_vex | SUSE CVE CVE-2023-52658 | known affected: 330 known not affected: 237 recommended: 733 | 2026-10-11T01:08:26+00:00 | Vulnerability · Source |
| CVE-2023-52659 | suse_vex | SUSE CVE CVE-2023-52659 | known affected: 315 known not affected: 305 recommended: 666 | 2026-10-11T01:08:24+00:00 | Vulnerability · Source |
| CVE-2023-52661 | suse_vex | SUSE CVE CVE-2023-52661 | known affected: 315 known not affected: 270 recommended: 670 | 2026-10-11T01:08:23+00:00 | Vulnerability · Source |
| CVE-2023-52667 | suse_vex | SUSE CVE CVE-2023-52667 | known affected: 330 known not affected: 237 recommended: 733 | 2026-10-11T01:08:21+00:00 | Vulnerability · Source |
| CVE-2023-52672 | suse_vex | SUSE CVE CVE-2023-52672 | known affected: 419 known not affected: 237 recommended: 737 | 2026-10-11T01:08:19+00:00 | Vulnerability · Source |
| CVE-2023-52679 | suse_vex | SUSE CVE CVE-2023-52679 | known affected: 464 known not affected: 161 recommended: 690 | 2026-10-11T01:08:15+00:00 | Vulnerability · Source |
| CVE-2023-52680 | suse_vex | SUSE CVE CVE-2023-52680 | known affected: 464 known not affected: 155 recommended: 666 | 2026-10-11T01:08:13+00:00 | Vulnerability · Source |
| CVE-2023-52681 | suse_vex | SUSE CVE CVE-2023-52681 | known not affected: 332 recommended: 357 | 2026-10-11T01:08:11+00:00 | Vulnerability · Source |
| CVE-2023-52685 | suse_vex | SUSE CVE CVE-2023-52685 | known affected: 577 known not affected: 14 recommended: 747 | 2026-10-11T01:08:09+00:00 | Vulnerability · Source |
| CVE-2023-52688 | suse_vex | SUSE CVE CVE-2023-52688 | known affected: 394 known not affected: 332 recommended: 355 | 2026-10-11T01:08:05+00:00 | Vulnerability · Source |
| CVE-2023-52689 | suse_vex | SUSE CVE CVE-2023-52689 | known not affected: 385 recommended: 47 | 2026-10-11T01:08:03+00:00 | Vulnerability · Source |
| CVE-2023-52691 | suse_vex | SUSE CVE CVE-2023-52691 | known affected: 569 known not affected: 20 recommended: 740 | 2026-10-11T01:07:58+00:00 | Vulnerability · Source |
| CVE-2023-52692 | suse_vex | SUSE CVE CVE-2023-52692 | known affected: 382 known not affected: 237 recommended: 666 | 2026-10-11T01:07:56+00:00 | Vulnerability · Source |
| CVE-2023-52695 | suse_vex | SUSE CVE CVE-2023-52695 | known affected: 394 known not affected: 332 recommended: 357 | 2026-10-11T01:07:55+00:00 | Vulnerability · Source |
| CVE-2023-52700 | suse_vex | SUSE CVE CVE-2023-52700 | known not affected: 385 recommended: 20 | 2026-10-11T01:07:47+00:00 | Vulnerability · Source |
| CVE-2023-52722 | suse_vex | SUSE CVE CVE-2023-52722 | known affected: 108 recommended: 77 | 2026-10-11T01:07:45+00:00 | Vulnerability · Source |
| CVE-2023-52731 | suse_vex | SUSE CVE CVE-2023-52731 | known affected: 315 known not affected: 323 recommended: 313 | 2026-10-11T01:07:43+00:00 | Vulnerability · Source |
| CVE-2023-52735 | suse_vex | SUSE CVE CVE-2023-52735 | known affected: 446 known not affected: 194 recommended: 713 | 2026-10-11T01:07:41+00:00 | Vulnerability · Source |
| CVE-2023-52737 | suse_vex | SUSE CVE CVE-2023-52737 | known affected: 330 known not affected: 316 recommended: 382 | 2026-10-11T01:07:39+00:00 | Vulnerability · Source |
| CVE-2023-52738 | suse_vex | SUSE CVE CVE-2023-52738 | known affected: 275 known not affected: 266 recommended: 452 | 2026-10-11T01:07:37+00:00 | Vulnerability · Source |
| CVE-2023-52741 | suse_vex | SUSE CVE CVE-2023-52741 | known affected: 421 known not affected: 71 recommended: 536 | 2026-10-11T01:07:36+00:00 | Vulnerability · Source |
| CVE-2023-52746 | suse_vex | SUSE CVE CVE-2023-52746 | known affected: 368 known not affected: 266 recommended: 313 | 2026-10-11T01:07:34+00:00 | Vulnerability · Source |
| CVE-2023-52750 | suse_vex | SUSE CVE CVE-2023-52750 | known affected: 538 known not affected: 271 recommended: 353 | 2026-10-11T01:07:32+00:00 | Vulnerability · Source |
| CVE-2023-52752 | suse_vex | SUSE CVE CVE-2023-52752 | known affected: 312 known not affected: 123 recommended: 1170 | 2026-10-11T01:07:30+00:00 | Vulnerability · Source |
| CVE-2023-52756 | suse_vex | SUSE CVE CVE-2023-52756 | known affected: 275 recommended: 514 | 2026-10-11T01:07:27+00:00 | Vulnerability · Source |
| CVE-2023-52759 | suse_vex | SUSE CVE CVE-2023-52759 | known affected: 413 known not affected: 31 recommended: 903 | 2026-10-11T01:07:25+00:00 | Vulnerability · Source |
| CVE-2023-52766 | suse_vex | SUSE CVE CVE-2023-52766 | known affected: 275 known not affected: 223 recommended: 848 | 2026-10-11T01:07:21+00:00 | Vulnerability · Source |
| CVE-2023-52769 | suse_vex | SUSE CVE CVE-2023-52769 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-11T01:07:19+00:00 | Vulnerability · Source |
| CVE-2023-52775 | suse_vex | SUSE CVE CVE-2023-52775 | known affected: 330 known not affected: 188 recommended: 671 | 2026-10-11T01:07:17+00:00 | Vulnerability · Source |
| CVE-2023-52776 | suse_vex | SUSE CVE CVE-2023-52776 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-11T01:07:15+00:00 | Vulnerability · Source |
| CVE-2023-52777 | suse_vex | SUSE CVE CVE-2023-52777 | known affected: 315 known not affected: 292 recommended: 686 | 2026-10-11T01:07:13+00:00 | Vulnerability · Source |
| CVE-2023-52781 | suse_vex | SUSE CVE CVE-2023-52781 | known affected: 380 known not affected: 38 recommended: 895 | 2026-10-11T01:07:11+00:00 | Vulnerability · Source |
| CVE-2023-52784 | suse_vex | SUSE CVE CVE-2023-52784 | known affected: 496 known not affected: 22 recommended: 755 | 2026-10-11T01:07:09+00:00 | Vulnerability · Source |
| CVE-2023-52786 | suse_vex | SUSE CVE CVE-2023-52786 | known affected: 416 known not affected: 374 recommended: 353 | 2026-10-11T01:07:07+00:00 | Vulnerability · Source |
| CVE-2023-52788 | suse_vex | SUSE CVE CVE-2023-52788 | known affected: 275 known not affected: 235 recommended: 805 | 2026-10-11T01:07:05+00:00 | Vulnerability · Source |
| CVE-2023-52789 | suse_vex | SUSE CVE CVE-2023-52789 | known affected: 275 known not affected: 164 recommended: 805 | 2026-10-11T01:07:03+00:00 | Vulnerability · Source |
| CVE-2023-52791 | suse_vex | SUSE CVE CVE-2023-52791 | known affected: 342 known not affected: 164 recommended: 825 | 2026-10-11T01:07:00+00:00 | Vulnerability · Source |
| CVE-2023-52798 | suse_vex | SUSE CVE CVE-2023-52798 | known affected: 275 known not affected: 235 recommended: 825 | 2026-10-11T01:06:57+00:00 | Vulnerability · Source |
| CVE-2023-52800 | suse_vex | SUSE CVE CVE-2023-52800 | known affected: 275 known not affected: 213 recommended: 856 | 2026-10-11T01:06:54+00:00 | Vulnerability · Source |
| CVE-2023-52801 | suse_vex | SUSE CVE CVE-2023-52801 | known affected: 394 known not affected: 354 recommended: 411 | 2026-10-11T01:06:52+00:00 | Vulnerability · Source |
| CVE-2023-52804 | suse_vex | SUSE CVE CVE-2023-52804 | known affected: 282 known not affected: 475 recommended: 805 | 2026-10-11T01:06:50+00:00 | Vulnerability · Source |
| CVE-2023-52807 | suse_vex | SUSE CVE CVE-2023-52807 | known affected: 315 known not affected: 235 recommended: 666 | 2026-10-11T01:06:48+00:00 | Vulnerability · Source |
| CVE-2023-52809 | suse_vex | SUSE CVE CVE-2023-52809 | known affected: 467 known not affected: 38 recommended: 828 | 2026-10-11T01:06:46+00:00 | Vulnerability · Source |
| CVE-2023-52811 | suse_vex | SUSE CVE CVE-2023-52811 | known affected: 447 known not affected: 36 recommended: 909 | 2026-10-11T01:06:43+00:00 | Vulnerability · Source |