OpenShift GitOps Operator Namespace Isolation Break

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2024-13484: 0.22% estimated exploitation activity in the next 30 days; percentile 13.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

28 Jan 2025, 18:31 UTC

Last modified by the source

21 Jul 2026, 15:01 UTC

Source last checked

26 Oct 2026, 15:27 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-58fx-7v9q-3g56

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-13484

Advisory: OpenShift GitOps Operator Namespace Isolation Break
IDs: CVE-2024-13484, GHSA-58fx-7v9q-3g56
Record: https://patchnext.com/advisories/cve-2024-13484 (revision 1, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/redhat-developer/gitops-operator 1.16.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/redhat-developer/gitops-operator: affected < 1.16.2; fixed in 1.16.2

## Suggested inspection (read-only)
- Go github.com/redhat-developer/gitops-operator: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/redhat-developer/gitops-operator.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-58fx-7v9q-3g56 (GitHub-reviewed advisory GHSA-58fx-7v9q-3g56 lists affected ranges: Go github.com/redhat-developer/gitops-operator >=0 <1.16.2)

Commands are suggestions: review each one before running it.