CVE-2026-82253

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated
7.5EG
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.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

August 28, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Aug 28, 2026
Patch available. Sources: github.
Web page

gitoxide 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-bypass
GitHub advisoryMentions a patch (unverified)

Submodule 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-rf9w

Vendor Advisories for CVE-2026-82253(2)

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)
PackageVulnerable rangeFix by version rangeDependents
gix—
  • every version up to 0.83.0: fixed in 0.83.0
—
gix-validate—
  • every version up to 0.11.1: fixed in 0.11.1
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
rust-gix0.69.1-1 ... 0.87.1-1 (10 versions)
  • every version on: no fix on record
—
rust-gix-validate0.10.1-1, 0.11.1-1, 0.11.3-1, 0.11.4-1, 0.9.2-1
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
rust-gix0.69.1-1 ... 0.73.0-4 (6 versions)
  • every version up to 0.83.0-1: fixed in 0.83.0-1
—
rust-gix-validate0.10.1-1, 0.9.2-1
  • every version up to 0.11.1-1: fixed in 0.11.1-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 153× 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 232 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 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-82253?
CVE-2026-82253 is a high-severity vulnerability; its CVE record was published on August 28, 2026. 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;…
When was CVE-2026-82253 made public?
CVE-2026-82253 was made public on April 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of August 31, 2026; the record at its source may have been updated since.
Is CVE-2026-82253 actively exploited?
CVE-2026-82253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82253?
CVE-2026-82253 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82253?
A fix for CVE-2026-82253 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82253 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-2026-82253

Explore →

Is Your Infrastructure Affected by CVE-2026-82253?

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

Book a Demo →Browse All CVEs