VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-57075 | redhat_vex | YAML::Syck: YAML::Syck: Information disclosure via out-of-bounds read in base64 decoder | known affected: 5 | 2026-07-17T14:05:57+00:00 | Vulnerability · Source |
| CVE-2026-57077 | redhat_vex | YAML::Syck: YAML::Syck: Information disclosure via out-of-bounds read | known affected: 5 | 2026-07-17T14:05:54+00:00 | Vulnerability · Source |
| CVE-2020-9925 | suse_vex | SUSE CVE CVE-2020-9925 | known affected: 102 recommended: 1073 | 2026-07-17T14:05:54+00:00 | Vulnerability · Source |
| CVE-2026-57076 | redhat_vex | YAML-Syck: YAML::Syck: Heap use-after-free via anchor name reuse | known affected: 5 | 2026-07-17T14:05:50+00:00 | Vulnerability · Source |
| CVE-2020-11865 | suse_vex | SUSE CVE CVE-2020-11865 | recommended: 47 | 2026-07-17T14:05:17+00:00 | Vulnerability · Source |
| CVE-2020-11866 | suse_vex | SUSE CVE CVE-2020-11866 | recommended: 44 | 2026-07-17T14:05:16+00:00 | Vulnerability · Source |
| CVE-2026-13713 | redhat_vex | YAML-Syck: YAML::Syck: Denial of Service via crafted YAML document | known affected: 5 | 2026-07-17T14:05:02+00:00 | Vulnerability · Source |
| CVE-2020-12695 | suse_vex | SUSE CVE CVE-2020-12695 | recommended: 81 | 2026-07-17T14:04:53+00:00 | Vulnerability · Source |
| CVE-2020-13401 | suse_vex | SUSE CVE CVE-2020-13401 | known affected: 360 recommended: 518 | 2026-07-17T14:04:50+00:00 | Vulnerability · Source |
| CVE-2020-13543 | suse_vex | SUSE CVE CVE-2020-13543 | recommended: 938 | 2026-07-17T14:04:48+00:00 | Vulnerability · Source |
| CVE-2020-13999 | suse_vex | SUSE CVE CVE-2020-13999 | known not affected: 8 recommended: 27 | 2026-07-17T14:04:40+00:00 | Vulnerability · Source |
| CVE-2020-15169 | suse_vex | SUSE CVE CVE-2020-15169 | known affected: 396 known not affected: 45 recommended: 148 | 2026-07-17T14:04:25+00:00 | Vulnerability · Source |
| CVE-2020-35654 | suse_vex | SUSE CVE CVE-2020-35654 | known not affected: 55 recommended: 39 | 2026-07-17T14:02:42+00:00 | Vulnerability · Source |
| CVE-2021-3624 | suse_vex | SUSE CVE CVE-2021-3624 | recommended: 26 | 2026-07-17T14:02:09+00:00 | Vulnerability · Source |
| CVE-2021-21707 | suse_vex | SUSE CVE CVE-2021-21707 | recommended: 4958 | 2026-07-17T14:01:25+00:00 | Vulnerability · Source |
| CVE-2021-23953 | suse_vex | SUSE CVE CVE-2021-23953 | recommended: 471 | 2026-07-17T14:01:05+00:00 | Vulnerability · Source |
| CVE-2021-27921 | suse_vex | SUSE CVE CVE-2021-27921 | known affected: 2 known not affected: 51 recommended: 42 | 2026-07-17T14:00:36+00:00 | Vulnerability · Source |
| CVE-2021-29951 | suse_vex | SUSE CVE CVE-2021-29951 | known affected: 57 known not affected: 1 recommended: 411 | 2026-07-17T14:00:30+00:00 | Vulnerability · Source |
| CVE-2021-31542 | suse_vex | SUSE CVE CVE-2021-31542 | recommended: 274 | 2026-07-17T14:00:07+00:00 | Vulnerability · Source |
| CVE-2021-32142 | suse_vex | SUSE CVE CVE-2021-32142 | recommended: 88 | 2026-07-17T13:59:58+00:00 | Vulnerability · Source |
| CVE-2021-32715 | suse_vex | SUSE CVE CVE-2021-32715 | known not affected: 374 recommended: 18 | 2026-07-17T13:59:55+00:00 | Vulnerability · Source |
| CVE-2021-38509 | suse_vex | SUSE CVE CVE-2021-38509 | known affected: 1 recommended: 404 | 2026-07-17T13:59:19+00:00 | Vulnerability · Source |
| CVE-2021-39259 | suse_vex | SUSE CVE CVE-2021-39259 | recommended: 144 | 2026-07-17T13:59:12+00:00 | Vulnerability · Source |
| CVE-2021-40346 | suse_vex | SUSE CVE CVE-2021-40346 | known not affected: 11 recommended: 13 | 2026-07-17T13:59:04+00:00 | Vulnerability · Source |
| CVE-2021-41116 | suse_vex | SUSE CVE CVE-2021-41116 | recommended: 6 | 2026-07-17T13:58:57+00:00 | Vulnerability · Source |
| CVE-2021-43310 | suse_vex | SUSE CVE CVE-2021-43310 | known not affected: 72 recommended: 201 | 2026-07-17T13:58:37+00:00 | Vulnerability · Source |
| CVE-2021-43860 | suse_vex | SUSE CVE CVE-2021-43860 | known not affected: 48 recommended: 338 | 2026-07-17T13:58:32+00:00 | Vulnerability · Source |
| CVE-2021-45115 | suse_vex | SUSE CVE CVE-2021-45115 | recommended: 22 | 2026-07-17T13:58:26+00:00 | Vulnerability · Source |
| CVE-2021-45958 | suse_vex | SUSE CVE CVE-2021-45958 | known affected: 32 recommended: 41 | 2026-07-17T13:58:20+00:00 | Vulnerability · Source |
| CVE-2021-46141 | suse_vex | SUSE CVE CVE-2021-46141 | recommended: 13 | 2026-07-17T13:58:17+00:00 | Vulnerability · Source |
| CVE-2022-0585 | suse_vex | SUSE CVE CVE-2022-0585 | known not affected: 101 recommended: 339 | 2026-07-17T13:57:34+00:00 | Vulnerability · Source |
| CVE-2022-0711 | suse_vex | SUSE CVE CVE-2022-0711 | known not affected: 15 recommended: 10 | 2026-07-17T13:57:28+00:00 | Vulnerability · Source |
| CVE-2022-1996 | suse_vex | SUSE CVE CVE-2022-1996 | known affected: 414 known not affected: 330 recommended: 481 | 2026-07-17T13:56:47+00:00 | Vulnerability · Source |
| CVE-2022-2990 | suse_vex | SUSE CVE CVE-2022-2990 | recommended: 118 | 2026-07-17T13:56:19+00:00 | Vulnerability · Source |
| CVE-2022-3598 | suse_vex | SUSE CVE CVE-2022-3598 | known affected: 418 known not affected: 1 recommended: 231 | 2026-07-17T13:56:02+00:00 | Vulnerability · Source |
| CVE-2022-21248 | suse_vex | SUSE CVE CVE-2022-21248 | known affected: 406 known not affected: 32 recommended: 1020 | 2026-07-17T13:55:45+00:00 | Vulnerability · Source |
| CVE-2022-22589 | suse_vex | SUSE CVE CVE-2022-22589 | known not affected: 9 recommended: 912 | 2026-07-17T13:55:30+00:00 | Vulnerability · Source |
| CVE-2022-22818 | suse_vex | SUSE CVE CVE-2022-22818 | recommended: 83 | 2026-07-17T13:55:14+00:00 | Vulnerability · Source |
| CVE-2022-23524 | suse_vex | SUSE CVE CVE-2022-23524 | known affected: 406 recommended: 96 | 2026-07-17T13:55:05+00:00 | Vulnerability · Source |
| CVE-2022-23948 | suse_vex | SUSE CVE CVE-2022-23948 | known not affected: 72 recommended: 201 | 2026-07-17T13:55:01+00:00 | Vulnerability · Source |
| CVE-2022-24303 | suse_vex | SUSE CVE CVE-2022-24303 | known not affected: 5 recommended: 26 | 2026-07-17T13:54:55+00:00 | Vulnerability · Source |
| CVE-2022-24805 | suse_vex | SUSE CVE CVE-2022-24805 | known affected: 394 known not affected: 169 recommended: 249 | 2026-07-17T13:54:50+00:00 | Vulnerability · Source |
| CVE-2022-25647 | suse_vex | SUSE CVE CVE-2022-25647 | known affected: 394 recommended: 58 | 2026-07-17T13:54:40+00:00 | Vulnerability · Source |
| CVE-2022-26129 | suse_vex | SUSE CVE CVE-2022-26129 | recommended: 244 | 2026-07-17T13:54:39+00:00 | Vulnerability · Source |
| CVE-2022-27382 | suse_vex | SUSE CVE CVE-2022-27382 | known not affected: 190 recommended: 365 | 2026-07-17T13:54:31+00:00 | Vulnerability · Source |
| CVE-2022-28346 | suse_vex | SUSE CVE CVE-2022-28346 | recommended: 110 | 2026-07-17T13:54:13+00:00 | Vulnerability · Source |
| CVE-2022-30698 | suse_vex | SUSE CVE CVE-2022-30698 | known affected: 56 recommended: 142 | 2026-07-17T13:53:55+00:00 | Vulnerability · Source |
| CVE-2022-30783 | suse_vex | SUSE CVE CVE-2022-30783 | recommended: 129 | 2026-07-17T13:53:54+00:00 | Vulnerability · Source |
| CVE-2022-30789 | suse_vex | SUSE CVE CVE-2022-30789 | recommended: 247 | 2026-07-17T13:53:52+00:00 | Vulnerability · Source |
| CVE-2022-31250 | suse_vex | SUSE CVE CVE-2022-31250 | recommended: 225 | 2026-07-17T13:53:49+00:00 | Vulnerability · Source |