VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-106334 | microsoft_vex | Chromium CVE-2026-106334: Information leak | fixed: 1 known affected: 1 | 2026-10-16T07:00:00+00:00 | Vulnerability · Source |
| CVE-2026-106224 | microsoft_vex | Chromium CVE-2026-106224: Missing authorization | fixed: 1 known affected: 1 | 2026-10-16T07:00:00+00:00 | Vulnerability · Source |
| CVE-2026-106396 | microsoft_vex | Chromium CVE-2026-106396: Improper input validation | fixed: 1 known affected: 1 | 2026-10-16T07:00:00+00:00 | Vulnerability · Source |
| CVE-2026-106362 | microsoft_vex | Chromium CVE-2026-106362: Missing authorization | fixed: 1 known affected: 1 | 2026-10-16T07:00:00+00:00 | Vulnerability · Source |
| CVE-2026-73569 | redhat_vex | fast-xml-parser: fast-xml-parser: Denial of Service via repeated DOCTYPE declarations | fixed: 112 known affected: 2 known not affected: 58 | 2026-10-16T06:50:43+00:00 | Vulnerability · Source |
| CVE-2026-84369 | redhat_vex | svgo: SVGO: Cross-Site Scripting (XSS) vulnerability in SVG foreignObject processing | under investigation: 84 | 2026-10-16T05:05:38+00:00 | Vulnerability · Source |
| CVE-2026-29063 | redhat_vex | immutable-js: Immutable.js: Arbitrary code execution via Prototype Pollution | fixed: 570 known affected: 36 known not affected: 12776 | 2026-10-16T04:37:13+00:00 | Vulnerability · Source |
| CVE-2026-4926 | redhat_vex | path-to-regexp: path-to-regexp: Denial of Service via crafted regular expressions | fixed: 50 known affected: 27 known not affected: 1183 | 2026-10-16T04:37:00+00:00 | Vulnerability · Source |
| CVE-2026-4800 | redhat_vex | lodash: lodash: Arbitrary code execution via untrusted input in template imports | fixed: 1169 known affected: 100 known not affected: 10886 | 2026-10-16T04:36:52+00:00 | Vulnerability · Source |
| CVE-2026-4602 | redhat_vex | jsrsasign: jsrsasign: Signature verification bypass via negative exponent handling | fixed: 19 known affected: 1 known not affected: 118 | 2026-10-16T04:36:48+00:00 | Vulnerability · Source |
| CVE-2026-4601 | redhat_vex | jsrsasign: jsrsasign: Private Key Recovery via Missing Cryptographic Step in DSA Signing | fixed: 19 known affected: 1 known not affected: 118 | 2026-10-16T04:36:44+00:00 | Vulnerability · Source |
| CVE-2026-4600 | redhat_vex | jsrsasign: jsrsasign: Cryptographic signature forgery via malicious DSA domain parameters | fixed: 19 known affected: 1 known not affected: 118 | 2026-10-16T04:36:31+00:00 | Vulnerability · Source |
| CVE-2026-4599 | redhat_vex | jsrsasign: jsrsasign: Private key recovery via incomplete comparison checks biasing DSA nonces | fixed: 19 known affected: 1 known not affected: 118 | 2026-10-16T04:36:26+00:00 | Vulnerability · Source |
| CVE-2026-4598 | redhat_vex | jsrsasign: jsrsasign: Denial of Service via infinite loop in bnModInverse function with crafted inputs | fixed: 19 known affected: 1 known not affected: 124 | 2026-10-16T04:36:13+00:00 | Vulnerability · Source |
| CVE-2023-30551 | redhat_vex | rekor: compressed archives can result in OOM conditions | fixed: 8 known affected: 1 known not affected: 893 | 2026-10-16T04:34:45+00:00 | Vulnerability · Source |
| CVE-2026-66053 | redhat_vex | thrift: Apache Thrift Python bindings: Information disclosure due to improper certificate validation | fixed: 13 known affected: 1 under investigation: 11 | 2026-10-16T04:01:58+00:00 | Vulnerability · Source |
| CVE-2026-33939 | redhat_vex | handlebars.js: Handlebars.js: Denial of Service via malformed decorator syntax in template compilation | fixed: 16 known affected: 20 known not affected: 174 | 2026-10-16T03:00:00+00:00 | Vulnerability · Source |
| CVE-2022-49935 | redhat_vex | kernel: dma-buf/dma-resv: check if the new fence is really later | fixed: 321 known affected: 38 known not affected: 119 | 2026-10-16T03:00:00+00:00 | Vulnerability · Source |
| CVE-2026-102674 | redhat_vex | electron: Electron: Sandbox bypass via popup window creation | known affected: 4 | 2026-10-16T03:00:00+00:00 | Vulnerability · Source |
| CVE-2025-38110 | redhat_vex | kernel: net/mdiobus: Fix potential out-of-bounds clause 45 read/write access | fixed: 891 known affected: 22 known not affected: 90 | 2026-10-16T03:00:00+00:00 | Vulnerability · Source |
| CVE-2022-50229 | redhat_vex | kernel: ALSA: bcd2000: Fix a UAF bug on the error path of probing | fixed: 647 known affected: 52 known not affected: 77 | 2026-10-16T03:00:00+00:00 | Vulnerability · Source |
| CVE-2022-50079 | redhat_vex | kernel: drm/amd/display: Check correct bounds for stream encoder instances for DCN303 | fixed: 321 known affected: 38 known not affected: 119 | 2026-10-16T03:00:00+00:00 | Vulnerability · Source |
| CVE-2026-98185 | redhat_vex | kernel: wifi: mwifiex: validate scan response extents | known affected: 263 known not affected: 14 | 2026-10-16T02:46:12+00:00 | Vulnerability · Source |
| CVE-2023-52759 | suse_vex | SUSE CVE CVE-2023-52759 | known affected: 413 known not affected: 31 recommended: 903 | 2026-10-16T02:42:36+00:00 | Vulnerability · Source |
| CVE-2023-52760 | suse_vex | SUSE CVE CVE-2023-52760 | known not affected: 385 | 2026-10-16T02:42:34+00:00 | Vulnerability · Source |
| CVE-2023-52764 | suse_vex | SUSE CVE CVE-2023-52764 | known affected: 477 known not affected: 23 recommended: 909 | 2026-10-16T02:42:29+00:00 | Vulnerability · Source |
| CVE-2023-52767 | suse_vex | SUSE CVE CVE-2023-52767 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-16T02:42:27+00:00 | Vulnerability · Source |
| CVE-2023-52770 | suse_vex | SUSE CVE CVE-2023-52770 | known not affected: 385 | 2026-10-16T02:42:25+00:00 | Vulnerability · Source |
| CVE-2023-52772 | suse_vex | SUSE CVE CVE-2023-52772 | known affected: 394 known not affected: 332 recommended: 356 | 2026-10-16T02:42:23+00:00 | Vulnerability · Source |
| CVE-2023-52775 | suse_vex | SUSE CVE CVE-2023-52775 | known affected: 330 known not affected: 188 recommended: 671 | 2026-10-16T02:42:20+00:00 | Vulnerability · Source |
| CVE-2023-52776 | suse_vex | SUSE CVE CVE-2023-52776 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-16T02:42:18+00:00 | Vulnerability · Source |
| CVE-2023-52778 | suse_vex | SUSE CVE CVE-2023-52778 | known affected: 398 known not affected: 426 recommended: 358 | 2026-10-16T02:42:15+00:00 | Vulnerability · Source |
| CVE-2023-52780 | suse_vex | SUSE CVE CVE-2023-52780 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-16T02:42:13+00:00 | Vulnerability · Source |
| CVE-2023-52785 | suse_vex | SUSE CVE CVE-2023-52785 | known not affected: 385 | 2026-10-16T02:42:10+00:00 | Vulnerability · Source |
| CVE-2023-52787 | suse_vex | SUSE CVE CVE-2023-52787 | known affected: 352 known not affected: 304 recommended: 651 | 2026-10-16T02:42:07+00:00 | Vulnerability · Source |
| CVE-2023-52788 | suse_vex | SUSE CVE CVE-2023-52788 | known affected: 275 known not affected: 235 recommended: 805 | 2026-10-16T02:42:05+00:00 | Vulnerability · Source |
| CVE-2023-52791 | suse_vex | SUSE CVE CVE-2023-52791 | known affected: 342 known not affected: 164 recommended: 825 | 2026-10-16T02:42:03+00:00 | Vulnerability · Source |
| CVE-2023-52794 | suse_vex | SUSE CVE CVE-2023-52794 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-16T02:42:00+00:00 | Vulnerability · Source |
| CVE-2023-52795 | suse_vex | SUSE CVE CVE-2023-52795 | known affected: 315 known not affected: 292 recommended: 666 | 2026-10-16T02:41:58+00:00 | Vulnerability · Source |
| CVE-2023-52797 | suse_vex | SUSE CVE CVE-2023-52797 | known not affected: 385 | 2026-10-16T02:41:54+00:00 | Vulnerability · Source |
| CVE-2023-52799 | suse_vex | SUSE CVE CVE-2023-52799 | known affected: 275 known not affected: 231 recommended: 805 | 2026-10-16T02:41:51+00:00 | Vulnerability · Source |
| CVE-2023-52801 | suse_vex | SUSE CVE CVE-2023-52801 | known affected: 394 known not affected: 354 recommended: 411 | 2026-10-16T02:41:48+00:00 | Vulnerability · Source |
| CVE-2023-52810 | suse_vex | SUSE CVE CVE-2023-52810 | known affected: 275 known not affected: 235 recommended: 805 | 2026-10-16T02:41:45+00:00 | Vulnerability · Source |
| CVE-2023-52814 | suse_vex | SUSE CVE CVE-2023-52814 | known affected: 324 known not affected: 216 recommended: 805 | 2026-10-16T02:41:43+00:00 | Vulnerability · Source |
| CVE-2023-52817 | suse_vex | SUSE CVE CVE-2023-52817 | known affected: 463 known not affected: 36 recommended: 953 | 2026-10-16T02:41:39+00:00 | Vulnerability · Source |
| CVE-2023-52818 | suse_vex | SUSE CVE CVE-2023-52818 | known affected: 441 known not affected: 25 recommended: 875 | 2026-10-16T02:41:37+00:00 | Vulnerability · Source |
| CVE-2023-52822 | suse_vex | SUSE CVE CVE-2023-52822 | known not affected: 168 | 2026-10-16T02:41:35+00:00 | Vulnerability · Source |
| CVE-2023-52823 | suse_vex | SUSE CVE CVE-2023-52823 | known not affected: 332 | 2026-10-16T02:41:33+00:00 | Vulnerability · Source |
| CVE-2023-52826 | suse_vex | SUSE CVE CVE-2023-52826 | known affected: 342 known not affected: 164 recommended: 805 | 2026-10-16T02:41:31+00:00 | Vulnerability · Source |
| CVE-2023-52827 | suse_vex | SUSE CVE CVE-2023-52827 | known affected: 394 known not affected: 354 recommended: 353 | 2026-10-16T02:41:29+00:00 | Vulnerability · Source |