VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291927 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-17887 | redhat_vex | chromium-browser: chromium-browser: Use after free in TabStrip | known not affected: 1 | 2026-07-30T23:10:13+00:00 | Vulnerability · Source |
| CVE-2026-17850 | redhat_vex | chromium-browser: chromium-browser: Inappropriate implementation in Permissions | known not affected: 1 | 2026-07-30T23:10:12+00:00 | Vulnerability · Source |
| CVE-2026-17864 | redhat_vex | chromium-browser: chromium-browser: Inappropriate implementation in Updater | known not affected: 1 | 2026-07-30T23:10:10+00:00 | Vulnerability · Source |
| CVE-2026-17827 | redhat_vex | chromium-browser: chromium-browser: Inappropriate implementation in CSS | known not affected: 1 | 2026-07-30T23:10:09+00:00 | Vulnerability · Source |
| CVE-2026-17857 | redhat_vex | chromium-browser: chromium-browser: Inappropriate implementation in Network | known not affected: 1 | 2026-07-30T23:10:06+00:00 | Vulnerability · Source |
| CVE-2026-17883 | redhat_vex | chromium-browser: Google Chrome Headless: Same-Origin Policy bypass via crafted HTML page | known not affected: 1 | 2026-07-30T23:09:28+00:00 | Vulnerability · Source |
| CVE-2025-4435 | redhat_vex | cpython: Tarfile extracts filtered members when errorlevel=0 | fixed: 1018 known not affected: 49 | 2026-07-30T23:07:08+00:00 | Vulnerability · Source |
| CVE-2024-12718 | redhat_vex | cpython: python: Bypass extraction filter to modify file metadata outside extraction directory | fixed: 832 known not affected: 53 | 2026-07-30T23:04:06+00:00 | Vulnerability · Source |
| CVE-2021-23133 | redhat_vex | kernel: Race condition in sctp_destroy_sock list_del | fixed: 150 known affected: 29 known not affected: 120 | 2026-07-30T19:45:52+00:00 | Vulnerability · Source |
| CVE-2021-23134 | redhat_vex | kernel: use-after-free in nfc sockets | known not affected: 197 | 2026-07-30T19:45:44+00:00 | Vulnerability · Source |
| CVE-2026-9563 | redhat_vex | org.eclipse.parsson/parsson: Eclipse Parsson: Denial of Service via uncontrolled resource consumption in JSON parsing | known affected: 15 known not affected: 14 | 2026-07-30T19:35:55+00:00 | Vulnerability · Source |
| CVE-2021-27365 | redhat_vex | kernel: heap buffer overflow in the iSCSI subsystem | fixed: 1339 known not affected: 108 | 2026-07-30T19:35:51+00:00 | Vulnerability · Source |
| CVE-2026-41284 | redhat_vex | tomcat: Apache Tomcat: Denial of Service due to uncontrolled resource allocation | fixed: 68 known affected: 4 known not affected: 58 | 2026-07-30T19:35:47+00:00 | Vulnerability · Source |
| CVE-2026-63797 | redhat_vex | kernel: rpmsg: char: Fix use-after-free on probe error path | known affected: 76 known not affected: 198 | 2026-07-30T17:44:59+00:00 | Vulnerability · Source |
| CVE-2026-63794 | redhat_vex | kernel: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path | known affected: 232 known not affected: 42 | 2026-07-30T17:44:59+00:00 | Vulnerability · Source |
| CVE-2023-1281 | redhat_vex | kernel: tcindex: use-after-free vulnerability in traffic control index filter allows privilege escalation | fixed: 806 known affected: 28 known not affected: 122 | 2026-07-30T17:05:21+00:00 | Vulnerability · Source |
| CVE-2026-20213 | suse_vex | SUSE CVE CVE-2026-20213 | known affected: 32 recommended: 189 | 2026-07-30T17:00:51+00:00 | Vulnerability · Source |
| CVE-2026-20214 | suse_vex | SUSE CVE CVE-2026-20214 | known affected: 16 known not affected: 16 recommended: 189 | 2026-07-30T17:00:49+00:00 | Vulnerability · Source |
| CVE-2026-20215 | suse_vex | SUSE CVE CVE-2026-20215 | known affected: 16 known not affected: 16 recommended: 189 | 2026-07-30T17:00:48+00:00 | Vulnerability · Source |
| CVE-2026-20216 | suse_vex | SUSE CVE CVE-2026-20216 | known affected: 16 known not affected: 16 recommended: 189 | 2026-07-30T17:00:46+00:00 | Vulnerability · Source |
| CVE-2026-20217 | suse_vex | SUSE CVE CVE-2026-20217 | known affected: 16 known not affected: 16 recommended: 189 | 2026-07-30T17:00:45+00:00 | Vulnerability · Source |
| CVE-2026-20243 | suse_vex | SUSE CVE CVE-2026-20243 | known affected: 16 known not affected: 16 recommended: 189 | 2026-07-30T17:00:43+00:00 | Vulnerability · Source |
| CVE-2026-20244 | suse_vex | SUSE CVE CVE-2026-20244 | known affected: 32 recommended: 189 | 2026-07-30T17:00:41+00:00 | Vulnerability · Source |
| CVE-2026-20706 | suse_vex | SUSE CVE CVE-2026-20706 | No product status | 2026-07-30T17:00:40+00:00 | Vulnerability · Source |
| CVE-2026-20719 | suse_vex | SUSE CVE CVE-2026-20719 | No product status | 2026-07-30T17:00:38+00:00 | Vulnerability · Source |
| CVE-2026-20779 | suse_vex | SUSE CVE CVE-2026-20779 | No product status | 2026-07-30T17:00:36+00:00 | Vulnerability · Source |
| CVE-2026-20896 | suse_vex | SUSE CVE CVE-2026-20896 | No product status | 2026-07-30T17:00:34+00:00 | Vulnerability · Source |
| CVE-2026-21388 | suse_vex | SUSE CVE CVE-2026-21388 | No product status | 2026-07-30T17:00:32+00:00 | Vulnerability · Source |
| CVE-2026-21721 | suse_vex | SUSE CVE CVE-2026-21721 | known affected: 2 recommended: 57 | 2026-07-30T17:00:29+00:00 | Vulnerability · Source |
| CVE-2026-21728 | suse_vex | SUSE CVE CVE-2026-21728 | No product status | 2026-07-30T17:00:25+00:00 | Vulnerability · Source |
| CVE-2026-22555 | suse_vex | SUSE CVE CVE-2026-22555 | No product status | 2026-07-30T17:00:23+00:00 | Vulnerability · Source |
| CVE-2026-22872 | suse_vex | SUSE CVE CVE-2026-22872 | No product status | 2026-07-30T17:00:19+00:00 | Vulnerability · Source |
| CVE-2026-22874 | suse_vex | SUSE CVE CVE-2026-22874 | No product status | 2026-07-30T17:00:17+00:00 | Vulnerability · Source |
| CVE-2026-23998 | suse_vex | SUSE CVE CVE-2026-23998 | No product status | 2026-07-30T16:59:35+00:00 | Vulnerability · Source |
| CVE-2026-24000 | suse_vex | SUSE CVE CVE-2026-24000 | No product status | 2026-07-30T16:59:34+00:00 | Vulnerability · Source |
| CVE-2026-24661 | suse_vex | SUSE CVE CVE-2026-24661 | No product status | 2026-07-30T16:59:32+00:00 | Vulnerability · Source |
| CVE-2026-24899 | suse_vex | SUSE CVE CVE-2026-24899 | No product status | 2026-07-30T16:59:29+00:00 | Vulnerability · Source |
| CVE-2026-25119 | suse_vex | SUSE CVE CVE-2026-25119 | No product status | 2026-07-30T16:59:27+00:00 | Vulnerability · Source |
| CVE-2026-25714 | suse_vex | SUSE CVE CVE-2026-25714 | No product status | 2026-07-30T16:59:24+00:00 | Vulnerability · Source |
| CVE-2026-25726 | suse_vex | SUSE CVE CVE-2026-25726 | No product status | 2026-07-30T16:59:23+00:00 | Vulnerability · Source |
| CVE-2026-25773 | suse_vex | SUSE CVE CVE-2026-25773 | No product status | 2026-07-30T16:59:21+00:00 | Vulnerability · Source |
| CVE-2026-25779 | suse_vex | SUSE CVE CVE-2026-25779 | No product status | 2026-07-30T16:59:20+00:00 | Vulnerability · Source |
| CVE-2026-26062 | suse_vex | SUSE CVE CVE-2026-26062 | No product status | 2026-07-30T16:59:18+00:00 | Vulnerability · Source |
| CVE-2026-26191 | suse_vex | SUSE CVE CVE-2026-26191 | No product status | 2026-07-30T16:59:16+00:00 | Vulnerability · Source |
| CVE-2026-26231 | suse_vex | SUSE CVE CVE-2026-26231 | No product status | 2026-07-30T16:59:15+00:00 | Vulnerability · Source |
| CVE-2026-26931 | suse_vex | SUSE CVE CVE-2026-26931 | No product status | 2026-07-30T16:59:13+00:00 | Vulnerability · Source |
| CVE-2026-26933 | suse_vex | SUSE CVE CVE-2026-26933 | No product status | 2026-07-30T16:59:12+00:00 | Vulnerability · Source |
| CVE-2026-27656 | suse_vex | SUSE CVE CVE-2026-27656 | No product status | 2026-07-30T16:59:02+00:00 | Vulnerability · Source |
| CVE-2026-27659 | suse_vex | SUSE CVE CVE-2026-27659 | No product status | 2026-07-30T16:59:01+00:00 | Vulnerability · Source |
| CVE-2026-27761 | suse_vex | SUSE CVE CVE-2026-27761 | No product status | 2026-07-30T16:58:59+00:00 | Vulnerability · Source |