CVE-2025-13888

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in OpenShift GitOps. Namespace admins can create ArgoCD Custom Resources (CRs) that trick the system into granting them elevated permissions in other namespaces, including privileged namespaces. An authenticated attacker can then use these elevated permissions to create privileged workloads that run on master nodes, effectively giving them root access to the entire cluster.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 15, 2025

Last Modified

October 7, 2026

Advisory Details (9)

Auto-updated Aug 1, 2026
Patch available. Sources: redhat, github_commit, github_pr, github_release.
GitHub release Patch Available

v1.16.2

Patch available: redhat-developer/gitops-operator v1.16.2

https://github.com/redhat-developer/gitops-operator/releases/tag/v1.16.2
GitHub pull request Patch Available

cherrypick fix CVE namespace-isolation break

Patch available: redhat-developer/gitops-operator v1.16.2 (PR #897 merged 2025-05-26)

https://github.com/redhat-developer/gitops-operator/pull/897
GitHub commit Patch Available

commit bc6ac3e03d7c (redhat-developer/gitops-operator)

Patch available: redhat-developer/gitops-operator v1.16.2 (contains commit bc6ac3e03d7c)

https://github.com/redhat-developer/gitops-operator/commit/bc6ac3e03d7c8b3db5d8f1770c868396a4c2dcef
Red Hat

2418361 – (CVE-2025-13888) CVE-2025-13888 openshift-gitops-operator: OpenShift GitOps: Namespace Admin Cluster Takeover via Privileged Jobs

https://bugzilla.redhat.com/show_bug.cgi?id=2418361
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2025-13888
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:1017
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:23207
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:23206
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:23203

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-gitops-1/gitops-rhel8-operator:17688810332026-01-22redhat
redhatopenshift-gitops-1/gitops-rhel8-operator:1.172025-12-15redhat
redhatopenshift-gitops-1/gitops-rhel8-operator:1.182025-12-15redhat
redhatopenshift-gitops-1/gitops-rhel8-operator:1.162025-12-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/redhat-developer/gitops-operator—
  • every version up to 1.16.2: fixed in 1.16.2
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 216 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 18:06 UTCEG score recompute
  2. 2026-10-15 18:06 UTCVendor advisory
  3. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-14 11:54 UTCEG score recompute
  6. 2026-10-14 11:54 UTCVendor advisory
  7. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-13 11:15 UTCVendor advisory
  9. 2026-10-12 17:23 UTCEG score recompute
  10. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-12 12:20 UTCVendor advisory
  12. 2026-10-11 20:54 UTCEG score recompute
  13. 2026-10-11 19:04 UTCEG score recompute
  14. 2026-10-11 15:45 UTCEG score recompute
  15. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-07 11:22 UTCEG score recompute
  21. 2026-10-07 11:22 UTCVendor advisory
  22. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.7% · 51st percentile
Show 72 more
  1. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-09-30 20:24 UTCEG score recompute
  3. 2026-09-30 20:24 UTCVendor advisory
  4. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  8. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-09-14 08:50 UTCOSV refresh
  16. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  26. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  27. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  28. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  29. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  30. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-08-26 10:02 UTCOSV refresh
  35. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  39. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  40. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  42. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  43. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  44. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  45. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  47. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  48. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  49. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  50. 2026-08-09 23:52 UTCEG score recompute
  51. 2026-08-09 23:52 UTCVendor advisory
  52. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  53. 2026-08-08 06:41 UTCEG score recompute
  54. 2026-08-08 06:41 UTCVendor advisory
  55. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  56. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  57. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  58. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  59. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  60. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  61. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  62. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  63. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  64. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  65. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  66. 2026-07-27 14:12 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  67. 2026-07-27 05:09 UTCOSV refresh
  68. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  69. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  70. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  71. 2026-07-23 14:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  72. 2026-07-23 02:49 UTCEG score recompute

Frequently asked(5)

What is CVE-2025-13888?
CVE-2025-13888 is a critical-severity vulnerability; its CVE record was published on December 15, 2025. A flaw was found in OpenShift GitOps. Namespace admins can create ArgoCD Custom Resources (CRs) that trick the system into granting them elevated permissions in other namespaces, including privileged namespaces. An authenticated attacker can then use these elevated permissions to create privileged…
When was CVE-2025-13888 made public?
CVE-2025-13888 was made public on December 15, 2025: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on December 15, 2025. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2025-13888 actively exploited?
CVE-2025-13888 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-13888?
CVE-2025-13888 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-13888?
A fix for CVE-2025-13888 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-13888 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-13888

Explore →

Is Your Infrastructure Affected by CVE-2025-13888?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.