Finding and attribution
A partially initialized trusted submodule override passes a guard that checks only for a trusted section, while the update value falls through to attacker-controlled .gitmodules. A downstream gitoxide consumer that executes the returned Command value can run attacker-supplied shell commands; gitoxide itself has no submodule-update command.
Product: gitoxide. AI system: Claude Mythos Preview. Team / organization: Anthropic.
CVE identifiers: CVE-2026-40034.
AI and human contribution (source account): Item CVD ANT-2026-6SNS6KMP explicitly identifies Claude Mythos Preview as discoverer. The vendor GHSA confirms the exact distinct gitoxide flaw and fix but does not itself credit AI; CVD timeline gives first public AI account on 2026-05-20. Its timeline dates discovery/logging March 10 and maintainer report March 29, before the April 24 patch.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Public disclosure is documented. Sources do not establish exploitation in the wild or zero-day status. CVD says finding was static-analysis-only and not dynamically reproduced.
Remediation status: fix documented. Affected gix versions >=0.31.0 and <0.83.0; fixed in 0.83.0. This is an unsafe API result for downstream gitoxide-based submodule-update consumers: the gix CLI itself does not currently implement submodule update, so do not claim direct RCE in that CLI. The vendor advisory demonstrates the bug with a unit test and an end-to-end comparison against Git.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 25 Apr 2026. AI attribution dated 20 May 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 7.8. Documented technical effects: code execution.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-40034: CVSS 4.0 · 7.3 (High) ·
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. VulnCheck (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-40034: CVSS 3.1 · 7.8 (High) ·
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. VulnCheck (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-40034: code execution.
Prerequisites / affected scope: 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. Improper Neutralization of Special Elements used in a Command ('Command Injection').
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Affected gix versions >=0.31.0 and <0.83.0; fixed in 0.83.0. This is an unsafe API result for downstream gitoxide-based submodule-update consumers: the gix CLI itself does not currently implement submodule update, so do not claim direct RCE in that CLI. The vendor advisory demonstrates the bug with a unit test and an end-to-end comparison against Git.