VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
296126 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-27830 | suse_vex | SUSE CVE CVE-2026-27830 | recommended: 9 | 2026-07-01T03:32:51+00:00 | Vulnerability · Source |
| CVE-2026-28364 | suse_vex | SUSE CVE CVE-2026-28364 | known affected: 32 recommended: 98 | 2026-07-01T03:32:39+00:00 | Vulnerability · Source |
| CVE-2026-28802 | suse_vex | SUSE CVE CVE-2026-28802 | known not affected: 18 | 2026-07-01T03:32:30+00:00 | Vulnerability · Source |
| CVE-2026-31892 | suse_vex | SUSE CVE CVE-2026-31892 | No product status | 2026-07-01T03:30:01+00:00 | Vulnerability · Source |
| CVE-2026-32305 | suse_vex | SUSE CVE CVE-2026-32305 | recommended: 2 | 2026-07-01T03:29:51+00:00 | Vulnerability · Source |
| CVE-2026-32640 | suse_vex | SUSE CVE CVE-2026-32640 | recommended: 6 | 2026-07-01T03:29:49+00:00 | Vulnerability · Source |
| CVE-2026-32748 | suse_vex | SUSE CVE CVE-2026-32748 | known affected: 34 recommended: 5 | 2026-07-01T03:29:44+00:00 | Vulnerability · Source |
| CVE-2026-33150 | suse_vex | SUSE CVE CVE-2026-33150 | known not affected: 248 | 2026-07-01T03:29:33+00:00 | Vulnerability · Source |
| CVE-2026-33231 | suse_vex | SUSE CVE CVE-2026-33231 | recommended: 1 | 2026-07-01T03:29:26+00:00 | Vulnerability · Source |
| CVE-2026-33487 | suse_vex | SUSE CVE CVE-2026-33487 | recommended: 1 | 2026-07-01T03:29:23+00:00 | Vulnerability · Source |
| CVE-2026-33526 | suse_vex | SUSE CVE CVE-2026-33526 | known affected: 34 recommended: 5 | 2026-07-01T03:29:20+00:00 | Vulnerability · Source |
| CVE-2026-34580 | suse_vex | SUSE CVE CVE-2026-34580 | known not affected: 5 | 2026-07-01T03:28:50+00:00 | Vulnerability · Source |
| CVE-2026-34601 | suse_vex | SUSE CVE CVE-2026-34601 | known affected: 69 known not affected: 12 recommended: 5 | 2026-07-01T03:28:45+00:00 | Vulnerability · Source |
| CVE-2026-34734 | suse_vex | SUSE CVE CVE-2026-34734 | known affected: 708 | 2026-07-01T03:28:44+00:00 | Vulnerability · Source |
| CVE-2026-35093 | suse_vex | SUSE CVE CVE-2026-35093 | known not affected: 129 recommended: 5 | 2026-07-01T03:28:35+00:00 | Vulnerability · Source |
| CVE-2026-41053 | suse_vex | SUSE CVE CVE-2026-41053 | No product status | 2026-07-01T03:27:43+00:00 | Vulnerability · Source |
| CVE-2026-42027 | suse_vex | SUSE CVE CVE-2026-42027 | No product status | 2026-07-01T03:27:11+00:00 | Vulnerability · Source |
| CVE-2026-42573 | suse_vex | SUSE CVE CVE-2026-42573 | known affected: 75 | 2026-07-01T03:26:44+00:00 | Vulnerability · Source |
| CVE-2026-44727 | suse_vex | SUSE CVE CVE-2026-44727 | recommended: 6 | 2026-07-01T03:23:58+00:00 | Vulnerability · Source |
| CVE-2026-44947 | suse_vex | SUSE CVE CVE-2026-44947 | No product status | 2026-07-01T03:23:48+00:00 | Vulnerability · Source |
| CVE-2026-46625 | suse_vex | SUSE CVE CVE-2026-46625 | No product status | 2026-07-01T03:21:10+00:00 | Vulnerability · Source |
| CVE-2026-53115 | suse_vex | SUSE CVE CVE-2026-53115 | known affected: 214 known not affected: 77 | 2026-07-01T03:18:56+00:00 | Vulnerability · Source |
| CVE-2026-53116 | suse_vex | SUSE CVE CVE-2026-53116 | known affected: 226 known not affected: 65 | 2026-07-01T03:18:54+00:00 | Vulnerability · Source |
| CVE-2026-53117 | suse_vex | SUSE CVE CVE-2026-53117 | known affected: 226 known not affected: 65 | 2026-07-01T03:18:52+00:00 | Vulnerability · Source |
| CVE-2026-53119 | suse_vex | SUSE CVE CVE-2026-53119 | known affected: 15 known not affected: 276 | 2026-07-01T03:18:51+00:00 | Vulnerability · Source |
| CVE-2026-53120 | suse_vex | SUSE CVE CVE-2026-53120 | known affected: 287 known not affected: 4 | 2026-07-01T03:18:49+00:00 | Vulnerability · Source |
| CVE-2026-53127 | suse_vex | SUSE CVE CVE-2026-53127 | known not affected: 291 | 2026-07-01T03:18:43+00:00 | Vulnerability · Source |
| CVE-2026-53128 | suse_vex | SUSE CVE CVE-2026-53128 | known affected: 285 known not affected: 6 | 2026-07-01T03:18:41+00:00 | Vulnerability · Source |
| CVE-2026-53155 | suse_vex | SUSE CVE CVE-2026-53155 | known not affected: 291 | 2026-07-01T03:18:08+00:00 | Vulnerability · Source |
| CVE-2026-53206 | suse_vex | SUSE CVE CVE-2026-53206 | known not affected: 291 | 2026-07-01T03:17:23+00:00 | Vulnerability · Source |
| CVE-2026-53231 | suse_vex | SUSE CVE CVE-2026-53231 | known not affected: 291 | 2026-07-01T03:17:07+00:00 | Vulnerability · Source |
| CVE-2026-53261 | suse_vex | SUSE CVE CVE-2026-53261 | known affected: 112 known not affected: 179 | 2026-07-01T03:16:47+00:00 | Vulnerability · Source |
| CVE-2026-53282 | suse_vex | SUSE CVE CVE-2026-53282 | known not affected: 291 | 2026-07-01T03:16:31+00:00 | Vulnerability · Source |
| CVE-2026-53288 | suse_vex | SUSE CVE CVE-2026-53288 | known not affected: 291 | 2026-07-01T03:16:27+00:00 | Vulnerability · Source |
| CVE-2026-53294 | suse_vex | SUSE CVE CVE-2026-53294 | known affected: 287 known not affected: 4 | 2026-07-01T03:16:20+00:00 | Vulnerability · Source |
| CVE-2026-53299 | suse_vex | SUSE CVE CVE-2026-53299 | known not affected: 291 | 2026-07-01T03:16:18+00:00 | Vulnerability · Source |
| CVE-2026-53302 | suse_vex | SUSE CVE CVE-2026-53302 | known not affected: 291 | 2026-07-01T03:16:16+00:00 | Vulnerability · Source |
| CVE-2026-53305 | suse_vex | SUSE CVE CVE-2026-53305 | known not affected: 291 | 2026-07-01T03:16:15+00:00 | Vulnerability · Source |
| CVE-2026-53307 | suse_vex | SUSE CVE CVE-2026-53307 | known not affected: 291 | 2026-07-01T03:16:11+00:00 | Vulnerability · Source |
| CVE-2026-53311 | suse_vex | SUSE CVE CVE-2026-53311 | known not affected: 291 | 2026-07-01T03:16:05+00:00 | Vulnerability · Source |
| CVE-2026-53316 | suse_vex | SUSE CVE CVE-2026-53316 | known not affected: 291 | 2026-07-01T03:16:00+00:00 | Vulnerability · Source |
| CVE-2026-53319 | suse_vex | SUSE CVE CVE-2026-53319 | known not affected: 291 | 2026-07-01T03:15:56+00:00 | Vulnerability · Source |
| CVE-2026-54250 | suse_vex | SUSE CVE CVE-2026-54250 | No product status | 2026-07-01T03:15:31+00:00 | Vulnerability · Source |
| CVE-2026-56017 | suse_vex | SUSE CVE CVE-2026-56017 | recommended: 1 | 2026-07-01T03:15:04+00:00 | Vulnerability · Source |
| CVE-2026-56018 | suse_vex | SUSE CVE CVE-2026-56018 | recommended: 1 | 2026-07-01T03:15:02+00:00 | Vulnerability · Source |
| CVE-2026-56766 | suse_vex | SUSE CVE CVE-2026-56766 | recommended: 1 | 2026-07-01T03:14:56+00:00 | Vulnerability · Source |
| CVE-2026-57947 | suse_vex | SUSE CVE CVE-2026-57947 | No product status | 2026-07-01T03:14:52+00:00 | Vulnerability · Source |
| CVE-2026-57948 | suse_vex | SUSE CVE CVE-2026-57948 | No product status | 2026-07-01T03:14:51+00:00 | Vulnerability · Source |
| CVE-2024-0760 | redhat_vex | bind: bind9: A flood of DNS messages over TCP may make the server unstable | known not affected: 78 | 2026-07-01T03:02:45+00:00 | Vulnerability · Source |
| CVE-2026-43828 | redhat_vex | apache-shiro: Apache Shiro: Information disclosure via insecure cookie handling | known affected: 2 | 2026-07-01T02:22:24+00:00 | Vulnerability · Source |