VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
78834 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-87512 | redhat_vex | chromium-browser: angle: Chromium-browser: Arbitrary code execution via use-after-free vulnerability in ANGLE | known affected: 22 known not affected: 23 | 2026-10-04T19:21:53+00:00 | Vulnerability · Source |
| CVE-2026-79230 | redhat_vex | chromium-browser: angle: ANGLE in Google Chrome: Arbitrary code execution via improper input validation | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:21:53+00:00 | Vulnerability · Source |
| CVE-2026-5868 | redhat_vex | chromium-browser: angle: Heap buffer overflow in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:16:48+00:00 | Vulnerability · Source |
| CVE-2026-79019 | redhat_vex | chromium-browser: angle: ANGLE: Arbitrary code execution via a crafted HTML page | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:16:48+00:00 | Vulnerability · Source |
| CVE-2026-17785 | redhat_vex | chromium-browser: angle: chromium-browser: Uninitialized Use in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:16:48+00:00 | Vulnerability · Source |
| CVE-2026-11123 | redhat_vex | chromium-browser: angle: Uninitialized Use in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:11:36+00:00 | Vulnerability · Source |
| CVE-2026-17682 | redhat_vex | chromium-browser: angle: chromium-browser: Integer overflow in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:11:36+00:00 | Vulnerability · Source |
| CVE-2026-14412 | redhat_vex | chromium-browser: angle: chromium-browser: Insufficient validation of untrusted input in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:11:36+00:00 | Vulnerability · Source |
| CVE-2026-14152 | redhat_vex | chromium-browser: angle: Out of bounds write in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:11:36+00:00 | Vulnerability · Source |
| CVE-2026-11043 | redhat_vex | chromium-browser: angle: Out of bounds write in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:11:36+00:00 | Vulnerability · Source |
| CVE-2026-10889 | redhat_vex | chromium-browser: angle: Out of bounds read in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:06:42+00:00 | Vulnerability · Source |
| CVE-2026-9969 | redhat_vex | chromium-browser: angle: Insufficient validation of untrusted input in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:06:42+00:00 | Vulnerability · Source |
| CVE-2026-9916 | redhat_vex | chromium-browser: angle: Out of bounds write in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T19:01:48+00:00 | Vulnerability · Source |
| CVE-2026-7901 | redhat_vex | chromium-browser: angle: Use after free in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:51:47+00:00 | Vulnerability · Source |
| CVE-2026-87500 | redhat_vex | chromium-browser: angle: ANGLE in Google Chrome: Arbitrary code execution via crafted HTML page | known affected: 18 known not affected: 27 | 2026-10-04T18:51:47+00:00 | Vulnerability · Source |
| CVE-2026-79229 | redhat_vex | chromium-browser: angle: Chromium: Information disclosure via uninitialized resource in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:51:47+00:00 | Vulnerability · Source |
| CVE-2026-17750 | redhat_vex | chromium-browser: angle: chromium-browser: Use after free in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:46:13+00:00 | Vulnerability · Source |
| CVE-2026-17678 | redhat_vex | chromium-browser: angle: chromium-browser: Out of bounds read in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:46:13+00:00 | Vulnerability · Source |
| CVE-2026-5283 | redhat_vex | chromium-browser: angle: Inappropriate implementation in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:46:13+00:00 | Vulnerability · Source |
| CVE-2026-11113 | redhat_vex | chromium-browser: angle: Insufficient validation of untrusted input in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:36:47+00:00 | Vulnerability · Source |
| CVE-2026-14411 | redhat_vex | chromium-browser: angle: chromium-browser: Insufficient validation of untrusted input in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:36:47+00:00 | Vulnerability · Source |
| CVE-2026-14125 | redhat_vex | chromium-browser: angle: Uninitialized Use in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:36:47+00:00 | Vulnerability · Source |
| CVE-2026-11040 | redhat_vex | chromium-browser: angle: Use after free in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:31:47+00:00 | Vulnerability · Source |
| CVE-2026-10883 | redhat_vex | chromium-browser: angle: Out of bounds write in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-04T18:31:47+00:00 | Vulnerability · Source |
| CVE-2026-105217 | redhat_vex | cockpit: Cockpit CMS: Sensitive token disclosure via disabled TLS certificate verification | known affected: 32 | 2026-10-04T17:31:12+00:00 | Vulnerability · Source |
| CVE-2013-1944 | suse_vex | SUSE CVE CVE-2013-1944 | known affected: 2 recommended: 202 | 2026-10-04T17:03:16+00:00 | Vulnerability · Source |
| CVE-2015-1931 | suse_vex | SUSE CVE CVE-2015-1931 | known affected: 396 known not affected: 1046 recommended: 418 | 2026-10-04T17:03:02+00:00 | Vulnerability · Source |
| CVE-2016-9594 | suse_vex | SUSE CVE CVE-2016-9594 | known affected: 320 known not affected: 165 recommended: 363 | 2026-10-04T17:02:39+00:00 | Vulnerability · Source |
| CVE-2017-7994 | suse_vex | SUSE CVE CVE-2017-7994 | known affected: 6 recommended: 28 | 2026-10-04T17:02:29+00:00 | Vulnerability · Source |
| CVE-2017-1000257 | suse_vex | SUSE CVE CVE-2017-1000257 | known affected: 338 known not affected: 93 recommended: 400 | 2026-10-04T17:02:19+00:00 | Vulnerability · Source |
| CVE-2019-15031 | suse_vex | SUSE CVE CVE-2019-15031 | known affected: 445 known not affected: 269 recommended: 1422 | 2026-10-04T17:01:52+00:00 | Vulnerability · Source |
| CVE-2020-0543 | suse_vex | SUSE CVE CVE-2020-0543 | known affected: 320 known not affected: 405 recommended: 2192 | 2026-10-04T17:01:46+00:00 | Vulnerability · Source |
| CVE-2020-8166 | suse_vex | SUSE CVE CVE-2020-8166 | known affected: 414 known not affected: 42 recommended: 145 | 2026-10-04T17:01:42+00:00 | Vulnerability · Source |
| CVE-2020-10690 | suse_vex | SUSE CVE CVE-2020-10690 | known affected: 335 known not affected: 49 recommended: 1447 | 2026-10-04T17:01:38+00:00 | Vulnerability · Source |
| CVE-2020-11979 | suse_vex | SUSE CVE CVE-2020-11979 | known affected: 18 known not affected: 60 recommended: 958 | 2026-10-04T17:01:35+00:00 | Vulnerability · Source |
| CVE-2020-12399 | suse_vex | SUSE CVE CVE-2020-12399 | known affected: 596 known not affected: 62 recommended: 1576 | 2026-10-04T17:01:32+00:00 | Vulnerability · Source |
| CVE-2020-19909 | suse_vex | SUSE CVE CVE-2020-19909 | recommended: 6 | 2026-10-04T17:01:27+00:00 | Vulnerability · Source |
| CVE-2020-26145 | suse_vex | SUSE CVE CVE-2020-26145 | known affected: 318 known not affected: 159 recommended: 1487 | 2026-10-04T17:01:23+00:00 | Vulnerability · Source |
| CVE-2020-36310 | suse_vex | SUSE CVE CVE-2020-36310 | known affected: 300 known not affected: 209 recommended: 1340 | 2026-10-04T17:01:19+00:00 | Vulnerability · Source |
| CVE-2021-0342 | suse_vex | SUSE CVE CVE-2021-0342 | known affected: 353 known not affected: 364 recommended: 1174 | 2026-10-04T17:01:17+00:00 | Vulnerability · Source |
| CVE-2021-3347 | suse_vex | SUSE CVE CVE-2021-3347 | known affected: 441 known not affected: 124 recommended: 1675 | 2026-10-04T17:01:14+00:00 | Vulnerability · Source |
| CVE-2021-22543 | suse_vex | SUSE CVE CVE-2021-22543 | known affected: 305 known not affected: 180 recommended: 1634 | 2026-10-04T17:01:08+00:00 | Vulnerability · Source |
| CVE-2021-23134 | suse_vex | SUSE CVE CVE-2021-23134 | known affected: 296 known not affected: 98 recommended: 1678 | 2026-10-04T17:01:06+00:00 | Vulnerability · Source |
| CVE-2021-23982 | suse_vex | SUSE CVE CVE-2021-23982 | recommended: 629 | 2026-10-04T17:01:04+00:00 | Vulnerability · Source |
| CVE-2021-27365 | suse_vex | SUSE CVE CVE-2021-27365 | known affected: 300 known not affected: 71 recommended: 1842 | 2026-10-04T17:01:01+00:00 | Vulnerability · Source |
| CVE-2021-30002 | suse_vex | SUSE CVE CVE-2021-30002 | known affected: 322 known not affected: 61 recommended: 1505 | 2026-10-04T17:00:58+00:00 | Vulnerability · Source |
| CVE-2021-46958 | suse_vex | SUSE CVE CVE-2021-46958 | known affected: 388 known not affected: 275 recommended: 207 | 2026-10-04T17:00:52+00:00 | Vulnerability · Source |
| CVE-2021-46966 | suse_vex | SUSE CVE CVE-2021-46966 | known affected: 388 known not affected: 236 recommended: 222 | 2026-10-04T17:00:50+00:00 | Vulnerability · Source |
| CVE-2021-46991 | suse_vex | SUSE CVE CVE-2021-46991 | known affected: 462 known not affected: 163 recommended: 207 | 2026-10-04T17:00:48+00:00 | Vulnerability · Source |
| CVE-2021-47054 | suse_vex | SUSE CVE CVE-2021-47054 | known affected: 463 known not affected: 195 recommended: 222 | 2026-10-04T17:00:46+00:00 | Vulnerability · Source |