CVE-2026-40034

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-26. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.8EG
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.8Exploit: Elevated riskExposed: 0

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

gix-submodule before 0.29.0 (gitoxide before 0.5.21, gix before 0.84.0) incorrectly validates the update field in .gitmodules, allowing attackers to bypass the CommandForbiddenInModulesConfiguration guard when a submodule has been initialized with only partial configuration in .git/config. An attacker can inject arbitrary shell commands via the update field in .gitmodules that will be executed when Submodule::update() is called on a previously-initialized submodule, enabling remote code execution.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 24, 2026

Advisory Details (5)

Auto-updated May 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

`gix-submodule` - `.gitmodules` can bypass `update = !command` trust check · Advisory · GitoxideLabs/gitoxide · GitHub

https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-f26g-jm89-4g65
generic

gitoxide - Command Injection via Partial .gitmodules Override in gix-submodule | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitoxide-command-injection-via-partial-gitmodules-override-in-gix-submodule
generic

ANT-2026-6SNS6KMP · GitoxideLabs/gitoxide

https://red.anthropic.com/2026/cvd/findings/ANT-2026-6SNS6KMP
github_commit Patch Available

commit dd5c18d9e526 (GitoxideLabs/gitoxide)

Patch available: GitoxideLabs/gitoxide gix-trace-v0.1.20 (contains commit dd5c18d9e526)

https://github.com/GitoxideLabs/gitoxide/commit/dd5c18d9e526e8de462fa40aa047acd097cfa7dc
github_commit Patch Available

commit 6a2e6a436f76 (GitoxideLabs/gitoxide)

Patch available: GitoxideLabs/gitoxide gix-trace-v0.1.20 (contains commit 6a2e6a436f76)

https://github.com/GitoxideLabs/gitoxide/commit/6a2e6a436f76c8bbf2487f9967413a51356667a0

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
gix0.83.0
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rust-gix-submodule0.16.0-1, 0.20.0-1, 0.30.0-1, 0.33.0-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rust-gix-submodule0.16.0-1, 0.20.0-10.30.0-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 242 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40034?
CVE-2026-40034 is a high vulnerability published on May 26, 2026. gix-submodule before 0.29.0 (gitoxide before 0.5.21, gix before 0.84.0) incorrectly validates the update field in .gitmodules, allowing attackers to bypass the CommandForbiddenInModulesConfiguration guard when a submodule has been initialized with only partial configuration in .git/config. An…
When was CVE-2026-40034 disclosed?
CVE-2026-40034 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40034 actively exploited?
CVE-2026-40034 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 71.6% of all scored CVEs.
What is the CVSS score of CVE-2026-40034?
CVE-2026-40034 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-40034?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40034, 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-40034

Explore →

Is Your Infrastructure Affected by CVE-2026-40034?

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