CVE-2026-82252

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

gitoxide before 0.52.1 follows symlinks when reading the worktree .gitmodules file, allowing attackers to inject out-of-repository bytes into submodule metadata. Attackers can create a malicious repository with a symlinked .gitmodules pointing outside the repository tree, causing gitoxide to parse arbitrary external files as submodule configuration and expose attacker-controlled name, path, and url values.

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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (2)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

gitoxide before 0.52.1 Repository Boundary Violation via symlinked .gitmodules | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitoxide-before-0.52.1-repository-boundary-violation-via-symlinked-gitmodules
github Patch Available🟡 PoC Available

symlinked .gitmodules is followed and parsed from outside the repository · Advisory · GitoxideLabs/gitoxide · GitHub

https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-pg4w-g64p-qwhj

Vendor Advisories for CVE-2026-82252(1)

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

Affected Packages

(2 across 1 ecosystem)
crates.io(2)
PackageVulnerable rangeFixed inDependents
gitoxide—0.52.1—
gix—0.83.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 20× 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-08-30 02:35 UTCEG score recompute
  2. 2026-08-30 02:34 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 14:23 UTCEG score recompute
  5. 2026-08-29 14:23 UTCGHSA enrichment
  6. 2026-08-29 13:45 UTCEG score recompute
  7. 2026-08-29 13:45 UTCGHSA enrichment
  8. 2026-08-29 12:20 UTCEG score recompute
  9. 2026-08-29 12:19 UTCGHSA enrichment
  10. 2026-08-29 11:58 UTCEG score recompute
  11. 2026-08-29 11:58 UTCGHSA enrichment
  12. 2026-08-29 07:08 UTCGHSA enrichment
  13. 2026-08-28 18:57 UTCGHSA enrichment
  14. 2026-08-28 16:36 UTCEG score recompute
  15. 2026-08-28 16:36 UTCGHSA enrichment
  16. 2026-08-28 15:37 UTCEG score recompute
  17. 2026-08-28 15:37 UTCGHSA enrichment
  18. 2026-08-28 12:22 UTCEG score recompute
  19. 2026-08-28 11:22 UTCEG score recompute
  20. 2026-08-28 11:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82252?
CVE-2026-82252 is a high vulnerability published on August 28, 2026. gitoxide before 0.52.1 follows symlinks when reading the worktree .gitmodules file, allowing attackers to inject out-of-repository bytes into submodule metadata. Attackers can create a malicious repository with a symlinked .gitmodules pointing outside the repository tree, causing gitoxide to parse…
When was CVE-2026-82252 disclosed?
CVE-2026-82252 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82252 actively exploited?
CVE-2026-82252 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 68.3% of all scored CVEs.
What is the CVSS score of CVE-2026-82252?
CVE-2026-82252 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-82252?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82252, 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-2026-82252

Explore →

Is Your Infrastructure Affected by CVE-2026-82252?

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

Start Free Scan →Browse All CVEs