CVSS 3.1
6.8 mediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NMedium (6.8). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NExplain CVE-2026-107176 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107176?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107176?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107176 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Red Hat OpenShift Container Platform 4.19 | 1793123280 |
| Red Hat OpenShift Container Platform 4.20 | 1792826398 |
| Red Hat OpenShift Container Platform 4.21 | 1792852494 |
| Red Hat OpenShift Container Platform 4.22 | 1792770602 |
Red Hat rates this Moderate.
A flaw was found in the cluster-samples-operator where the RBAC Role `coreos-pull-secret-reader` (https://github.com/openshift/cluster-samples-operator/blob/release-5.1/manifests/05-kube-system-rbac.yaml#L1-L17) grants overly broad read access to secrets in the `openshift-config` namespace. The Role allows `get`, `list`, and `watch` on all `secrets` resources without a `resourceNames` restriction, although the operator only reads the single secret named `pull-secret` (https://github.com/openshift/cluster-samples-operator/blob/release-5.1/pkg/metrics/metrics.go#L182). Exploitation requires a prior compromise of the samples-operator pod or its service account token. Red Hat rates this as Moderate impact because the excessive RBAC permissions can only be leveraged after an attacker gains code execution within the operator pod or access to the service account token through a separate vulnerability.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.20 | openshift4/ose-cluster-samples-rhel9-operator:1792826398 | Fixed 2026-10-26 | RHSA-2026:89341 |
| Red Hat OpenShift Container Platform 4.21 | openshift4/ose-cluster-samples-rhel9-operator:1792852494 | Fixed 2026-10-26 | RHSA-2026:89626 |
| Red Hat OpenShift Container Platform 4.22 | openshift4/ose-cluster-samples-rhel9-operator:1792770602 | Fixed 2026-10-27 | RHSA-2026:89198 |
| Red Hat OpenShift Container Platform 4 | openshift4/ose-cluster-samples-operator | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift5/ose-cluster-samples-rhel9-operator | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107176.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.