Repository navigation
fix(deps): update dependency isomorphic-git to v1.38.6 [security] - #105
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
Contributor
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



This PR contains the following updates:
1.25.3→1.38.6isomorphic-git: Arbitrary file write outside of working tree via directory symlink during checkout (potential RCE)
CVE-2026-63395 / GHSA-9qw7-j9xw-fv9c
More information
Details
Summary
git.checkoutwrites working-tree files through a directory symlink without checking the leading path, so a malicious repository can write outside the intended working directory. The defect is in isomorphic-git's checkout logic itself and is therefore independent of thefsprovider. The impact depends on the configured filesystem; worst case is arbitrary file write on the host, e.g. injecting an attacker key into~/.ssh/authorized_keys→ remote login / code execution.Details
A single git tree can't hold a name as both a symlink and a directory, so the attack uses two states:
Checking out commit N writes
configas a directory symlink. Checking out commit N+1 seesconfig/authorized_keysas a new path: isomorphic-gitmkdirs the parent (config, already a symlink →EEXIST, ignored) thenwriteFiles the file, which the OS resolves through the symlink to outside the working directory. A file-level symlink swap is caught (the120000→100644mode change triggers anrm), but the directory-level variant is not — the payload is always a new child path, a plaincreate, so the parent symlink is never removed.The symlink target is attacker-chosen. Besides
~/.ssh, pointing it at the repo's own control directory —hooks → .git/hooksthenhooks/pre-commit, orx → .gitthen overwriting.git/config(core.hooksPath/ alias /core.fsmonitor) — yields RCE on the next nativegitcommand without depending on~/.sshexisting, since.git/is always present in a fresh clone.Canonical git behavior (divergence)
git refuses to do this:
has_symlink_leading_path()(symlinks.c) checks each leading path component during checkout and will not follow a symlink — the hardening behind CVE-2021-21300 and CVE-2024-32002. isomorphic-git has no equivalent check.PoC
https://github.com/spiceoverflow/av1-symlink-hook-rce— open in a Codespace; it builds the malicious repo, serves it locally, and runs a victim. Output on Linux:Trigger: minimal realistic path is
clone(commit N) + a laterpull(commit N+1) — ordinary sync of an already-trusted repo. It also collapses to a singleclonewhen the consuming app reads or writes into the cloned tree, or when a symlink already exists on disk.Impact
isomorphic-git is filesystem-agnostic, so exploitability and blast radius depend on the active
fsprovider — specifically whether it creates a symlink and follows it on a later write:fson Linux/macOS (servers, CI, CLIs, Electron/desktop tooling — the common server-side use): real OS symlinks → the write lands anywhere the process can reach → arbitrary file write on the host → RCE (the PoC above). Highest impact.fson Windows:fs.symlinktypically requires privilege and throwsEPERM, so the symlink-plant step usually fails — not exploitable by default. (A property of the OS/provider, not of isomorphic-git.)fs): there is no host filesystem to escape to, so the worst case is writing outside the intended clone directory but within that virtual filesystem — i.e. corrupting other repos/app data the same provider holds. Bounded by the sandbox, and only if the provider implements symlink creation + following.The CVSS above reflects the worst-case (Node
fson a POSIX host). Browser/in-memory-only deployments are lower severity (sandboxed integrity impact).Suggested fix
Before each working-tree write,
lstatevery leading path component and refuse to traverse asymlink (mirrors git's
has_symlink_leading_path()); optionally honorcore.symlinks=false.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
isomorphic-git: Circular symbolic references cause non-terminating resolution (DoS)
CVE-2026-63475 / GHSA-96wc-2m84-2cj7
More information
Details
Summary
A malicious server can advertise circular
symref=capabilities (e.g.a → bandb → a). isomorphic-git writes them to disk as loose symrefs, andGitRefManager.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 adepthargument is passed (depth = undefinedby default), and has no visited-set:updateRemoteRefspersists all server-supplied symrefs unconditionally. After clone the client hasrefs/remotes/origin/a → ref: refs/remotes/origin/bandb → aon 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 areturns immediately withwarning: ignoring dangling symref— no recursion, no hang.PoC
https://github.com/spiceoverflow/av5-circular-symref— open in a Codespace; clone writes the circular symrefs, thengit.logon one never returns (the runner stops it after a 20s hang):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.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
isomorphic-git: Path traversal via a ".." tree-entry name writes files outside the working directory on clone/checkout
CVE-2026-63478 / GHSA-cw2g-2vwq-88w6
More information
Details
Summary
isomorphic-git's tree parser (
src/models/GitTree.js) validates each entry name only against the path separators/and\. It does not reject the standalone reserved name.., so a malicious repository can, on a singleclone/checkout, write files outside the workingdirectory (unbounded depth). Works on any host-backed
fsprovider.Details
The guard is:
The standalone string
..passes. isomorphic-git assembles the full path incrementally across tree levels, so nesting..trees yields../escaped.txt,../../escaped.txt, … with unbounded depth (each level is a separate tree object that passes the per-entry guard). On checkoutmkdir(workdir/..)hitsEEXIST(ignored) and the file is written above the working directory. Depth is chosen to reach the home dir,/etc,/tmp, etc.; overwriting a shell rc / config / startup file can escalate to code execution.Canonical git behavior (divergence)
git rejects this via
verify_path():git read-treefails witherror: invalid path '../escaped.txt'andgit fsckflagswarning … hasDotdot: contains '..'. (git'sverify_pathalso rejects.and.git, the latter flagged by fsck ashasDotgit— see the fix note below.) GitHub runs fsck on push, so such a tree can't be hosted there; reach is limited to a self-hosted/Smart-HTTP remote or a MitM.PoC
https://github.com/spiceoverflow/av2-dotdot-traversal— open in a Codespace; a singlegit.clone()from the bundled server writesescaped.txtone directory above the clone target (DEPTH=Nescapes N levels):Impact
A path-traversal arbitrary file write outside the working directory (CWE-22), triggered by a single clone/checkout; it can escalate to code execution by overwriting shell rc, config, or startup files.
Any application or user that clones/checks out an untrusted (or compromised / MitM'd) repository with isomorphic-git on a host-backed filesystem (Linux, macOS, or Windows — no symlink or privilege required). Requires a non-GitHub remote (self-hosted / Smart-HTTP) or a MitM, since GitHub's fsck rejects trees containing
...Suggested fix
In the tree parser, reject any entry name equal to
.or... For fullverify_pathparity it should also reject.git(case-insensitively, trailing dots/spaces stripped) and the NTFS 8.3 / HFS variants git blocks. Note: a literal.gitentry is not independently exploitable viaclone/checkoutin current isomorphic-git — the checkout walk skips a.gittree entry (a sibling file is written but the.gitentry is not), so rejecting.gitis defense-in-depth / git parity rather than a separately demonstrated bug. Additionally, normalize and bounds-check the assembled full path against the working-tree root before any filesystem write.Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
isomorphic-git/isomorphic-git (isomorphic-git)
v1.38.6Compare Source
Bug Fixes
v1.38.5Compare Source
Bug Fixes
v1.38.4Compare Source
Bug Fixes
v1.38.3Compare Source
Bug Fixes
v1.38.2Compare Source
Bug Fixes
v1.38.1Compare Source
Bug Fixes
v1.38.0Compare Source
Bug Fixes
Features
v1.37.9Compare Source
Bug Fixes
v1.37.8Compare Source
Bug Fixes
v1.37.7Compare Source
Bug Fixes
v1.37.6Compare Source
Bug Fixes
v1.37.5Compare Source
Bug Fixes
v1.37.4Compare Source
Bug Fixes
v1.37.3Compare Source
Bug Fixes
v1.37.2Compare Source
Bug Fixes
v1.37.1Compare Source
Bug Fixes
v1.37.0Compare Source
Features
v1.36.3Compare Source
Bug Fixes
commitupdate detachedHEAD(#2276) (f87ef9a)v1.36.2Compare Source
Bug Fixes
GitWalkerFs#contenthandle symlinks correctly (#2271) (667be27)v1.36.1Compare Source
Bug Fixes
v1.36.0Compare Source
Features
v1.35.1Compare Source
Bug Fixes
v1.35.0Compare Source
Bug Fixes
Features
v1.34.2Compare Source
Bug Fixes
v1.34.1Compare Source
Bug Fixes
v1.34.0Compare Source
Features
v1.33.3Compare Source
Bug Fixes
v1.33.2Compare Source
Bug Fixes
v1.33.1Compare Source
Bug Fixes
v1.33.0Compare Source
Features
v1.32.3Compare Source
Bug Fixes
v1.32.2Compare Source
Bug Fixes
v1.32.1Compare Source
Bug Fixes
v1.32.0Compare Source
Features
v1.31.1Compare Source
Bug Fixes
v1.31.0Compare Source
Features
v1.30.3Compare Source
Bug Fixes
v1.30.2Compare Source
Bug Fixes
v1.30.1Compare Source
Bug Fixes
v1.30.0Compare Source
Features
v1.29.0Compare Source
Features
v1.28.0Compare Source
Features
v1.27.3Compare Source
Bug Fixes
v1.27.2Compare Source
Bug Fixes
v1.27.1Compare Source
Bug Fixes
v1.27.0Compare Source
Features
v1.26.5Compare Source
Bug Fixes
v1.26.4Compare Source
Bug Fixes
v1.26.3Compare Source
Bug Fixes
onAuthdocs (#1940) (7d34886)v1.26.2Compare Source
Bug Fixes
path.joinfromstdlibinstead of custom join (#1861)" (#1937) (59254b5)v1.26.1Compare Source
Bug Fixes
wrapped(#1935) (85bde9d)v1.26.0Compare Source
Features
v1.25.10Compare Source
Bug Fixes
v1.25.9Compare Source
Bug Fixes
v1.25.8Compare Source
Bug Fixes
v1.25.7Compare Source
Bug Fixes
v1.25.6Compare Source
Bug Fixes
v1.25.5Compare Source
Bug Fixes
v1.25.4Compare Source
Bug Fixes
deflatemust clean up dangling resources (#1864) (45bc531)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.