gitoxide (Rust crates gix <= 0.72.0 and gix-validate <= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of '..' via name.find(b".."), allowing crafted names such as 'a..b/../../../.git/' to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository's git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.
CVE-2026-82253
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 31, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026gitoxide before 0.82.0 Path Traversal via Submodule Name Validation Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitoxide-before-0.82.0-path-traversal-via-submodule-name-validation-bypassSubmodule name validation bypass + trust inheritance flaw enables path traversal and credential disclosure · Advisory · GitoxideLabs/gitoxide · GitHub
https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-p3hw-mv63-rf9wVendor Advisories for CVE-2026-82253(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(6 across 3 ecosystems)
crates.io(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gix | — | 0.83.0 | — |
| gix-validate | — | 0.11.1 | — |
Debian:13(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust-gix | 0.69.1-1 ... 0.86.0-1 (9 versions) | — | — |
| rust-gix-validate | 0.10.1-1, 0.11.1-1, 0.11.3-1, 0.9.2-1 | — | — |
Debian:14(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rust-gix | 0.69.1-1 ... 0.73.0-4 (6 versions) | 0.83.0-1 | — |
| rust-gix-validate | 0.10.1-1, 0.9.2-1 | 0.11.1-1 | — |
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 39× in last 7d / 108× 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.
Showing the most recent 100 of 108 total refreshes for this CVE.
- 2026-09-19 10:01 UTCVendor advisory
- 2026-09-19 10:01 UTCGHSA enrichment
- 2026-09-18 21:28 UTCEG score recompute
- 2026-09-18 21:28 UTCVendor advisory
- 2026-09-18 21:28 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 09:08 UTCVendor advisory
- 2026-09-18 09:08 UTCGHSA enrichment
- 2026-09-17 20:51 UTCEG score recompute
- 2026-09-17 20:51 UTCVendor advisory
- 2026-09-17 20:51 UTCGHSA enrichment
- 2026-09-17 07:20 UTCVendor advisory
- 2026-09-17 07:19 UTCGHSA enrichment
- 2026-09-16 18:58 UTCEG score recompute
- 2026-09-16 18:58 UTCVendor advisory
- 2026-09-16 18:58 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 04:32 UTCVendor advisory
- 2026-09-16 04:32 UTCGHSA enrichment
- 2026-09-15 16:15 UTCVendor advisory
- 2026-09-15 16:15 UTCGHSA enrichment
- 2026-09-15 03:58 UTCEG score recompute
- 2026-09-15 03:58 UTCVendor advisory
- 2026-09-15 03:58 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 15:39 UTCVendor advisory
- 2026-09-14 15:39 UTCGHSA enrichment
- 2026-09-14 03:22 UTCEG score recompute
- 2026-09-14 03:22 UTCVendor advisory
- 2026-09-14 03:22 UTCGHSA enrichment
- 2026-09-13 15:05 UTCVendor advisory
- 2026-09-13 15:05 UTCGHSA enrichment
- 2026-09-13 02:49 UTCEG score recompute
- 2026-09-13 02:49 UTCVendor advisory
- 2026-09-13 02:49 UTCGHSA enrichment
- 2026-09-12 14:32 UTCVendor advisory
- 2026-09-12 14:32 UTCGHSA enrichment
- 2026-09-12 02:15 UTCEG score recompute
- 2026-09-12 02:15 UTCVendor advisory
- 2026-09-12 02:15 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 13:58 UTCEG score recompute
- 2026-09-11 13:58 UTCGHSA enrichment
- 2026-09-11 01:41 UTCGHSA enrichment
- 2026-09-10 13:24 UTCEG score recompute
- 2026-09-10 13:24 UTCGHSA enrichment
- 2026-09-10 01:07 UTCGHSA enrichment
- 2026-09-09 12:50 UTCVendor advisory
- 2026-09-09 12:50 UTCGHSA enrichment
- 2026-09-09 00:32 UTCEG score recompute
- 2026-09-09 00:32 UTCVendor advisory
- 2026-09-09 00:32 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 12:15 UTCVendor advisory
- 2026-09-08 12:15 UTCGHSA enrichment
- 2026-09-07 23:54 UTCEG score recompute
- 2026-09-07 23:54 UTCVendor advisory
- 2026-09-07 23:54 UTCGHSA enrichment
- 2026-09-07 11:35 UTCVendor advisory
- 2026-09-07 11:35 UTCGHSA enrichment
- 2026-09-06 23:19 UTCEG score recompute
- 2026-09-06 23:19 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 11:00 UTCGHSA enrichment
- 2026-09-05 22:43 UTCEG score recompute
- 2026-09-05 22:43 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 10:25 UTCGHSA enrichment
- 2026-09-04 22:07 UTCEG score recompute
- 2026-09-04 22:06 UTCGHSA enrichment
- 2026-09-04 09:45 UTCEG score recompute
- 2026-09-04 09:45 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 21:27 UTCGHSA enrichment
- 2026-09-03 09:08 UTCGHSA enrichment
- 2026-09-02 20:51 UTCEG score recompute
- 2026-09-02 20:50 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 08:32 UTCGHSA enrichment
- 2026-09-01 20:11 UTCEG score recompute
- 2026-09-01 20:11 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 07:54 UTCEG score recompute
- 2026-09-01 07:54 UTCGHSA enrichment
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 19:32 UTCEG score recompute
- 2026-08-31 19:32 UTCGHSA enrichment
- 2026-08-31 18:57 UTCEG score recompute
- 2026-08-31 18:57 UTCGHSA enrichment
- 2026-08-31 08:31 UTCGHSA enrichment
- 2026-08-30 20:08 UTCEG score recompute
- 2026-08-30 20:08 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 07:51 UTCEG score recompute
- 2026-08-30 07:51 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-82253?
When was CVE-2026-82253 disclosed?
Is CVE-2026-82253 actively exploited?
What is the CVSS score of CVE-2026-82253?
How do I remediate CVE-2026-82253?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82253
Is Your Infrastructure Affected by CVE-2026-82253?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.