CVE-2026-77355: isomorphic-git · Path Traversal
Affects isomorphic-gitSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 1.38.7 soon.
Data as of 20 Nov 2026, 19:29 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.8 |
|---|
- Patch
- Available – fixed in 1.38.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade isomorphic-git to 1.38.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| isomorphic-gitisomorphic-git | Affected
| Fixed in
|
AI-suggested
Upgrade isomorphic-git to version 1.38.7 or later, where this vulnerability is fixed. Additionally, strict hosting environments that reject hasDotgit objects can prevent this attack. Non-NTFS filesystems are not affected by this issue. No other mitigation is required as the fix is available.
Description
isomorphic-git is a pure JavaScript implementation of Git for Node.js and browsers. Prior to 1.38.7, tree-entry validation in src/models/GitTree.js does not reject the Windows NTFS reserved pathname alias .git::$INDEX_ALLOCATION. When clone() or checkout materializes an attacker-controlled tree containing this alias on Windows using an NTFS filesystem, the alias resolves to the active .git directory and permits writes to trusted repository metadata instead of a normal worktree directory. A malicious repository or object stream can therefore poison repository configuration, hooks, refs, attributes, or other gitdir state. Strict hosting that rejects hasDotgit objects can block the crafted tree, and non-NTFS systems do not interpret the pathname as the active gitdir. isomorphic-git performs the gitdir write but does not itself execute the written hook or configuration; a later native Git or compatible-tool action, such as processing a poisoned core.fsmonitor value, can execute configured commands as the victim developer or CI identity. This issue is fixed in version 1.38.7.
References
- github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-6fxm-h49m-4fg3 (opens in a new tab)
- github.com/isomorphic-git/isomorphic-git/pull/2376 (opens in a new tab)
- github.com/isomorphic-git/isomorphic-git/commit/e5dbec689fab148fd5b518f3d4958c9d728886f9 (opens in a new tab)
- github.com/isomorphic-git/isomorphic-git/releases/tag/v1.38.7 (opens in a new tab)