NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven🐍 PyPI
Not in CISA KEV
CRITICAL severity

JGit Improper Input Validation vulnerabilityGHSA-6vvc-c2m3-cjf3

CRITICALFix: libgit2/libgit2@928429c

GHSA-6vvc-c2m3-cjf3 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in org.eclipse.jgit:org.eclipse.jgit. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.eclipse.jgit:org.eclipse.jgit — see the affected versions and patch details below.

Also known asCVE-2014-9390PYSEC-2020-217
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
75.6%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk
59.0%66.4%73.9%81.3%77.2%75.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.eclipse.jgit:org.eclipse.jgit🐍mercurial

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Windows and OS X; Mercurial before 3.2.3 on Windows and OS X; Apple Xcode before 6.2 beta 3; mine all versions before 08-12-2014; libgit2 all versions up to 0.21.2; Egit all versions before 08-12-2014; and JGit all versions before 08-12-2014 allow remote Git servers to execute arbitrary commands via a tree containing a crafted .git/config file with (1) an ignorable Unicode codepoint, (2) a git~1/config representation, or (3) mixed case that is improperly handled on a case-insensitive filesystem.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.eclipse.jgit:org.eclipse.jgitall versions3.5.3org.eclipse.jgit:org.eclipse.jgit:3.5.3
🐍PyPImercurialall versions3.2.3pip install --upgrade 'mercurial==3.2.3'

Affected Products

6 products · 13 configurations
Application
xcodeapple
≤ 6.1.1
1 version
6.2
Application
egiteclipse
< 08-12-2014
range
Application
jgiteclipse
≥ 3.5.0 && < 3.5.3
range
Application
gitgit-scm
≥ 2.2.0 && < 2.2.1
range
Application
libgit2libgit2
< 0.21.3
range
Application
mercurialmercurial
< 3.2.3
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jgit:org.eclipse.jgit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.eclipse.jgit:org.eclipse.jgit to 3.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vvc-c2m3-cjf3 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

UbuntuCRITICAL

Frequently Asked Questions

Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Windows and OS X; Mercurial before 3.2.3 on Windows and OS X; Apple Xcode before 6.2 beta 3; mine; libgit2; Egit; and JGit allow remote Git servers to execute arbitrary commands via a tree containing a crafted .git/config file with (1) an ignorable Unicode codepoint, (2) a git~1/config representation, or (3) mixed case that is improperly handled on a case-insensitive filesystem.
O3 Security · Impact-Aware SCA

Is GHSA-6vvc-c2m3-cjf3 in your dependencies?

Find it across Maven, PyPI, including transitive dependencies.

JGit Improper Input Validation vulnerability (Critical 9.8)