VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
304374 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-74694 | suse_vex | SUSE CVE CVE-2026-74694 | known affected: 621 known not affected: 93 recommended: 107 | 2026-10-03T00:23:40+00:00 | Vulnerability · Source |
| CVE-2026-74695 | suse_vex | SUSE CVE CVE-2026-74695 | known affected: 570 known not affected: 93 recommended: 359 | 2026-10-03T00:23:38+00:00 | Vulnerability · Source |
| CVE-2026-74705 | suse_vex | SUSE CVE CVE-2026-74705 | known affected: 693 known not affected: 6 recommended: 168 | 2026-10-03T00:23:35+00:00 | Vulnerability · Source |
| CVE-2026-74712 | suse_vex | SUSE CVE CVE-2026-74712 | known affected: 447 known not affected: 286 recommended: 228 | 2026-10-03T00:23:32+00:00 | Vulnerability · Source |
| CVE-2026-74717 | suse_vex | SUSE CVE CVE-2026-74717 | known affected: 623 known not affected: 93 recommended: 252 | 2026-10-03T00:23:30+00:00 | Vulnerability · Source |
| CVE-2026-74719 | suse_vex | SUSE CVE CVE-2026-74719 | known affected: 242 known not affected: 117 recommended: 145 | 2026-10-03T00:23:27+00:00 | Vulnerability · Source |
| CVE-2026-74722 | suse_vex | SUSE CVE CVE-2026-74722 | known affected: 477 known not affected: 239 recommended: 252 | 2026-10-03T00:23:25+00:00 | Vulnerability · Source |
| CVE-2026-74723 | suse_vex | SUSE CVE CVE-2026-74723 | known affected: 359 recommended: 145 | 2026-10-03T00:23:23+00:00 | Vulnerability · Source |
| CVE-2026-74730 | suse_vex | SUSE CVE CVE-2026-74730 | known affected: 355 known not affected: 4 recommended: 145 | 2026-10-03T00:23:19+00:00 | Vulnerability · Source |
| CVE-2026-74737 | suse_vex | SUSE CVE CVE-2026-74737 | known affected: 212 known not affected: 143 recommended: 145 | 2026-10-03T00:23:17+00:00 | Vulnerability · Source |
| CVE-2026-74743 | suse_vex | SUSE CVE CVE-2026-74743 | known affected: 564 known not affected: 89 recommended: 241 | 2026-10-03T00:23:14+00:00 | Vulnerability · Source |
| CVE-2026-74744 | suse_vex | SUSE CVE CVE-2026-74744 | known affected: 349 known not affected: 6 recommended: 145 | 2026-10-03T00:23:11+00:00 | Vulnerability · Source |
| CVE-2026-75032 | suse_vex | SUSE CVE CVE-2026-75032 | known affected: 188 | 2026-10-03T00:23:08+00:00 | Vulnerability · Source |
| CVE-2026-75805 | suse_vex | SUSE CVE CVE-2026-75805 | known affected: 49 known not affected: 391 recommended: 65 | 2026-10-03T00:23:04+00:00 | Vulnerability · Source |
| CVE-2026-75806 | suse_vex | SUSE CVE CVE-2026-75806 | known affected: 279 known not affected: 261 recommended: 65 | 2026-10-03T00:23:02+00:00 | Vulnerability · Source |
| CVE-2026-76879 | suse_vex | SUSE CVE CVE-2026-76879 | known affected: 220 recommended: 30 | 2026-10-03T00:22:59+00:00 | Vulnerability · Source |
| CVE-2026-76880 | suse_vex | SUSE CVE CVE-2026-76880 | known affected: 220 recommended: 30 | 2026-10-03T00:22:56+00:00 | Vulnerability · Source |
| CVE-2026-76881 | suse_vex | SUSE CVE CVE-2026-76881 | known affected: 220 recommended: 30 | 2026-10-03T00:22:53+00:00 | Vulnerability · Source |
| CVE-2026-76882 | suse_vex | SUSE CVE CVE-2026-76882 | known affected: 220 recommended: 30 | 2026-10-03T00:22:51+00:00 | Vulnerability · Source |
| CVE-2026-76883 | suse_vex | SUSE CVE CVE-2026-76883 | known affected: 220 recommended: 30 | 2026-10-03T00:22:48+00:00 | Vulnerability · Source |
| CVE-2026-76884 | suse_vex | SUSE CVE CVE-2026-76884 | known affected: 220 recommended: 30 | 2026-10-03T00:22:45+00:00 | Vulnerability · Source |
| CVE-2026-76885 | suse_vex | SUSE CVE CVE-2026-76885 | known affected: 220 recommended: 30 | 2026-10-03T00:22:43+00:00 | Vulnerability · Source |
| CVE-2026-76886 | suse_vex | SUSE CVE CVE-2026-76886 | known affected: 220 recommended: 30 | 2026-10-03T00:22:41+00:00 | Vulnerability · Source |
| CVE-2026-76887 | suse_vex | SUSE CVE CVE-2026-76887 | known affected: 220 recommended: 30 | 2026-10-03T00:22:38+00:00 | Vulnerability · Source |
| CVE-2026-76888 | suse_vex | SUSE CVE CVE-2026-76888 | known affected: 220 recommended: 30 | 2026-10-03T00:22:35+00:00 | Vulnerability · Source |
| CVE-2026-76889 | suse_vex | SUSE CVE CVE-2026-76889 | known affected: 220 recommended: 30 | 2026-10-03T00:22:32+00:00 | Vulnerability · Source |
| CVE-2026-76890 | suse_vex | SUSE CVE CVE-2026-76890 | known affected: 220 recommended: 30 | 2026-10-03T00:22:30+00:00 | Vulnerability · Source |
| CVE-2026-76891 | suse_vex | SUSE CVE CVE-2026-76891 | known affected: 220 recommended: 30 | 2026-10-03T00:22:27+00:00 | Vulnerability · Source |
| CVE-2026-76917 | suse_vex | SUSE CVE CVE-2026-76917 | known affected: 220 recommended: 30 | 2026-10-03T00:22:24+00:00 | Vulnerability · Source |
| CVE-2026-76918 | suse_vex | SUSE CVE CVE-2026-76918 | known affected: 220 recommended: 30 | 2026-10-03T00:22:22+00:00 | Vulnerability · Source |
| CVE-2026-76919 | suse_vex | SUSE CVE CVE-2026-76919 | known affected: 220 recommended: 30 | 2026-10-03T00:22:20+00:00 | Vulnerability · Source |
| CVE-2026-76920 | suse_vex | SUSE CVE CVE-2026-76920 | known affected: 220 recommended: 30 | 2026-10-03T00:22:18+00:00 | Vulnerability · Source |
| CVE-2026-76921 | suse_vex | SUSE CVE CVE-2026-76921 | known affected: 220 recommended: 30 | 2026-10-03T00:22:16+00:00 | Vulnerability · Source |
| CVE-2026-76922 | suse_vex | SUSE CVE CVE-2026-76922 | known affected: 220 recommended: 30 | 2026-10-03T00:22:14+00:00 | Vulnerability · Source |
| CVE-2026-76923 | suse_vex | SUSE CVE CVE-2026-76923 | known affected: 220 recommended: 30 | 2026-10-03T00:22:12+00:00 | Vulnerability · Source |
| CVE-2026-76924 | suse_vex | SUSE CVE CVE-2026-76924 | known affected: 220 recommended: 30 | 2026-10-03T00:22:10+00:00 | Vulnerability · Source |
| CVE-2026-76926 | suse_vex | SUSE CVE CVE-2026-76926 | known affected: 220 recommended: 30 | 2026-10-03T00:22:07+00:00 | Vulnerability · Source |
| CVE-2026-76927 | suse_vex | SUSE CVE CVE-2026-76927 | known affected: 220 recommended: 30 | 2026-10-03T00:22:05+00:00 | Vulnerability · Source |
| CVE-2026-76928 | suse_vex | SUSE CVE CVE-2026-76928 | known affected: 220 recommended: 30 | 2026-10-03T00:22:03+00:00 | Vulnerability · Source |
| CVE-2026-76929 | suse_vex | SUSE CVE CVE-2026-76929 | known affected: 220 recommended: 30 | 2026-10-03T00:22:00+00:00 | Vulnerability · Source |
| CVE-2026-77696 | suse_vex | SUSE CVE CVE-2026-77696 | known affected: 279 known not affected: 261 recommended: 65 | 2026-10-03T00:21:56+00:00 | Vulnerability · Source |
| CVE-2026-80529 | suse_vex | SUSE CVE CVE-2026-80529 | known affected: 473 known not affected: 239 recommended: 252 | 2026-10-03T00:21:29+00:00 | Vulnerability · Source |
| CVE-2026-80530 | suse_vex | SUSE CVE CVE-2026-80530 | known affected: 31 known not affected: 324 recommended: 145 | 2026-10-03T00:21:26+00:00 | Vulnerability · Source |
| CVE-2026-80531 | suse_vex | SUSE CVE CVE-2026-80531 | known affected: 31 known not affected: 324 recommended: 145 | 2026-10-03T00:21:24+00:00 | Vulnerability · Source |
| CVE-2026-80533 | suse_vex | SUSE CVE CVE-2026-80533 | known affected: 31 known not affected: 324 recommended: 145 | 2026-10-03T00:21:22+00:00 | Vulnerability · Source |
| CVE-2026-80534 | suse_vex | SUSE CVE CVE-2026-80534 | known affected: 652 known not affected: 6 recommended: 275 | 2026-10-03T00:21:19+00:00 | Vulnerability · Source |
| CVE-2026-80535 | suse_vex | SUSE CVE CVE-2026-80535 | known affected: 31 known not affected: 324 recommended: 145 | 2026-10-03T00:21:17+00:00 | Vulnerability · Source |
| CVE-2026-80557 | suse_vex | SUSE CVE CVE-2026-80557 | known affected: 351 known not affected: 4 recommended: 145 | 2026-10-03T00:21:15+00:00 | Vulnerability · Source |
| CVE-2026-80558 | suse_vex | SUSE CVE CVE-2026-80558 | known affected: 351 known not affected: 4 recommended: 145 | 2026-10-03T00:21:13+00:00 | Vulnerability · Source |
| CVE-2026-80561 | suse_vex | SUSE CVE CVE-2026-80561 | known affected: 351 known not affected: 4 recommended: 145 | 2026-10-03T00:21:11+00:00 | Vulnerability · Source |