GHSA-96WC-2M84-2CJ7

Vulnerability from github – Published: 2026-11-09 19:58 – Updated: 2026-11-09 19:58
VLAI
Summary
isomorphic-git: Circular symbolic references cause non-terminating resolution (DoS)
Details

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:

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.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.38.5"
      },
      "package": {
        "ecosystem": "npm",
        "name": "isomorphic-git"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.38.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-63475"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-674",
      "CWE-835"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-09T19:58:32Z",
    "nvd_published_at": "2026-11-03T20:18:15Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\nA malicious server can advertise circular `symref=` capabilities (e.g. `a \u2192 b` and `b \u2192 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`, \u2026) **loops forever** \u2014 a persistent denial of service from a single clone.\n\n### Details\n`src/managers/GitRefManager.js` \u2014 `resolve()` only enforces a depth limit when a `depth` argument is passed (`depth = undefined` by default), and has no visited-set:\n\n```js\nstatic async resolve({ fs, gitdir, ref, depth = undefined }) {\n  if (depth !== undefined) { depth--; if (depth === -1) return ref }\n  \u2026\n}\n```\n\n`updateRemoteRefs` persists all server-supplied symrefs unconditionally. After clone the client has `refs/remotes/origin/a \u2192 ref: refs/remotes/origin/b` and `b \u2192 a` on disk; resolving either never terminates. Because the bad refs live on disk, the repo is effectively bricked for the application.\n\n#### Canonical git behavior (divergence)\ngit caps symref resolution at `SYMREF_MAXDEPTH = 5` (refs.c): `git rev-parse a` returns immediately with `warning: ignoring dangling symref` \u2014 no recursion, no hang.\n\n### PoC\n`https://github.com/spiceoverflow/av5-circular-symref` \u2014 open in a Codespace; clone writes the circular symrefs, then `git.log` on one never returns (the runner stops it after a 20s hang):\n\n```\n[AV-5] refs/remotes/origin/a contains: ref: refs/remotes/origin/b\n[AV-5] refs/remotes/origin/b contains: ref: refs/remotes/origin/a\n[run] *** DoS CONFIRMED: resolving a circular symref never terminates ***\n```\n\n### Impact\nA persistent denial of service via non-terminating symbolic-ref resolution (CWE-674 / CWE-835). After a single clone from a malicious (or MitM\u0027d) server the circular refs are written to disk, so every later operation that resolves them (`log`, `status`, `checkout`, `branch`, \u2026) hangs forever \u2014 the repository becomes effectively unusable for the application.\n\nImpacted: any application that clones from untrusted/compromised remotes with isomorphic-git.\n\n### Suggested fix\nAdd visited-set cycle detection (and/or a default maximum depth, as git does) in `GitRefManager.resolve()`; optionally validate server-supplied symref targets before persisting.",
  "id": "GHSA-96wc-2m84-2cj7",
  "modified": "2026-11-09T19:58:32Z",
  "published": "2026-11-09T19:58:32Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-96wc-2m84-2cj7"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63475"
    },
    {
      "type": "WEB",
      "url": "https://github.com/isomorphic-git/isomorphic-git/pull/2370"
    },
    {
      "type": "WEB",
      "url": "https://github.com/isomorphic-git/isomorphic-git/commit/823843d1cd19182df79bc907c767f5bcecb39a0b"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/isomorphic-git/isomorphic-git"
    },
    {
      "type": "WEB",
      "url": "https://github.com/isomorphic-git/isomorphic-git/releases/tag/v1.38.6"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "isomorphic-git: Circular symbolic references cause non-terminating resolution (DoS)"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…