CVE-2025-24890

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

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

Score 6.8 from GitHub Security Advisory (severity: MODERATE) published 2026-09-09. A secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-210908 (ENISA EUVD) · GHSA-7rhf-42qf-vrvc (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

gitoxide is an implementation of git written in Rust. Prior to 0.13.3, the gix-sec crate on Windows incorrectly treats repositories controlled by another user as trusted when an administrator runs a dependent program with an unfiltered elevated token. In gix-sec/src/identity.rs, gix_sec::identity::is_path_owned_by_current_user obtains folder_owner and token_owner, but its administrator-specific IsWellKnownSid and CheckTokenMembership checks examine the running token rather than confirming the directory owner. This bypasses safe.directory-style protection for repositories owned and configured by a limited user, allowing repository configuration or hooks to execute commands with the administrator's privileges when an affected operation is performed. Exploitation requires Windows, an elevated administrator, a program that relies on gix-sec trust results, and interaction with a repository controlled by another user. An unelevated UAC process is not affected, and cloning is not affected because repository configuration and hooks are not copied. This issue is fixed in version 0.13.3.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
47
EG Risk 47/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)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
5th
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 (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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 9, 2026

Last Modified

October 14, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

gix-sec v0.13.3

Patch available: GitoxideLabs/gitoxide gix-sec-v0.13.3

https://github.com/GitoxideLabs/gitoxide/releases/tag/gix-sec-v0.13.3
GitHub commit Patch Available

commit 39e37482d6f8 (GitoxideLabs/gitoxide)

Patch available: GitoxideLabs/gitoxide gix-ref-v0.67.1 (contains commit 39e37482d6f8)

https://github.com/GitoxideLabs/gitoxide/commit/39e37482d6f884bf4765dbe9c95a93dc2a92e559
GitHub pull request Patch Available

fix: make `gix-sec` identity check on Windows similar to Git for Windows

Patch available: GitoxideLabs/gitoxide gix-ref-v0.67.1 (PR #2510 merged 2026-04-24)

https://github.com/GitoxideLabs/gitoxide/pull/2510
GitHub advisoryMentions a patch (unverified)

gix-sec safe.directory protections absent for elevated administrators · Advisory · GitoxideLabs/gitoxide · GitHub

https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-7rhf-42qf-vrvc

Vendor Advisories for CVE-2025-24890(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustgix-sec @ 0.13.3 (fixes <= 0.13.2)—ghsa

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)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
gix-sec—
  • every version up to 0.13.3: fixed in 0.13.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 51× 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 98 of 103 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 5 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-24890?
CVE-2025-24890 is a medium-severity vulnerability; its CVE record was published on September 9, 2026. gitoxide is an implementation of git written in Rust. Prior to 0.13.3, the gix-sec crate on Windows incorrectly treats repositories controlled by another user as trusted when an administrator runs a dependent program with an unfiltered elevated token. In gix-sec/src/identity.rs,…
When was the CVE record for CVE-2025-24890 published?
The CVE record for CVE-2025-24890 was published on September 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2025-24890 actively exploited?
CVE-2025-24890 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-24890?
CVE-2025-24890 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-24890?
A fix for CVE-2025-24890 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-24890 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-24890

Explore →

Is Your Infrastructure Affected by CVE-2025-24890?

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