VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104391 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-36311 | suse_vex | SUSE CVE CVE-2020-36311 | known affected: 300 known not affected: 209 recommended: 1340 | 2026-10-17T01:43:47+00:00 | Vulnerability · Source |
| CVE-2020-36465 | suse_vex | SUSE CVE CVE-2020-36465 | recommended: 22 | 2026-10-17T01:43:45+00:00 | Vulnerability · Source |
| CVE-2020-36518 | suse_vex | SUSE CVE CVE-2020-36518 | known affected: 402 recommended: 279 | 2026-10-17T01:43:44+00:00 | Vulnerability · Source |
| CVE-2020-36694 | suse_vex | SUSE CVE CVE-2020-36694 | known affected: 0 known not affected: 359 recommended: 242 | 2026-10-17T01:43:42+00:00 | Vulnerability · Source |
| CVE-2020-36776 | suse_vex | SUSE CVE CVE-2020-36776 | known affected: 0 known not affected: 367 | 2026-10-17T01:43:40+00:00 | Vulnerability · Source |
| CVE-2020-36779 | suse_vex | SUSE CVE CVE-2020-36779 | known affected: 0 known not affected: 321 | 2026-10-17T01:43:38+00:00 | Vulnerability · Source |
| CVE-2020-36783 | suse_vex | SUSE CVE CVE-2020-36783 | known affected: 388 known not affected: 254 recommended: 137 | 2026-10-17T01:43:37+00:00 | Vulnerability · Source |
| CVE-2026-93323 | microsoft_vex | Oversized Dockerfile or .dockerignore can exhaust buildkitd memory | fixed: 1 known affected: 1 known not affected: 1 | 2026-10-17T01:43:35+00:00 | Vulnerability · Source |
| CVE-2020-36784 | suse_vex | SUSE CVE CVE-2020-36784 | known affected: 462 known not affected: 214 recommended: 222 | 2026-10-17T01:43:35+00:00 | Vulnerability · Source |
| CVE-2020-36785 | suse_vex | SUSE CVE CVE-2020-36785 | known affected: 0 known not affected: 321 | 2026-10-17T01:43:34+00:00 | Vulnerability · Source |
| CVE-2020-36789 | suse_vex | SUSE CVE CVE-2020-36789 | known affected: 488 known not affected: 300 recommended: 122 | 2026-10-17T01:43:32+00:00 | Vulnerability · Source |
| CVE-2020-36791 | suse_vex | SUSE CVE CVE-2020-36791 | known affected: 394 known not affected: 415 recommended: 102 | 2026-10-17T01:43:30+00:00 | Vulnerability · Source |
| CVE-2020-36843 | suse_vex | SUSE CVE CVE-2020-36843 | known affected: 4 recommended: 67 | 2026-10-17T01:43:28+00:00 | Vulnerability · Source |
| CVE-2020-36846 | suse_vex | SUSE CVE CVE-2020-36846 | known affected: 0 known not affected: 356 recommended: 5 | 2026-10-17T01:43:27+00:00 | Vulnerability · Source |
| CVE-2021-0127 | suse_vex | SUSE CVE CVE-2021-0127 | recommended: 87 | 2026-10-17T01:43:25+00:00 | Vulnerability · Source |
| CVE-2021-0512 | suse_vex | SUSE CVE CVE-2021-0512 | known affected: 299 known not affected: 71 recommended: 1690 | 2026-10-17T01:43:24+00:00 | Vulnerability · Source |
| CVE-2026-76844 | microsoft_vex | zlib 1.2.11 through 1.3.2 Heap Buffer Overflow via Stale gzwrite Pointer After Failed Write | fixed: 1 known affected: 1 | 2026-10-17T01:43:23+00:00 | Vulnerability · Source |
| CVE-2021-0606 | suse_vex | SUSE CVE CVE-2021-0606 | known affected: 0 known not affected: 342 | 2026-10-17T01:43:22+00:00 | Vulnerability · Source |
| CVE-2021-0929 | suse_vex | SUSE CVE CVE-2021-0929 | known affected: 0 known not affected: 388 | 2026-10-17T01:43:21+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-17T01:43:19+00:00 | Vulnerability · Source |
| CVE-2021-0938 | suse_vex | SUSE CVE CVE-2021-0938 | known affected: 0 known not affected: 338 | 2026-10-17T01:43:18+00:00 | Vulnerability · Source |
| CVE-2021-0961 | suse_vex | SUSE CVE CVE-2021-0961 | known affected: 0 known not affected: 388 | 2026-10-17T01:43:17+00:00 | Vulnerability · Source |
| CVE-2021-1252 | suse_vex | SUSE CVE CVE-2021-1252 | recommended: 287 | 2026-10-17T01:43:15+00:00 | Vulnerability · Source |
| CVE-2021-1404 | suse_vex | SUSE CVE CVE-2021-1404 | recommended: 287 | 2026-10-17T01:43:14+00:00 | Vulnerability · Source |
| CVE-2026-94283 | microsoft_vex | Out-of-bounds read vulnerability in libX11's XIM (X Input Method) attribute parser | fixed: 1 known affected: 1 | 2026-10-17T01:43:13+00:00 | Vulnerability · Source |
| CVE-2021-1788 | suse_vex | SUSE CVE CVE-2021-1788 | recommended: 1106 | 2026-10-17T01:43:12+00:00 | Vulnerability · Source |
| CVE-2021-1799 | suse_vex | SUSE CVE CVE-2021-1799 | recommended: 1008 | 2026-10-17T01:43:11+00:00 | Vulnerability · Source |
| CVE-2026-94284 | microsoft_vex | Out-of-bounds read vulnerability in libX11's XIM trigger-keyregistration parser.registration parser | fixed: 1 known affected: 1 | 2026-10-17T01:43:09+00:00 | Vulnerability · Source |
| CVE-2021-1825 | suse_vex | SUSE CVE CVE-2021-1825 | known affected: 1 known not affected: 117 recommended: 925 | 2026-10-17T01:43:09+00:00 | Vulnerability · Source |
| CVE-2026-87875 | microsoft_vex | Cups: openprinting cups: heap out-of-bounds read in cupsutf32toutf8() via missing source-length bound | fixed: 1 known affected: 1 | 2026-10-17T01:43:08+00:00 | Vulnerability · Source |
| CVE-2021-1826 | suse_vex | SUSE CVE CVE-2021-1826 | known affected: 1 known not affected: 117 recommended: 925 | 2026-10-17T01:43:08+00:00 | Vulnerability · Source |
| CVE-2021-2166 | suse_vex | SUSE CVE CVE-2021-2166 | known affected: 0 known not affected: 42 recommended: 475 | 2026-10-17T01:43:06+00:00 | Vulnerability · Source |
| CVE-2021-2389 | suse_vex | SUSE CVE CVE-2021-2389 | known affected: 0 known not affected: 42 recommended: 475 | 2026-10-17T01:43:05+00:00 | Vulnerability · Source |
| CVE-2026-94285 | microsoft_vex | Out-of-bounds read in libX11's byte-oriented codeset parser | fixed: 1 known affected: 1 | 2026-10-17T01:43:04+00:00 | Vulnerability · Source |
| CVE-2021-3177 | suse_vex | SUSE CVE CVE-2021-3177 | known affected: 293 known not affected: 192 recommended: 1770 | 2026-10-17T01:43:02+00:00 | Vulnerability · Source |
| CVE-2021-3178 | suse_vex | SUSE CVE CVE-2021-3178 | No product status | 2026-10-17T01:43:01+00:00 | Vulnerability · Source |
| CVE-2021-3236 | suse_vex | SUSE CVE CVE-2021-3236 | known affected: 0 known not affected: 284 | 2026-10-17T01:42:59+00:00 | Vulnerability · Source |
| CVE-2021-3326 | suse_vex | SUSE CVE CVE-2021-3326 | known affected: 330 known not affected: 285 recommended: 1361 | 2026-10-17T01:42:58+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-17T01:42:56+00:00 | Vulnerability · Source |
| CVE-2021-3348 | suse_vex | SUSE CVE CVE-2021-3348 | known affected: 312 known not affected: 275 recommended: 1177 | 2026-10-17T01:42:54+00:00 | Vulnerability · Source |
| CVE-2021-3409 | suse_vex | SUSE CVE CVE-2021-3409 | known affected: 436 known not affected: 811 recommended: 1556 | 2026-10-17T01:42:53+00:00 | Vulnerability · Source |
| CVE-2021-3410 | suse_vex | SUSE CVE CVE-2021-3410 | known affected: 52 known not affected: 2 recommended: 185 | 2026-10-17T01:42:52+00:00 | Vulnerability · Source |
| CVE-2021-3416 | suse_vex | SUSE CVE CVE-2021-3416 | known affected: 388 known not affected: 269 recommended: 1991 | 2026-10-17T01:42:50+00:00 | Vulnerability · Source |
| CVE-2021-3426 | suse_vex | SUSE CVE CVE-2021-3426 | known affected: 361 known not affected: 419 recommended: 953 | 2026-10-17T01:42:48+00:00 | Vulnerability · Source |
| CVE-2021-3443 | suse_vex | SUSE CVE CVE-2021-3443 | known affected: 468 recommended: 111 | 2026-10-17T01:42:47+00:00 | Vulnerability · Source |
| CVE-2021-3446 | suse_vex | SUSE CVE CVE-2021-3446 | recommended: 51 | 2026-10-17T01:42:45+00:00 | Vulnerability · Source |
| CVE-2021-3472 | suse_vex | SUSE CVE CVE-2021-3472 | known affected: 396 recommended: 297 | 2026-10-17T01:42:44+00:00 | Vulnerability · Source |
| CVE-2021-3489 | suse_vex | SUSE CVE CVE-2021-3489 | known affected: 322 known not affected: 346 recommended: 754 | 2026-10-17T01:42:43+00:00 | Vulnerability · Source |
| CVE-2021-3490 | suse_vex | SUSE CVE CVE-2021-3490 | known affected: 322 known not affected: 346 recommended: 734 | 2026-10-17T01:42:41+00:00 | Vulnerability · Source |
| CVE-2021-3497 | suse_vex | SUSE CVE CVE-2021-3497 | known affected: 26 recommended: 154 | 2026-10-17T01:42:40+00:00 | Vulnerability · Source |