Arbitrary File Overwrite in Eclipse JGit

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2023-4759: 2.19% estimated exploitation activity in the next 30 days; percentile 82.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Arbitrary File Overwrite in Eclipse JGit <= 6.6.0 In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem. This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command. The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links…

Published by the source

18 Sep 2023, 15:30 UTC

Last modified by the source

11 Apr 2024, 19:37 UTC

Source last checked

26 Oct 2026, 16:29 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3p86-9955-h393

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-4759

Advisory: Arbitrary File Overwrite in Eclipse JGit
IDs: CVE-2023-4759, GHSA-3p86-9955-h393
Record: https://patchnext.com/advisories/cve-2023-4759 (revision 1, source checked 26 Oct 2026, 16:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.jgit:org.eclipse.jgit 6.6.1.202309021850-r, 5.13.3.202401111512-r. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.jgit:org.eclipse.jgit: affected >= 6.0.0.202111291000-r, <= 6.6.0.202305301015-r; < 5.13.3.202401111512-r; fixed in 6.6.1.202309021850-r, 5.13.3.202401111512-r

## Suggested inspection (read-only)
- Maven org.eclipse.jgit:org.eclipse.jgit: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.jgit:org.eclipse.jgit.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3p86-9955-h393 (GitHub-reviewed advisory GHSA-3p86-9955-h393 lists affected ranges: Maven org.eclipse.jgit:org.eclipse.jgit >=6.0.0.202111291000-r =0 <5.13.3.202401111512-r)

Commands are suggestions: review each one before running it.