Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

isomorphic-git: Circular symbolic references cause non-terminating resolution (DoS)

CVSS 3.1 4.3 MEDIUMEUVD CVSS 3.1 4.3 CVSS 3.1 · [email protected] · Secondary 4.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by isomorphic-git 1.38.6KEV status unknown

cve-program · CVE-2026-63475

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-116273

Published

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.

Read the publisher's advisory

nvd · CVE-2026-63475

Published

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.

Read the publisher's advisory

osv · GHSA-96wc-2m84-2cj7

Published

### Summary A malicious server can advertise circular `symref=` capabilities (e.g. `a → b` and `b → a`). isomorphic-git writes them to disk as loose symrefs, and `GitRefManager.resolve()` follows them with no depth limit and no cycle detection, so any later operation that resolves one of them (`log`, `status`, `checkout`, `branch`, …) **loops forever** — a persistent denial of service from a single clone. ### Details `src/managers/GitRefManager.js` — `resolve()` only enforces a depth limit when a `depth` argument is passed (`depth = undefined` by default), and has no visited-set: ```js static async resolve({ fs, gitdir, ref, depth = undefined }) { if (depth !== undefined) { depth--; if (depth === -1) return ref } … } ``` `updateRemoteRefs` persists all server-supplied symrefs unconditionally. After clone the client has `refs/remotes/origin/a → ref: refs/remotes/origin/b` and `b → a` on disk; resolving either never terminates. Because the bad refs live on disk, the repo is effectively bricked for the application. #### Canonical git behavior (divergence) git caps symref resolution at `SYMREF_MAXDEPTH = 5` (refs.c): `git rev-parse a` returns immediately with `warning: ignoring dangling symref` — no recursion, no hang. ### PoC `https://github.com/spiceoverflow/av5-circular-symref` — open in a Codespace; clone writes the circular symrefs, then `git.log` on one never returns (the runner stops it after a 20s hang): ``` [AV-5] refs/remotes/origin/a contains: ref: refs/remotes/origin/b [AV-5] refs/remotes/origin/b contains: ref: refs/remotes/origin/a [run] *** DoS CONFIRMED: resolving a circular symref never terminates *** ``` ### Impact A persistent denial of service via non-terminating symbolic-ref resolution (CWE-674 / CWE-835). After a single clone from a malicious (or MitM'd) server the circular refs are written to disk, so every later operation that resolves them (`log`, `status`, `checkout`, `branch`, …) hangs forever — the repository becomes effectively unusable for the application. Impacted: any application that clones from untrusted/compromised remotes with isomorphic-git. ### Suggested fix Add visited-set cycle detection (and/or a default maximum depth, as git does) in `GitRefManager.resolve()`; optionally validate server-supplied symref targets before persisting.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-63475

Published

isomorphic-git

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "isomorphic-git",
                    "product": "isomorphic-git",
                    "versions": [
                        {
                            "version": "< 1.38.6",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-116273

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 3, 2026, 7:45:24 PM

dateUpdated: Nov 3, 2026, 9:31:07 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-63475

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-674 · CWE-835

Original publisher date fields

published: 2026-11-03T20:18:15.903

lastModified: 2026-11-03T22:19:47.803

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-96wc-2m84-2cj7

Published

isomorphic-git

npm

SEMVER · introduced 0 → fixed 1.38.6

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 05:47 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current