CVE-2023-4759 [High] | RCE in Jgit

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 must be enabled in the git configuration. Setting git configuration option core.symlinks = false before checking out avoids the problem. The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/ and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ . A backport is available in 5.13.3 starting from 5.13.3.202401111512-r. The JGit maintainers would like to thank RyotaK for finding and reporting this issue.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.97%	1.88%	+0.91%
2	2026-03-04	1.08%	0.97%	-0.10%
3	2026-03-01	—	1.08%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.97%

1.88%

+0.91%

2026-03-04

1.08%

0.97%

-0.10%

2026-03-01

—

1.08%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

OS Trackers for CVE-2023-4759

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2023-4759 not yet assigned priority: Debian including 1 source packages (jgit), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2.	https://security-tracker.debian.org/tracker/CVE-2023-4759
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2023-4759
`suse`	high	CVE-2023-4759 severity important: SUSE including 13 source package names (5.0.0-beta1.2.122:jsch-0.2.9-150200.11.10.1, 5.1.0.6.40:jsch-0.2.9-150200.11.10.1, …), 61 product×package rows across 29 product lines (Container suse/manager/5.0/x86_64/server, Container suse/multi-linux-manager/5.1/x86_64/server, … (29 product lines)): Fixed 42, Known Not Affected 19.	https://www.suse.com/security/cve/CVE-2023-4759/
`ubuntu`	negligible	CVE-2023-4759 negligible priority: Ubuntu including 1 source packages (jgit), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 5.	https://ubuntu.com/security/CVE-2023-4759

Affected software / configurations for CVE-2023-4759

Vendor	Product	Version	Raw CPE
eclipse	jgit	< 5.13.3.202401111512-r	cpe:2.3:a:eclipse:jgit::::::::
eclipse	jgit	>= 6.6.0, < 6.6.0.202305301015	cpe:2.3:a:eclipse:jgit::::::::
eclipse	jgit	>= 6.7.0, < 6.7.0.202309050840	cpe:2.3:a:eclipse:jgit::::::::

References for CVE-2023-4759

URL	Tags
https://git.eclipse.org/c/jgit/jgit.git/commit/?id=9072103f3b3cf64dd12ad2949836ab98f62dabf1	Patch Vendor Advisory
https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/11	Issue Tracking Vendor Advisory
https://projects.eclipse.org/projects/technology.jgit/releases/6.6.1	Release Notes Vendor Advisory

URL

CVE-2023-4759 | Improper handling of case insensitive filesystems in Eclipse JGit allows arbitrary file write

Exploit prediction scoring system (EPSS) score for CVE-2023-4759

Common vulnerability scoring system (CVSS) metrics for CVE-2023-4759

Weakness enumeration for CVE-2023-4759

GitHub Security Advisory for CVE-2023-4759

OS Trackers for CVE-2023-4759

Affected software / configurations for CVE-2023-4759

References for CVE-2023-4759