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
33%
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

(4 across 3 ecosystems)
crates.io(2)
PackageVulnerable rangeFixed inDependents
gitoxide—0.52.1—
gix—0.83.0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rust-gix0.69.1-1 ... 0.86.0-1 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rust-gix0.69.1-1 ... 0.73.0-4 (6 versions)0.83.0-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 38× in last 7d / 112× 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 112 total refreshes for this CVE.

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

Related CVEs(same vendor + 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 67.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