VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289533 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-17566 | redhat_vex | pgAdmin 4: pgAdmin 4: Remote Code Execution via backslash-escape mismatch in Import/Export Data tool | known not affected: 1 | 2026-07-31T19:18:42+00:00 | Vulnerability · Source |
| CVE-2026-63853 | redhat_vex | kernel: drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring | known affected: 246 known not affected: 28 | 2026-07-31T19:18:35+00:00 | Vulnerability · Source |
| CVE-2026-63840 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v5.3.0 ring | known affected: 198 known not affected: 76 | 2026-07-31T19:13:17+00:00 | Vulnerability · Source |
| CVE-2026-63841 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring | known affected: 198 known not affected: 76 | 2026-07-31T19:08:19+00:00 | Vulnerability · Source |
| CVE-2026-68563 | redhat_vex | ansible-collection-redhat-leapp: ansible-collection-redhat-leapp: Information disclosure of PostgreSQL data via insecure backup permissions | known affected: 2 | 2026-07-31T19:08:16+00:00 | Vulnerability · Source |
| CVE-2026-68562 | redhat_vex | ansible-collection-redhat-leapp: ansible-collection-redhat-leapp: Information disclosure via Leapp report tampering | known affected: 2 | 2026-07-31T19:08:13+00:00 | Vulnerability · Source |
| CVE-2026-63843 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring | known affected: 198 known not affected: 76 | 2026-07-31T19:03:52+00:00 | Vulnerability · Source |
| CVE-2026-63845 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring | known affected: 246 known not affected: 28 | 2026-07-31T18:58:13+00:00 | Vulnerability · Source |
| CVE-2026-63844 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring | known affected: 198 known not affected: 76 | 2026-07-31T18:58:11+00:00 | Vulnerability · Source |
| CVE-2026-63846 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring | known affected: 198 known not affected: 76 | 2026-07-31T18:53:12+00:00 | Vulnerability · Source |
| CVE-2026-17348 | redhat_vex | pgadmin4: pgAdmin 4: Unauthenticated access allows data manipulation and information disclosure | known not affected: 1 | 2026-07-31T18:53:11+00:00 | Vulnerability · Source |
| CVE-2026-63856 | redhat_vex | kernel: drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings | known affected: 198 known not affected: 76 | 2026-07-31T18:48:11+00:00 | Vulnerability · Source |
| CVE-2026-63855 | redhat_vex | kernel: drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings | known affected: 198 known not affected: 76 | 2026-07-31T18:43:12+00:00 | Vulnerability · Source |
| CVE-2026-63880 | redhat_vex | kernel: drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO | known affected: 198 known not affected: 76 | 2026-07-31T18:28:12+00:00 | Vulnerability · Source |
| CVE-2026-63881 | redhat_vex | kernel: drm/amdkfd: fix a vulnerability of integer overflow in kfd debugger | known affected: 274 | 2026-07-31T18:23:22+00:00 | Vulnerability · Source |
| CVE-2026-63882 | redhat_vex | kernel: drm/amdkfd: fix NULL pointer bug in svm_range_set_attr | known affected: 274 | 2026-07-31T18:19:18+00:00 | Vulnerability · Source |
| CVE-2026-46150 | redhat_vex | kernel: fanotify: fix false positive on permission events | fixed: 762 known affected: 64 | 2026-07-31T18:19:04+00:00 | Vulnerability · Source |
| CVE-2026-31692 | redhat_vex | kernel: rtnetlink: add missing netlink_ns_capable() check for peer netns | fixed: 459 known affected: 136 known not affected: 14 | 2026-07-31T18:19:00+00:00 | Vulnerability · Source |
| CVE-2026-43116 | redhat_vex | kernel: netfilter: ctnetlink: ensure safe access to master conntrack | fixed: 1980 known affected: 64 | 2026-07-31T18:19:00+00:00 | Vulnerability · Source |
| CVE-2026-64097 | redhat_vex | kernel: drm/amd/display: Validate GPIO pin LUT table size before iterating | known affected: 274 | 2026-07-31T18:13:21+00:00 | Vulnerability · Source |
| CVE-2026-9149 | redhat_vex | libsolv: Heap buffer overflow in libsolv repo_add_solv via negative maxsize from crafted .solv file | fixed: 149 known affected: 22 known not affected: 88 | 2026-07-31T17:51:19+00:00 | Vulnerability · Source |
| CVE-2026-9150 | redhat_vex | libsolv: Stack-based buffer overflow in libsolv's Debian metadata parser when handling SHA384/SHA512 checksums | fixed: 149 known affected: 17 known not affected: 93 | 2026-07-31T17:51:19+00:00 | Vulnerability · Source |
| CVE-2026-39819 | redhat_vex | cmd/go: golang: Go 'go bug' command: Arbitrary file overwrite via symlink attack | under investigation: 17 | 2026-07-31T17:48:33+00:00 | Vulnerability · Source |
| CVE-2019-19959 | suse_vex | SUSE CVE CVE-2019-19959 | known affected: 364 known not affected: 268 recommended: 440 | 2026-07-31T17:07:08+00:00 | Vulnerability · Source |
| CVE-2020-6581 | suse_vex | SUSE CVE CVE-2020-6581 | known not affected: 39 | 2026-07-31T17:07:02+00:00 | Vulnerability · Source |
| CVE-2020-8428 | suse_vex | SUSE CVE CVE-2020-8428 | known affected: 382 known not affected: 226 recommended: 1282 | 2026-07-31T17:06:58+00:00 | Vulnerability · Source |
| CVE-2020-9843 | suse_vex | SUSE CVE CVE-2020-9843 | known affected: 97 recommended: 1078 | 2026-07-31T17:06:56+00:00 | Vulnerability · Source |
| CVE-2020-12396 | suse_vex | SUSE CVE CVE-2020-12396 | known affected: 21 recommended: 9 | 2026-07-31T17:06:52+00:00 | Vulnerability · Source |
| CVE-2020-12402 | suse_vex | SUSE CVE CVE-2020-12402 | known affected: 500 known not affected: 7 recommended: 1816 | 2026-07-31T17:06:50+00:00 | Vulnerability · Source |
| CVE-2020-14765 | suse_vex | SUSE CVE CVE-2020-14765 | known not affected: 90 recommended: 654 | 2026-07-31T17:06:46+00:00 | Vulnerability · Source |
| CVE-2020-15658 | suse_vex | SUSE CVE CVE-2020-15658 | known affected: 24 recommended: 455 | 2026-07-31T17:06:43+00:00 | Vulnerability · Source |
| CVE-2020-16012 | suse_vex | SUSE CVE CVE-2020-16012 | known affected: 56 recommended: 419 | 2026-07-31T17:06:41+00:00 | Vulnerability · Source |
| CVE-2020-16155 | suse_vex | SUSE CVE CVE-2020-16155 | known not affected: 285 | 2026-07-31T17:06:40+00:00 | Vulnerability · Source |
| CVE-2020-16300 | suse_vex | SUSE CVE CVE-2020-16300 | known not affected: 172 recommended: 8 | 2026-07-31T17:06:38+00:00 | Vulnerability · Source |
| CVE-2020-17049 | suse_vex | SUSE CVE CVE-2020-17049 | known affected: 335 known not affected: 368 recommended: 722 | 2026-07-31T17:06:36+00:00 | Vulnerability · Source |
| CVE-2020-19185 | suse_vex | SUSE CVE CVE-2020-19185 | known affected: 1 known not affected: 634 | 2026-07-31T17:06:33+00:00 | Vulnerability · Source |
| CVE-2020-19715 | suse_vex | SUSE CVE CVE-2020-19715 | known not affected: 106 | 2026-07-31T17:06:31+00:00 | Vulnerability · Source |
| CVE-2020-21681 | suse_vex | SUSE CVE CVE-2020-21681 | recommended: 47 | 2026-07-31T17:06:29+00:00 | Vulnerability · Source |
| CVE-2020-25692 | suse_vex | SUSE CVE CVE-2020-25692 | known affected: 392 recommended: 854 | 2026-07-31T17:06:23+00:00 | Vulnerability · Source |
| CVE-2020-29573 | suse_vex | SUSE CVE CVE-2020-29573 | known affected: 330 known not affected: 60 recommended: 1236 | 2026-07-31T17:06:15+00:00 | Vulnerability · Source |
| CVE-2021-0326 | suse_vex | SUSE CVE CVE-2021-0326 | known not affected: 3 recommended: 99 | 2026-07-31T17:06:12+00:00 | Vulnerability · Source |
| CVE-2021-1788 | suse_vex | SUSE CVE CVE-2021-1788 | recommended: 1118 | 2026-07-31T17:06:11+00:00 | Vulnerability · Source |
| CVE-2021-1870 | suse_vex | SUSE CVE CVE-2021-1870 | recommended: 1020 | 2026-07-31T17:06:09+00:00 | Vulnerability · Source |
| CVE-2021-2372 | suse_vex | SUSE CVE CVE-2021-2372 | known not affected: 42 recommended: 467 | 2026-07-31T17:06:07+00:00 | Vulnerability · Source |
| CVE-2021-3639 | suse_vex | SUSE CVE CVE-2021-3639 | known affected: 1 recommended: 99 | 2026-07-31T17:06:05+00:00 | Vulnerability · Source |
| CVE-2021-3682 | suse_vex | SUSE CVE CVE-2021-3682 | known affected: 432 known not affected: 647 recommended: 1847 | 2026-07-31T17:06:03+00:00 | Vulnerability · Source |
| CVE-2021-3695 | suse_vex | SUSE CVE CVE-2021-3695 | known affected: 353 recommended: 724 | 2026-07-31T17:06:01+00:00 | Vulnerability · Source |
| CVE-2021-3999 | suse_vex | SUSE CVE CVE-2021-3999 | known affected: 339 recommended: 1452 | 2026-07-31T17:05:55+00:00 | Vulnerability · Source |
| CVE-2021-4069 | suse_vex | SUSE CVE CVE-2021-4069 | known affected: 363 known not affected: 15 recommended: 366 | 2026-07-31T17:05:52+00:00 | Vulnerability · Source |
| CVE-2021-20246 | suse_vex | SUSE CVE CVE-2021-20246 | known not affected: 130 recommended: 588 | 2026-07-31T17:05:49+00:00 | Vulnerability · Source |