Skip to main content
Menu
CVEs

isomorphic-git path traversal in NTFS checkout writes into .git

Affects isomorphic-git on Windows with an NTFS filesystem, where a malicious repository can write files into the real .git directory during clone or checkout. Fixed in 1.38.7.

CVE-2026-77355Published , updated

8.8HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 1.38.7
Who is exposed
Specific setups only

Summary

A remote attacker, without logging in, can get isomorphic-git to write into the active .git directory when a user clones or checks out a crafted repository on Windows with NTFS, because the tree validation fails to reject the reserved alias .git::$INDEX_ALLOCATION. The attacker can then poison repository configuration or hooks, which native Git may later run as that user.

Written by a model

Original 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.

Who should check

Teams running isomorphic-git 1.38.6 or earlier on Windows NTFS that clone or check out untrusted or self-hosted repositories

“Platform required for the alias: Windows on NTFS”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Windows with an NTFS filesystem
  2. Upgrade to a fixed version: 1.38.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77355 (isomorphic-git: NTFS .git::$INDEX_ALLOCATION alias bypass writes into the active gitdir), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77355 (entry last updated 2026-11-20):
Affected:
- isomorphic-git isomorphic-git: fixed in 1.38.7
Fixed versions: 1.38.7.
Conditions (all must be true for the bug to be hit):
- Windows with an NTFS filesystem (source: https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-6fxm-h49m-4fg3)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-77355 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77355 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-6fxm-h49m-4fg3
- https://github.com/isomorphic-git/isomorphic-git/pull/2376
- https://github.com/isomorphic-git/isomorphic-git/commit/e5dbec689fab148fd5b518f3d4958c9d728886f9
- https://github.com/isomorphic-git/isomorphic-git/releases/tag/v1.38.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77355
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77355"}.

Affected versions

cve.now Index

37Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 8.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 6

Questions about CVE-2026-77355

Is CVE-2026-77355 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A malicious repository can use an NTFS alias, .git::$INDEX_ALLOCATION, to make isomorphic-git write files into the active .git directory during clone or checkout. Those files can include repository metadata such as config and hooks.

Source: github.com

Which versions are affected by CVE-2026-77355?

isomorphic-git: before 1.38.7.

Source: cve.now feed data

Am I affected, and how do I check?

Affects isomorphic-git releases before 1.38.7 on Windows with an NTFS filesystem. To check an installed copy, look at the isomorphic-git version in the project's package manifest or lockfile, and confirm the platform is Windows on NTFS.

Source: github.com

How do I fix CVE-2026-77355?

Upgrade isomorphic-git to 1.38.7 or later.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.