Skip to main content
CVE-2025-55190VulnerabilityPublished Updated

Red Hat Security Advisory: Red Hat OpenShift GitOps v1.19.1 security update

Affects Red HatSource GCVE Database

0

Mentioned vulnerabilities

Authoritative record:CVE-2025-55190· Critical 10.0

Not known to be exploited · public detection template (Nuclei) · CVSS 10.0 Critical : upgrade Red Hat to 3.2.7-r0 or 1.19.1 as a priority.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
5.6% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.7-r0, 1.19.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Red Hat to 3.2.7-r0 or 1.19.1.

Affected software

ProductAffectedFixed in
Red Hat Product Security Red HatAffected
  • <1.19.1
  • Red Hat
  • Red Hat OpenShift GitOps
  • Red Hat OpenShift GitOps 1.19
  • amd64
  • registry.redhat.io/openshift-gitops-1/argo-rollouts-rhel8@sha256:88d3d7cfa9a703b161eb6155eb959afe9ca3608214a58c11520bfda255b2adca_amd64
  • Red Hat OpenShift GitOps 1.17
  • registry.redhat.io/openshift-gitops-1/argo-rollouts-rhel8@sha256:f218700bb266c8a829f48204a6d1584dda3868d019f1dbb7f9253b431e668ce7_amd64
  • Red Hat OpenShift GitOps 1.15
  • registry.redhat.io/openshift-gitops-1/argo-rollouts-rhel8@sha256:b79b74a5d78853eb8021375ad077e132637cd2f88a5563b8859718f023a5368d_amd64
  • Red Hat OpenShift GitOps 1.16
  • registry.redhat.io/openshift-gitops-1/argo-rollouts-rhel8@sha256:48eee951cbabfec9d37ba7b04b241670f745cbc20eb565288c7171a34780223b_amd64
  • <3.2.7-r0
Fixed in
  • 1.19.1
  • 3.2.7-r0

AI-suggested

A security update is available in Red Hat OpenShift GitOps version 1.19.1 that addresses this vulnerability. Users should apply this update to remediate the issue. Currently, no effective mitigations meeting Red Hat's criteria for ease of use and applicability are available. Prior to updating, ensure all previously released errata relevant to your system have been applied. Refer to Red Hat's official advisory for detailed update instructions.

Description

An update is now available for Red Hat OpenShift GitOps. Bug Fix(es) and Enhancement(s): * GITOPS-8080 (CVE-2025-58183 openshift-gitops-1/argocd-rhel8: Unbounded allocation when parsing GNU sparse map [gitops-1.19]) * GITOPS-8083 (CVE-2025-58183 openshift-gitops-1/dex-rhel8: Unbounded allocation when parsing GNU sparse map [gitops-1.19]) * GITOPS-7849 (Cherry pick Repo Type Fix to Argo CD 3.1 stream) * GITOPS-7992 (openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition) * GITOPS-8225 (RC 1.19.0-2 : haproxy replica remains 1 with HA upgrade) * GITOPS-8249 (Prevent argoCD from automatically refreshing to gitops repository ) * GITOPS-8411 (CVE-2025-55190 still blocking due to github.com/argoproj/argo-cd/v2@v2.14.11 in gitops-rhel8:v1.18.1) * GITOPS-8535 (Show All Namespaces or Current Namespace Only option) * GITOPS-8591 (Reciving TargetDown after upgrading GitOps )

References

Community reviews

Loading reviews…