Answer in brief
CVE-2026-77355 records a High severity (CVSS 8.8) vulnerability in isomorphic-git: NTFS .git::$INDEX_ALLOCATION alias bypass writes into the active gitdir. The current sources do not mark it as known exploited. The current feed maps isomorphic-git/isomorphic-git (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps isomorphic-git/isomorphic-git (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| isomorphic-git/isomorphic-gitgeneric | <1.38.7 | 1.38.7 |
Published upstream
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.