VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
297693 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-31488 | microsoft_vex | drm/amd/display: Do not skip unrelated mode changes in DSC validation | fixed: 1 known affected: 6 | 2026-06-23T14:43:47+00:00 | Vulnerability · Source |
| CVE-2026-40930 | microsoft_vex | LIBPNG: Chunk smuggling in push-mode APNG parser via unconsumed chunk body | known not affected: 3 | 2026-06-23T14:43:39+00:00 | Vulnerability · Source |
| CVE-2026-42497 | microsoft_vex | Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extraction directory | fixed: 1 known affected: 1 | 2026-06-23T14:42:42+00:00 | Vulnerability · Source |
| CVE-2026-23272 | microsoft_vex | netfilter: nf_tables: unconditionally bump set->nelems before insertion | fixed: 1 known affected: 7 | 2026-06-23T14:42:13+00:00 | Vulnerability · Source |
| CVE-2024-56647 | microsoft_vex | net: Fix icmp host relookup triggering ip_rt_bug | fixed: 1 known affected: 1 under investigation: 17 | 2026-06-23T14:40:36+00:00 | Vulnerability · Source |
| CVE-2023-27043 | microsoft_vex | The email module of Python through 3.11.3 incorrectly parses e-mail addresses that contain a special character. The wrong portion of an RFC2822 header is identified as the value of the addr-spec. In some applications, an attacker can bypass a protection mechanism in which application access is granted only after verifying receipt of e-mail to a specific domain (e.g., only @company.example.com addresses may be used for signup). This occurs in email/_parseaddr.py in recent versions of Python. | fixed: 3 known affected: 3 known not affected: 1 under investigation: 7 | 2026-06-23T14:40:24+00:00 | Vulnerability · Source |
| CVE-2015-5281 | suse_vex | SUSE CVE CVE-2015-5281 | recommended: 4 | 2026-06-23T02:43:56+00:00 | Vulnerability · Source |
| CVE-2018-17093 | suse_vex | SUSE CVE CVE-2018-17093 | recommended: 3 | 2026-06-23T02:42:59+00:00 | Vulnerability · Source |
| CVE-2021-4249 | suse_vex | SUSE CVE CVE-2021-4249 | recommended: 4 | 2026-06-23T02:41:53+00:00 | Vulnerability · Source |
| CVE-2022-0157 | suse_vex | SUSE CVE CVE-2022-0157 | recommended: 1 | 2026-06-23T02:41:28+00:00 | Vulnerability · Source |
| CVE-2022-0197 | suse_vex | SUSE CVE CVE-2022-0197 | No product status | 2026-06-23T02:41:27+00:00 | Vulnerability · Source |
| CVE-2026-2704 | suse_vex | SUSE CVE CVE-2026-2704 | recommended: 5 | 2026-06-23T02:31:37+00:00 | Vulnerability · Source |
| CVE-2026-4660 | suse_vex | SUSE CVE CVE-2026-4660 | No product status | 2026-06-23T02:31:18+00:00 | Vulnerability · Source |
| CVE-2026-12437 | suse_vex | SUSE CVE CVE-2026-12437 | recommended: 4 | 2026-06-23T02:30:39+00:00 | Vulnerability · Source |
| CVE-2026-12438 | suse_vex | SUSE CVE CVE-2026-12438 | recommended: 4 | 2026-06-23T02:30:38+00:00 | Vulnerability · Source |
| CVE-2026-12439 | suse_vex | SUSE CVE CVE-2026-12439 | recommended: 4 | 2026-06-23T02:30:37+00:00 | Vulnerability · Source |
| CVE-2026-12440 | suse_vex | SUSE CVE CVE-2026-12440 | recommended: 4 | 2026-06-23T02:30:36+00:00 | Vulnerability · Source |
| CVE-2026-12441 | suse_vex | SUSE CVE CVE-2026-12441 | recommended: 4 | 2026-06-23T02:30:35+00:00 | Vulnerability · Source |
| CVE-2026-12442 | suse_vex | SUSE CVE CVE-2026-12442 | recommended: 4 | 2026-06-23T02:30:33+00:00 | Vulnerability · Source |
| CVE-2026-12443 | suse_vex | SUSE CVE CVE-2026-12443 | recommended: 4 | 2026-06-23T02:30:32+00:00 | Vulnerability · Source |
| CVE-2026-12444 | suse_vex | SUSE CVE CVE-2026-12444 | recommended: 4 | 2026-06-23T02:30:31+00:00 | Vulnerability · Source |
| CVE-2026-12445 | suse_vex | SUSE CVE CVE-2026-12445 | recommended: 4 | 2026-06-23T02:30:29+00:00 | Vulnerability · Source |
| CVE-2026-12446 | suse_vex | SUSE CVE CVE-2026-12446 | recommended: 4 | 2026-06-23T02:30:27+00:00 | Vulnerability · Source |
| CVE-2026-12447 | suse_vex | SUSE CVE CVE-2026-12447 | recommended: 4 | 2026-06-23T02:30:26+00:00 | Vulnerability · Source |
| CVE-2026-12448 | suse_vex | SUSE CVE CVE-2026-12448 | recommended: 4 | 2026-06-23T02:30:25+00:00 | Vulnerability · Source |
| CVE-2026-12449 | suse_vex | SUSE CVE CVE-2026-12449 | recommended: 4 | 2026-06-23T02:30:24+00:00 | Vulnerability · Source |
| CVE-2026-12450 | suse_vex | SUSE CVE CVE-2026-12450 | recommended: 4 | 2026-06-23T02:30:23+00:00 | Vulnerability · Source |
| CVE-2026-12451 | suse_vex | SUSE CVE CVE-2026-12451 | recommended: 4 | 2026-06-23T02:30:21+00:00 | Vulnerability · Source |
| CVE-2026-12452 | suse_vex | SUSE CVE CVE-2026-12452 | recommended: 4 | 2026-06-23T02:30:20+00:00 | Vulnerability · Source |
| CVE-2026-12453 | suse_vex | SUSE CVE CVE-2026-12453 | recommended: 4 | 2026-06-23T02:30:18+00:00 | Vulnerability · Source |
| CVE-2026-12454 | suse_vex | SUSE CVE CVE-2026-12454 | recommended: 4 | 2026-06-23T02:30:17+00:00 | Vulnerability · Source |
| CVE-2026-12455 | suse_vex | SUSE CVE CVE-2026-12455 | recommended: 4 | 2026-06-23T02:30:16+00:00 | Vulnerability · Source |
| CVE-2026-12456 | suse_vex | SUSE CVE CVE-2026-12456 | recommended: 4 | 2026-06-23T02:30:15+00:00 | Vulnerability · Source |
| CVE-2026-12457 | suse_vex | SUSE CVE CVE-2026-12457 | recommended: 4 | 2026-06-23T02:30:13+00:00 | Vulnerability · Source |
| CVE-2026-12458 | suse_vex | SUSE CVE CVE-2026-12458 | recommended: 4 | 2026-06-23T02:30:12+00:00 | Vulnerability · Source |
| CVE-2026-12459 | suse_vex | SUSE CVE CVE-2026-12459 | recommended: 4 | 2026-06-23T02:30:10+00:00 | Vulnerability · Source |
| CVE-2026-12460 | suse_vex | SUSE CVE CVE-2026-12460 | recommended: 4 | 2026-06-23T02:30:09+00:00 | Vulnerability · Source |
| CVE-2026-12461 | suse_vex | SUSE CVE CVE-2026-12461 | recommended: 4 | 2026-06-23T02:30:08+00:00 | Vulnerability · Source |
| CVE-2026-12462 | suse_vex | SUSE CVE CVE-2026-12462 | recommended: 4 | 2026-06-23T02:30:06+00:00 | Vulnerability · Source |
| CVE-2026-12463 | suse_vex | SUSE CVE CVE-2026-12463 | recommended: 4 | 2026-06-23T02:30:05+00:00 | Vulnerability · Source |
| CVE-2026-12464 | suse_vex | SUSE CVE CVE-2026-12464 | recommended: 4 | 2026-06-23T02:30:04+00:00 | Vulnerability · Source |
| CVE-2026-12465 | suse_vex | SUSE CVE CVE-2026-12465 | recommended: 4 | 2026-06-23T02:30:03+00:00 | Vulnerability · Source |
| CVE-2026-12466 | suse_vex | SUSE CVE CVE-2026-12466 | recommended: 4 | 2026-06-23T02:30:01+00:00 | Vulnerability · Source |
| CVE-2026-12467 | suse_vex | SUSE CVE CVE-2026-12467 | recommended: 4 | 2026-06-23T02:30:00+00:00 | Vulnerability · Source |
| CVE-2026-12468 | suse_vex | SUSE CVE CVE-2026-12468 | recommended: 4 | 2026-06-23T02:29:58+00:00 | Vulnerability · Source |
| CVE-2026-12469 | suse_vex | SUSE CVE CVE-2026-12469 | recommended: 4 | 2026-06-23T02:29:57+00:00 | Vulnerability · Source |
| CVE-2026-30784 | suse_vex | SUSE CVE CVE-2026-30784 | No product status | 2026-06-23T02:27:41+00:00 | Vulnerability · Source |
| CVE-2026-30790 | suse_vex | SUSE CVE CVE-2026-30790 | No product status | 2026-06-23T02:27:40+00:00 | Vulnerability · Source |
| CVE-2026-33558 | suse_vex | SUSE CVE CVE-2026-33558 | No product status | 2026-06-23T02:26:02+00:00 | Vulnerability · Source |
| CVE-2026-41045 | suse_vex | SUSE CVE CVE-2026-41045 | No product status | 2026-06-23T02:24:56+00:00 | Vulnerability · Source |