CVE-2024-13484VulnerabilityPublished 24 Jun 2025Updated 6 Sep 2026

Red Hat Security Advisory: Red Hat OpenShift GitOps security update

Affects Red HatSource GCVE Database

Not known to be exploited : upgrade to 1.16.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.16.2

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Red Hat to 1.16.2.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=1.16.0 <1.16.2 Red Hat Red Hat OpenShift GitOps Red Hat OpenShift GitOps 1.16 amd64 registry.redhat.io/openshift-gitops-1/argocd-rhel8@sha256:66a05dbe2c838e38fd4ba7634f3e2687017dc75acf1226e16c7046697c2ec6a6_amd64	Fixed in 1.16.2

AI-suggested

Red Hat has released an official security update in Red Hat OpenShift GitOps version 1.16.2 that fixes this vulnerability. Applying this update is the recommended remediation. No other mitigation meeting Red Hat's criteria for ease of use and applicability is currently available. Users should ensure all relevant errata are applied before updating. Since this is not a cloud service, remediation is the responsibility of the system administrator.

Description

An update is now available for Red Hat OpenShift GitOps. Security Fix(es): * openshift-gitops-operator-container: Namespace Isolation Break [gitops-1.16](CVE-2024-13484) Bug Fix(es): * Gitops operator is not accepting regular expression in sourceNamespaces - Application in non-controlplane namespaces (GITOPS-6675) * gitops-plugin Pods should comply with the Pod Security restricted policy (GITOPS-6777) * Missing ArgoCD commit ID in UI (GITOPS-6896)

Impact

If exploited, this vulnerability allows a local attacker with admin privileges to create rogue PrometheusRules that propagate cluster-wide, potentially disrupting or manipulating the platform monitoring stack. This can lead to confidentiality, integrity, and availability impacts on monitoring data and operations. However, the requirement for local admin privileges limits the risk to trusted users with elevated access.

Summary

CVE-2024-13484 is a namespace isolation break in the openshift-gitops-operator-container where the openshift.io/cluster-monitoring label is applied broadly to namespaces with ArgoCD CR instances. This permits those namespaces to create PrometheusRules that are rolled out cluster-wide, potentially impacting the platform monitoring stack. Exploitation requires local administrative access, which restricts the vulnerability's exploitability. Red Hat has issued a security update in OpenShift GitOps version 1.16.2 to fix this issue. No effective mitigation other than applying the update is currently available according to Red Hat Product Security.

CWE-668Exposure of Resource to Wrong Sphere (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 18:22 UTC

WeaknessesCWE-668

Technical details

References

Community reviews

Related threats