gitoxide gix-fs before 0.23.0 contains a path validation bypass vulnerability in the worktree checkout mechanism that allows attackers to escape the worktree directory via symlink manipulation. During forced checkout with overwrite_existing enabled, attackers can craft malicious repository trees where symlink entries replace validated directories, causing subsequent files to be written outside the worktree through the symlink for code execution or file manipulation.
CVE-2026-100419
Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. A secondary CVSS source baseline 7.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.0
- EG Score
- 7.0HIGHhigh confidence
- EG Risk
- 48EG Risk 48/100CISA SSVC
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 computedSeverity70% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.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.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 25, 2026
Last Modified
September 28, 2026
Advisory Details (6)
Auto-updated Sep 25, 2026gitoxide gix-fs before 0.23.0 Worktree Escape via Symlink | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitoxide-gix-fs-before-0.23.0-worktree-escape-via-symlinkGitHub - GitoxideLabs/gitoxide: An idiomatic, lean, fast & safe pure Rust implementation of Git · GitHub
https://github.com/GitoxideLabs/gitoxideSymlink prefix-reuse allows worktree escape during checkout · Advisory · GitoxideLabs/gitoxide · GitHub
https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-f89h-2fjh-2r9qgitoxide/gix-fs/src/stack.rs at gix-fs-v0.22.1 · GitoxideLabs/gitoxide · GitHub
https://github.com/GitoxideLabs/gitoxide/blob/gix-fs-v0.22.1/gix-fs/src/stack.rs#L185-L196commit b62498378b8b (GitoxideLabs/gitoxide)
Patch available: GitoxideLabs/gitoxide gix-trace-v0.2.0 (contains commit b62498378b8b)
https://github.com/GitoxideLabs/gitoxide/commit/b62498378b8bc2c95863a044b700f2063b0b5875Force checkout replaces a directory with an attacker symlink while the prefix guard is disarmed, so the GHSA-f89h fix is bypassed and writes land outside the worktree · Advisory · GitoxideLabs/gitoxide · GitHub
https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-6p9q-f2xg-6pr5Vendor Advisories for CVE-2026-100419(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 34× in last 7d / 42× 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.
- 2026-10-04 01:42 UTCEG score recompute
- 2026-10-04 01:42 UTCVendor advisory
- 2026-10-04 01:42 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 12:36 UTCVendor advisory
- 2026-10-03 12:36 UTCGHSA enrichment
- 2026-10-02 23:29 UTCEG score recompute
- 2026-10-02 23:29 UTCVendor advisory
- 2026-10-02 23:28 UTCGHSA enrichment
- 2026-10-02 10:19 UTCVendor advisory
- 2026-10-02 10:19 UTCGHSA enrichment
- 2026-10-01 21:13 UTCEG score recompute
- 2026-10-01 21:13 UTCVendor advisory
- 2026-10-01 21:13 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 08:05 UTCVendor advisory
- 2026-10-01 08:05 UTCGHSA enrichment
- 2026-09-30 18:59 UTCEG score recompute
- 2026-09-30 18:59 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-30 05:53 UTCGHSA enrichment
- 2026-09-29 16:46 UTCEG score recompute
- 2026-09-29 16:46 UTCGHSA enrichment
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-29 03:33 UTCEG score recompute
Show 17 moreShow fewer
- 2026-09-29 03:33 UTCGHSA enrichment
- 2026-09-28 14:26 UTCEG score recompute
- 2026-09-28 14:26 UTCGHSA enrichment
- 2026-09-28 13:50 UTCEPSS rescore
- 2026-09-28 13:27 UTCEG score recompute
- 2026-09-28 13:27 UTCGHSA enrichment
- 2026-09-28 02:51 UTCEG score recompute
- 2026-09-28 02:51 UTCGHSA enrichment
- 2026-09-27 13:44 UTCGHSA enrichment
- 2026-09-27 00:37 UTCEG score recompute
- 2026-09-27 00:37 UTCGHSA enrichment
- 2026-09-26 15:58 UTCEPSS rescore
- 2026-09-26 11:31 UTCEG score recompute
- 2026-09-26 11:30 UTCGHSA enrichment
- 2026-09-25 22:22 UTCEG score recompute
- 2026-09-25 22:09 UTCEG score recompute
- 2026-09-25 22:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-100419?
When was CVE-2026-100419 disclosed?
Is CVE-2026-100419 actively exploited?
What is the CVSS score of CVE-2026-100419?
How do I remediate CVE-2026-100419?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-100419
Is Your Infrastructure Affected by CVE-2026-100419?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.