OpenShift GitOps Operator Namespace Isolation Break
Published Jan 28, 2025 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
OpenShift GitOps Operator Namespace Isolation Break
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A flaw was found in openshift-gitops-operator-container. The openshift.io/cluster-monitoring label is applied to all namespaces that deploy an ArgoCD CR instance, allowing the namespace to create a rogue PrometheusRule. This issue can have adverse effects on the platform monitoring stack, as the rule is rolled out cluster-wide when the label is applied.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2025:7753 ↗
- RHSA-2025:8274 ↗
- RHSA-2025:9506 ↗
- access.redhat.com ↗
- RHBZ#2269376 ↗
- Source repository ↗
- Source repository ↗
- Source repository ↗
- Source repository ↗
Record history
Published Jan 28, 2025 · Last refreshed Nov 3, 2026