VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
76422 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-95354 | redhat_vex | chromium-browser: Use after free in Verifier | known not affected: 1 | 2026-10-03T02:26:00+00:00 | Vulnerability · Source |
| CVE-2026-95290 | redhat_vex | chromium-browser: Missing authorization in NFC | known not affected: 1 | 2026-10-03T02:25:59+00:00 | Vulnerability · Source |
| CVE-2026-9932 | redhat_vex | chromium-browser: angle: Use after free in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T02:25:59+00:00 | Vulnerability · Source |
| CVE-2026-9900 | redhat_vex | chromium-browser: angle: Out of bounds write in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T02:25:59+00:00 | Vulnerability · Source |
| CVE-2026-87621 | redhat_vex | chromium-browser: angle: Google Chrome (ANGLE): Arbitrary Code Execution vulnerability | known affected: 22 known not affected: 23 | 2026-10-03T02:21:09+00:00 | Vulnerability · Source |
| CVE-2026-95341 | redhat_vex | chromium-browser: Improper input validation in Desktop | known not affected: 1 | 2026-10-03T02:21:09+00:00 | Vulnerability · Source |
| CVE-2026-79282 | redhat_vex | chromium-browser: angle: ANGLE in Google Chrome: Arbitrary code execution via crafted HTML page | fixed: 92 known affected: 7 known not affected: 27 | 2026-10-03T02:21:09+00:00 | Vulnerability · Source |
| CVE-2026-95346 | redhat_vex | chromium-browser: UI misrepresentation in Chromoting | known not affected: 1 | 2026-10-03T02:20:56+00:00 | Vulnerability · Source |
| CVE-2026-79120 | redhat_vex | chromium-browser: angle: ANGLE in Google Chrome: Cross-origin data disclosure via uninitialized resource | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T02:16:01+00:00 | Vulnerability · Source |
| CVE-2026-95276 | redhat_vex | chromium-browser: Improper input validation in Themes | known not affected: 1 | 2026-10-03T02:16:01+00:00 | Vulnerability · Source |
| CVE-2026-17847 | 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-03T02:11:34+00:00 | Vulnerability · Source |
| CVE-2026-7359 | redhat_vex | chromium-browser: angle: Use after free in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T02:11:34+00:00 | Vulnerability · Source |
| CVE-2026-17695 | redhat_vex | chromium-browser: angle: chromium-browser: Inappropriate implementation in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T02:05:58+00:00 | Vulnerability · Source |
| CVE-2026-105083 | redhat_vex | ImageMagick: ImageMagick: Security policy bypass via alternate XML DOCTYPE declaration | known affected: 14 | 2026-10-03T01:55:52+00:00 | Vulnerability · Source |
| CVE-2026-16413 | redhat_vex | chromium-browser: angle: Chromium: Sandbox escape via out-of-bounds write in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T01:55:52+00:00 | Vulnerability · Source |
| CVE-2026-14388 | redhat_vex | chromium-browser: angle: chromium-browser: Out of bounds read in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T01:55:52+00:00 | Vulnerability · Source |
| CVE-2026-95337 | redhat_vex | chromium-browser: UI misrepresentation in Messages | known not affected: 1 | 2026-10-03T01:55:50+00:00 | Vulnerability · Source |
| CVE-2026-13780 | redhat_vex | chromium-browser: angle: Insufficient validation of untrusted input in ANGLE | fixed: 92 known affected: 11 known not affected: 23 | 2026-10-03T01:48:28+00:00 | Vulnerability · Source |
| CVE-2017-5886 | suse_vex | SUSE CVE CVE-2017-5886 | known affected: 6 recommended: 28 | 2026-10-03T01:07:31+00:00 | Vulnerability · Source |
| CVE-2018-18493 | suse_vex | SUSE CVE CVE-2018-18493 | known affected: 24 known not affected: 164 recommended: 1221 | 2026-10-03T01:07:03+00:00 | Vulnerability · Source |
| CVE-2019-16994 | suse_vex | SUSE CVE CVE-2019-16994 | known affected: 134 known not affected: 319 recommended: 534 | 2026-10-03T01:06:43+00:00 | Vulnerability · Source |
| CVE-2019-19051 | suse_vex | SUSE CVE CVE-2019-19051 | known affected: 437 known not affected: 230 recommended: 1267 | 2026-10-03T01:06:39+00:00 | Vulnerability · Source |
| CVE-2019-19075 | suse_vex | SUSE CVE CVE-2019-19075 | known affected: 445 known not affected: 216 recommended: 1305 | 2026-10-03T01:06:37+00:00 | Vulnerability · Source |
| CVE-2019-19338 | suse_vex | SUSE CVE CVE-2019-19338 | known affected: 469 known not affected: 109 recommended: 1405 | 2026-10-03T01:06:35+00:00 | Vulnerability · Source |
| CVE-2019-19527 | suse_vex | SUSE CVE CVE-2019-19527 | known affected: 141 known not affected: 71 recommended: 747 | 2026-10-03T01:06:33+00:00 | Vulnerability · Source |
| CVE-2019-19534 | suse_vex | SUSE CVE CVE-2019-19534 | known affected: 149 known not affected: 81 recommended: 1419 | 2026-10-03T01:06:31+00:00 | Vulnerability · Source |
| CVE-2019-20096 | suse_vex | SUSE CVE CVE-2019-20096 | known not affected: 132 recommended: 698 | 2026-10-03T01:06:28+00:00 | Vulnerability · Source |
| CVE-2019-20908 | suse_vex | SUSE CVE CVE-2019-20908 | known affected: 105 known not affected: 196 recommended: 462 | 2026-10-03T01:06:25+00:00 | Vulnerability · Source |
| CVE-2020-6829 | suse_vex | SUSE CVE CVE-2020-6829 | known affected: 311 known not affected: 247 recommended: 1586 | 2026-10-03T01:06:19+00:00 | Vulnerability · Source |
| CVE-2020-8992 | suse_vex | SUSE CVE CVE-2020-8992 | known affected: 324 known not affected: 142 recommended: 1413 | 2026-10-03T01:06:16+00:00 | Vulnerability · Source |
| CVE-2020-10757 | suse_vex | SUSE CVE CVE-2020-10757 | known affected: 515 known not affected: 104 recommended: 1684 | 2026-10-03T01:06:12+00:00 | Vulnerability · Source |
| CVE-2020-12114 | suse_vex | SUSE CVE CVE-2020-12114 | known affected: 97 known not affected: 123 recommended: 644 | 2026-10-03T01:06:09+00:00 | Vulnerability · Source |
| CVE-2020-12769 | suse_vex | SUSE CVE CVE-2020-12769 | known affected: 393 known not affected: 180 recommended: 1357 | 2026-10-03T01:06:06+00:00 | Vulnerability · Source |
| CVE-2020-25645 | suse_vex | SUSE CVE CVE-2020-25645 | known affected: 598 known not affected: 17 recommended: 1766 | 2026-10-03T01:05:59+00:00 | Vulnerability · Source |
| CVE-2020-25704 | suse_vex | SUSE CVE CVE-2020-25704 | known affected: 404 known not affected: 255 recommended: 1403 | 2026-10-03T01:05:56+00:00 | Vulnerability · Source |
| CVE-2020-25705 | suse_vex | SUSE CVE CVE-2020-25705 | known affected: 523 known not affected: 30 recommended: 1833 | 2026-10-03T01:05:54+00:00 | Vulnerability · Source |
| CVE-2021-0935 | suse_vex | SUSE CVE CVE-2021-0935 | known affected: 455 known not affected: 279 recommended: 525 | 2026-10-03T01:05:49+00:00 | Vulnerability · Source |
| CVE-2021-3612 | suse_vex | SUSE CVE CVE-2021-3612 | known affected: 308 known not affected: 265 recommended: 1066 | 2026-10-03T01:05:45+00:00 | Vulnerability · Source |
| CVE-2021-3760 | suse_vex | SUSE CVE CVE-2021-3760 | known affected: 326 known not affected: 92 recommended: 1361 | 2026-10-03T01:05:43+00:00 | Vulnerability · Source |
| CVE-2021-20321 | suse_vex | SUSE CVE CVE-2021-20321 | known affected: 354 known not affected: 86 recommended: 1275 | 2026-10-03T01:05:39+00:00 | Vulnerability · Source |
| CVE-2021-28660 | suse_vex | SUSE CVE CVE-2021-28660 | known affected: 300 known not affected: 98 recommended: 1684 | 2026-10-03T01:05:34+00:00 | Vulnerability · Source |
| CVE-2021-29154 | suse_vex | SUSE CVE CVE-2021-29154 | known affected: 300 known not affected: 71 recommended: 1780 | 2026-10-03T01:05:32+00:00 | Vulnerability · Source |
| CVE-2021-39648 | suse_vex | SUSE CVE CVE-2021-39648 | known affected: 338 known not affected: 121 recommended: 971 | 2026-10-03T01:05:27+00:00 | Vulnerability · Source |
| CVE-2021-46955 | suse_vex | SUSE CVE CVE-2021-46955 | known affected: 388 known not affected: 361 recommended: 310 | 2026-10-03T01:05:23+00:00 | Vulnerability · Source |
| CVE-2021-46998 | suse_vex | SUSE CVE CVE-2021-46998 | known affected: 388 known not affected: 270 recommended: 207 | 2026-10-03T01:05:21+00:00 | Vulnerability · Source |
| CVE-2021-47034 | suse_vex | SUSE CVE CVE-2021-47034 | known affected: 388 known not affected: 270 recommended: 207 | 2026-10-03T01:05:18+00:00 | Vulnerability · Source |
| CVE-2021-47166 | suse_vex | SUSE CVE CVE-2021-47166 | known affected: 529 known not affected: 202 recommended: 221 | 2026-10-03T01:05:14+00:00 | Vulnerability · Source |
| CVE-2021-47168 | suse_vex | SUSE CVE CVE-2021-47168 | known affected: 535 known not affected: 196 recommended: 221 | 2026-10-03T01:05:12+00:00 | Vulnerability · Source |
| CVE-2021-47185 | suse_vex | SUSE CVE CVE-2021-47185 | known affected: 374 known not affected: 90 recommended: 709 | 2026-10-03T01:05:10+00:00 | Vulnerability · Source |
| CVE-2021-47193 | suse_vex | SUSE CVE CVE-2021-47193 | known affected: 315 known not affected: 245 recommended: 546 | 2026-10-03T01:05:08+00:00 | Vulnerability · Source |