VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100518 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-76139 | redhat_vex | acm-operator-bundle: acm-operator-bundle: Bundle build execs unpinned stolostron/release@master with full build credentials | fixed: 6 | 2026-10-16T15:31:08+00:00 | Vulnerability · Source |
| CVE-2026-75569 | redhat_vex | mce-operator-bundle: All GitHub Actions pinned by mutable tag, not commit SHA | fixed: 6 | 2026-10-16T15:31:04+00:00 | Vulnerability · Source |
| CVE-2026-73269 | redhat_vex | cluster-curator-controller: cluster-curator-controller: tenant-controllable trigger creates ClusterRoleBinding granting cluster-wide secrets access to namespace-local SA | fixed: 24 known not affected: 704 | 2026-10-16T15:31:01+00:00 | Vulnerability · Source |
| CVE-2026-73268 | redhat_vex | cluster-curator-controller: cluster-curator-controller: spec.install.overrideJob allows arbitrary Job spec injection | fixed: 24 known not affected: 704 | 2026-10-16T15:30:57+00:00 | Vulnerability · Source |
| CVE-2026-73267 | redhat_vex | clusterclaims-controller: ManagedCluster deletion keyed solely on ClusterClaim.Spec.Namespace with no local ownership check | fixed: 24 known not affected: 704 | 2026-10-16T15:30:53+00:00 | Vulnerability · Source |
| CVE-2026-73266 | redhat_vex | clusterclaims-controller: Confused deputy: tenant-controlled ClusterClaim labels propagated to ManagedCluster, enabling cross-tenant ManagedClusterSet join | fixed: 24 known not affected: 704 | 2026-10-16T15:30:46+00:00 | Vulnerability · Source |
| CVE-2026-73137 | redhat_vex | multicloud-operators-subscription: multicloud-operators-subscription: cross-namespace Secret exfiltration via HelmRelease.repo.secretRef.namespace | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:44+00:00 | Vulnerability · Source |
| CVE-2026-73122 | redhat_vex | multicloud-operators-channel: multicloud-operators-channel: auto-generated Role grants every managed-cluster agent secrets:get,list,watch in Channel namespaces | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:39+00:00 | Vulnerability · Source |
| CVE-2026-72526 | redhat_vex | multicloud-integrations: multicloud-integrations: pull-model propagation allows hub tenant to target arbitrary spoke cluster via unvalidated ocm-managed-cluster annotation | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:33+00:00 | Vulnerability · Source |
| CVE-2026-72508 | redhat_vex | multicloud-operators-subscription: multicloud-operators-subscription: hub and spoke ServiceAccounts bound to wildcard RBAC (*/*/*) | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:29+00:00 | Vulnerability · Source |
| CVE-2026-71472 | redhat_vex | acm-search-v2-rhel9: search-v2-operator: Shell-command and SQL injection in postgresql-start.sh via CR-supplied WORK_MEM | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:22+00:00 | Vulnerability · Source |
| CVE-2026-71471 | redhat_vex | acm-search-v2-rhel9: search-v2-operator: Hub Search CR Collector.ImageOverride propagated to every spoke as arbitrary container image | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:18+00:00 | Vulnerability · Source |
| CVE-2026-71470 | redhat_vex | acm-search-v2-rhel9: search-v2-operator: Search CR imageOverride/arguments/envVar flow unsanitized into pods running impersonating SA | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:16+00:00 | Vulnerability · Source |
| CVE-2026-71469 | redhat_vex | acm-search-v2-api-rhel9: search-v2-api: Unbounded tokenReviews cache allows unauthenticated memory-exhaustion DoS | fixed: 24 known not affected: 1048 | 2026-10-16T15:30:10+00:00 | Vulnerability · Source |
| CVE-2026-70496 | redhat_vex | search-v2-operator: search-v2-operator: operator ClusterRole is cluster-admin equivalent via impersonate, RBAC write, CSR approve, and ManifestWork | fixed: 28 known not affected: 1045 | 2026-10-16T15:30:04+00:00 | Vulnerability · Source |
| CVE-2026-70495 | redhat_vex | search-v2-operator: search-v2-operator: cluster-wide impersonate on users/groups shared across 4 pods grants hub system:masters | fixed: 24 known affected: 1 known not affected: 1048 | 2026-10-16T15:29:59+00:00 | Vulnerability · Source |
| CVE-2026-70398 | redhat_vex | multicloud-integrations: multicloud-integrations: GitOpsCluster.spec.argoServer.argoNamespace writes spoke bearer tokens to attacker-chosen namespace | fixed: 24 known not affected: 1048 | 2026-10-16T15:29:56+00:00 | Vulnerability · Source |
| CVE-2026-90011 | redhat_vex | kernel: scsi: target: iscsi: Reserve a terminator byte for the login payload | known affected: 263 known not affected: 14 | 2026-10-16T15:29:10+00:00 | Vulnerability · Source |
| CVE-2026-88815 | redhat_vex | perl-DBI: perl-DBI: Denial of Service via invalid memory read during numeric type casting | fixed: 36 known affected: 4 | 2026-10-16T15:29:04+00:00 | Vulnerability · Source |
| CVE-2026-102560 | redhat_vex | libsoup: libsoup: Heap buffer overflow during outgoing permessage-deflate buffer growth | fixed: 39 known affected: 9 | 2026-10-16T15:28:28+00:00 | Vulnerability · Source |
| CVE-2026-102331 | redhat_vex | chromium-browser: angle: chromium-browser: arbitrary code execution via buffer overflow in ANGLE | known affected: 27 known not affected: 18 | 2026-10-16T15:28:18+00:00 | Vulnerability · Source |
| CVE-2022-0847 | suse_vex | SUSE CVE CVE-2022-0847 | known affected: 204 known not affected: 111 recommended: 1321 | 2026-10-16T15:02:23+00:00 | Vulnerability · Source |
| CVE-2022-0850 | suse_vex | SUSE CVE CVE-2022-0850 | known affected: 347 known not affected: 82 recommended: 983 | 2026-10-16T15:02:21+00:00 | Vulnerability · Source |
| CVE-2022-0854 | suse_vex | SUSE CVE CVE-2022-0854 | known affected: 149 known not affected: 276 recommended: 1259 | 2026-10-16T15:02:19+00:00 | Vulnerability · Source |
| CVE-2022-0897 | suse_vex | SUSE CVE CVE-2022-0897 | known affected: 394 known not affected: 16 recommended: 1422 | 2026-10-16T15:02:17+00:00 | Vulnerability · Source |
| CVE-2022-0909 | suse_vex | SUSE CVE CVE-2022-0909 | known affected: 439 known not affected: 19 recommended: 239 | 2026-10-16T15:02:15+00:00 | Vulnerability · Source |
| CVE-2022-0934 | suse_vex | SUSE CVE CVE-2022-0934 | recommended: 106 | 2026-10-16T15:02:13+00:00 | Vulnerability · Source |
| CVE-2022-1011 | suse_vex | SUSE CVE CVE-2022-1011 | known affected: 347 known not affected: 61 recommended: 1704 | 2026-10-16T15:02:11+00:00 | Vulnerability · Source |
| CVE-2022-1012 | suse_vex | SUSE CVE CVE-2022-1012 | known affected: 225 recommended: 1343 | 2026-10-16T15:02:08+00:00 | Vulnerability · Source |
| CVE-2022-1015 | suse_vex | SUSE CVE CVE-2022-1015 | known affected: 32 known not affected: 18 recommended: 335 | 2026-10-16T15:02:07+00:00 | Vulnerability · Source |
| CVE-2022-1043 | suse_vex | SUSE CVE CVE-2022-1043 | known not affected: 401 | 2026-10-16T15:02:05+00:00 | Vulnerability · Source |
| CVE-2022-1048 | suse_vex | SUSE CVE CVE-2022-1048 | known affected: 180 known not affected: 14 recommended: 2051 | 2026-10-16T15:02:03+00:00 | Vulnerability · Source |
| CVE-2022-1050 | suse_vex | SUSE CVE CVE-2022-1050 | known affected: 415 known not affected: 526 recommended: 1394 | 2026-10-16T15:02:00+00:00 | Vulnerability · Source |
| CVE-2022-1053 | suse_vex | SUSE CVE CVE-2022-1053 | recommended: 224 | 2026-10-16T15:01:58+00:00 | Vulnerability · Source |
| CVE-2022-1056 | suse_vex | SUSE CVE CVE-2022-1056 | known affected: 439 known not affected: 19 recommended: 230 | 2026-10-16T15:01:57+00:00 | Vulnerability · Source |
| CVE-2022-1115 | suse_vex | SUSE CVE CVE-2022-1115 | known not affected: 415 recommended: 279 | 2026-10-16T15:01:55+00:00 | Vulnerability · Source |
| CVE-2022-1116 | suse_vex | SUSE CVE CVE-2022-1116 | known affected: 368 known not affected: 326 recommended: 736 | 2026-10-16T15:01:53+00:00 | Vulnerability · Source |
| CVE-2022-1122 | suse_vex | SUSE CVE CVE-2022-1122 | known affected: 0 known not affected: 181 recommended: 220 | 2026-10-16T15:01:52+00:00 | Vulnerability · Source |
| CVE-2022-1154 | suse_vex | SUSE CVE CVE-2022-1154 | known affected: 0 known not affected: 275 recommended: 48 | 2026-10-16T15:01:50+00:00 | Vulnerability · Source |
| CVE-2022-1184 | suse_vex | SUSE CVE CVE-2022-1184 | known affected: 194 known not affected: 2 recommended: 1865 | 2026-10-16T15:01:48+00:00 | Vulnerability · Source |
| CVE-2022-1195 | suse_vex | SUSE CVE CVE-2022-1195 | known affected: 216 known not affected: 353 recommended: 796 | 2026-10-16T15:01:46+00:00 | Vulnerability · Source |
| CVE-2022-1196 | suse_vex | SUSE CVE CVE-2022-1196 | known affected: 3 known not affected: 126 recommended: 396 | 2026-10-16T15:01:44+00:00 | Vulnerability · Source |
| CVE-2022-1210 | suse_vex | SUSE CVE CVE-2022-1210 | known affected: 562 known not affected: 309 recommended: 95 | 2026-10-16T15:01:42+00:00 | Vulnerability · Source |
| CVE-2022-1271 | suse_vex | SUSE CVE CVE-2022-1271 | known affected: 347 known not affected: 105 recommended: 960 | 2026-10-16T15:01:39+00:00 | Vulnerability · Source |
| CVE-2022-1280 | suse_vex | SUSE CVE CVE-2022-1280 | known affected: 216 known not affected: 228 recommended: 1083 | 2026-10-16T15:01:37+00:00 | Vulnerability · Source |
| CVE-2022-1292 | suse_vex | SUSE CVE CVE-2022-1292 | known affected: 213 known not affected: 104 recommended: 1115 | 2026-10-16T15:01:36+00:00 | Vulnerability · Source |
| CVE-2022-1304 | suse_vex | SUSE CVE CVE-2022-1304 | known affected: 351 known not affected: 3 recommended: 667 | 2026-10-16T15:01:34+00:00 | Vulnerability · Source |
| CVE-2022-1328 | suse_vex | SUSE CVE CVE-2022-1328 | known affected: 443 recommended: 130 | 2026-10-16T15:01:33+00:00 | Vulnerability · Source |
| CVE-2022-1343 | suse_vex | SUSE CVE CVE-2022-1343 | known affected: 0 known not affected: 707 recommended: 146 | 2026-10-16T15:01:31+00:00 | Vulnerability · Source |
| CVE-2022-1353 | suse_vex | SUSE CVE CVE-2022-1353 | known affected: 354 known not affected: 51 recommended: 1012 | 2026-10-16T15:01:29+00:00 | Vulnerability · Source |