CVE-2025-24890

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity68% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. 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_pr 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 Patch Available🟡 PoC Available

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(1)

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

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
gix-sec—0.13.3—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-19 03:51 UTCEG score recompute
  2. 2026-09-19 03:51 UTCVendor advisory
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 01:44 UTCEG score recompute
  5. 2026-09-18 01:44 UTCVendor advisory
  6. 2026-09-16 23:37 UTCEG score recompute
  7. 2026-09-16 23:37 UTCVendor advisory
  8. 2026-09-16 14:06 UTCEPSS rescore
  9. 2026-09-16 05:13 UTCEPSS rescore
  10. 2026-09-15 21:30 UTCVendor advisory
  11. 2026-09-14 16:26 UTCEG score recompute
  12. 2026-09-09 17:24 UTCEG score recompute

Frequently asked(5)

What is CVE-2025-24890?
CVE-2025-24890 is a medium vulnerability 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 CVE-2025-24890 disclosed?
CVE-2025-24890 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24890 actively exploited?
CVE-2025-24890 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.1% of all scored CVEs.
What is the CVSS score of CVE-2025-24890?
CVE-2025-24890 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2025-24890?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24890, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs