CVE-2025-10725

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2025-09-30. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-31761 (ENISA EUVD) · GHSA-g829-2387-h324 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Red Hat, Inc.) states them in the record's workaround: "The recommended fix is to upgrade to version 2.16.3."

A flaw was found in Red Hat Openshift AI Service. A low-privileged attacker with access to an authenticated account, for example as a data scientist using a standard Jupyter notebook, can escalate their privileges to a full cluster administrator. This allows for the complete compromise of the cluster's confidentiality, integrity, and availability. The attacker can steal sensitive data, disrupt all services, and take control of the underlying infrastructure, leading to a total breach of the platform and all applications hosted on it.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

September 30, 2025

Last Modified

April 15, 2026

Advisory Details (9)

Auto-updated Nov 2, 2026
Patch available. Sources: github_commit, github_pr, redhat.
GitHub pull request

remove useless kueue-batch-user-rolebinding

Fix merged in opendatahub-io/opendatahub-operator PR #2571 on 2025-09-30 — awaiting tagged release

https://github.com/opendatahub-io/opendatahub-operator/pull/2571
GitHub commit

commit 070057ebd088 (opendatahub-io/opendatahub-operator)

Fix landed in opendatahub-io/opendatahub-operator commit 070057ebd088 — awaiting tagged release

https://github.com/opendatahub-io/opendatahub-operator/commit/070057ebd0882be0e397bee1daa18c36374a03c0
Red Hat

2396641 – (CVE-2025-10725) CVE-2025-10725 openshift-ai: Overly Permissive ClusterRole Allows Authenticated Users to Escalate Privileges to Cluster Admin

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

CVE-2025-10725 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2025-10725
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:17501
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:16984
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:16983
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:16982
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:16981

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-rhel9-operator:v2.24.0-17592598402025-10-07redhat
redhatrhoai/odh-rhel8-operator:v2.16.3-17587158612025-09-29redhat
redhatrhoai/odh-rhel8-operator:v2.19.3-17587158712025-09-29redhat
redhatrhoai/odh-rhel9-operator:v2.21.1-17587158802025-09-29redhat
redhatrhoai/odh-rhel9-operator:v2.22.2-17587797692025-09-29redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 92× 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 100 of 304 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. None are among the latest 100 rows. The 204 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-10725?
CVE-2025-10725 is a critical-severity vulnerability; its CVE record was published on September 30, 2025. A flaw was found in Red Hat Openshift AI Service. A low-privileged attacker with access to an authenticated account, for example as a data scientist using a standard Jupyter notebook, can escalate their privileges to a full cluster administrator. This allows for the complete compromise of the…
When was CVE-2025-10725 made public?
CVE-2025-10725 was made public on September 29, 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 September 30, 2025. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-10725 actively exploited?
CVE-2025-10725 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-10725?
CVE-2025-10725 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-10725?
A fix for CVE-2025-10725 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Red Hat, Inc.) states them in the record's workaround: "The recommended fix is to upgrade to version 2.16.3." The vendor advisories EchelonGraph has for CVE-2025-10725 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-10725

Explore →

Is Your Infrastructure Affected by CVE-2025-10725?

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