isomorphic-git arbitrary file write via symlinks in cherry-pick
- Exploited
- No known exploitation
- Fix
- Fixed in 1.38.8
- Who is exposed
- Specific setups only
Summary
isomorphic-git, a pure JavaScript implementation of Git for Node.js and browsers, can let an attacker write files to locations outside the project folder when a user runs git cherry-pick. A remote attacker with low privileges who gets a user to cherry-pick a crafted change can do this by placing a file beneath a tracked symlink that points outside the worktree, which can lead to data tampering, code injection, or denial of service.
Written by a model
Original description
isomorphic-git is a pure JavaScript implementation of Git for Node.js and browsers. Prior to 1.38.8, git cherry-pick applies tree changes through applyTreeChanges in src/utils/walkerToTreeEntryMap.js without checking whether a leading path component is a symbolic link. If a victim worktree contains a tracked symlink to a location outside the worktree and a cherry-picked tree places a file beneath that path, the write follows the symlink and materializes attacker-controlled blob content at the external destination. This allows arbitrary file writes and can cause data tampering, code injection into interpreted files, privilege escalation, denial of service, or follow-on code execution depending on the selected target path. This issue is fixed in version 1.38.8.
Who should check
Teams using isomorphic-git below 1.38.7 that call cherryPick on repositories that may contain tracked symlinks, in Node.js or browser apps.
“verified on v1.38.7”
What to do
Check whether your setup matches what the bug needs.
The victim repository has a tracked symlink (for example link -> /) pointing outside the worktree. The bug is hit during git cherry-pick, where a cherry-picked tree places a file beneath the symlinked path. Affected isomorphic-git versions are those below 1.38.7 (verified on 1.38.7).Upgrade to a fixed version: 1.38.8.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-86017 (isomorphic-git: Arbitrary File Write via Symlink), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-86017 (entry last updated 2026-11-20):
Affected:
- isomorphic-git isomorphic-git: fixed in 1.38.8
Fixed versions: 1.38.8.
Conditions (all must be true for the bug to be hit):
- The victim repository has a tracked symlink (for example link -> /) pointing outside the worktree. (source: https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-pvh8-4vwp-j58p)
- The bug is hit during git cherry-pick, where a cherry-picked tree places a file beneath the symlinked path. (source: https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-pvh8-4vwp-j58p)
- Affected isomorphic-git versions are those below 1.38.7 (verified on 1.38.7). (source: https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-pvh8-4vwp-j58p)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-86017 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86017 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/isomorphic-git/isomorphic-git/security/advisories/GHSA-pvh8-4vwp-j58p
- https://github.com/isomorphic-git/isomorphic-git/pull/2377
- https://github.com/isomorphic-git/isomorphic-git/commit/4664c8e1147c3c7ba87c027e92093d28607ef4c0
- https://github.com/isomorphic-git/isomorphic-git/releases/tag/v1.38.8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-86017
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-86017"}.Affected versions
- isomorphic-git isomorphic-gitfixed in 1.38.8
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8/10CVSS 8.0
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · isomorphic-git/isomorphic-git · Advisory GHSA-pvh8-4vwp-j58p |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-86017 |
| Record | NVD · CVE-2026-86017 |
| Other links 3 | |
| Repository | GitHub · isomorphic-git/isomorphic-git · Pull request #2377 |
| Repository | GitHub · isomorphic-git/isomorphic-git · Commit 4664c8e1 |
| Repository | GitHub · isomorphic-git/isomorphic-git · Release v1.38.8 |
Questions about CVE-2026-86017
Is CVE-2026-86017 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: cve.now feed data
What does this mean?
A repository can contain a tracked symlink, such as link -> /, that points outside the worktree. When git cherry-pick applies a tree that places a file beneath that symlinked path, isomorphic-git can write attacker-controlled file content outside the worktree, at the filesystem root or wherever the symlink points.
Source: github.com
Which versions are affected by CVE-2026-86017?
isomorphic-git: before 1.38.8.
Source: cve.now feed data
Am I affected, and how do I check?
The advisory says versions below 1.38.7 are affected, and it was verified on 1.38.7. The bug is hit during git cherry-pick in a repository that has a tracked symlink pointing outside the worktree. To check a project, look at the isomorphic-git version listed in its package.json or installed lockfile.
Source: github.com
How do I fix CVE-2026-86017?
Upgrade isomorphic-git to 1.38.8, the fixed version listed for this vulnerability.
Source: github.com
Related
- CVE-2026-77355isomorphic-git: NTFS .git::$INDEX_ALLOCATION alias bypass writes into the active gitdir
- CVE-2026-63395isomorphic-git: Arbitrary file write outside the working tree via a directory symlink during checkout (potential RCE)
- CVE-2026-89011isomorphic-git < 1.42.0 Prototype Pollution via getRemoteInfo
- CVE-2026-63478isomorphic-git: Path traversal via a ".." tree-entry name writes files outside the working directory on clone/checkout
- CVE-2026-63475isomorphic-git: Circular symbolic references cause non-terminating resolution (DoS)
- CVE-2026-63476isomorphic-git: Unbounded memory allocation from attacker-controlled delta target size (DoS)
No corrections so far. Something wrong on this page? Report an error.