CVE-2025-4949 — org.eclipse.jgit
CVE-2025-4949 is a XML External Entity (XXE) vulnerability in org.eclipse.jgit:org.eclipse.jgit. A fix is available for org.eclipse.jgit:org.eclipse.jgit — see the affected versions and patch details below.
XXE vulnerability in Eclipse JGit
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-4949.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.eclipse.jgit:org.eclipse.jgit☕org.eclipse.jgit:org.eclipse.jgit☕org.eclipse.jgit:org.eclipse.jgit☕org.eclipse.jgit:org.eclipse.jgit☕org.eclipse.jgit:org.eclipse.jgit☕org.eclipse.jgit:org.eclipse.jgitReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Eclipse JGit versions 7.2.0.202503040940-r and older, the ManifestParser class used by the repo command and the AmazonS3 class used to implement the experimental amazons3 git transport protocol allowing to store git pack files in an Amazon S3 bucket, are vulnerable to XML External Entity (XXE) attacks when parsing XML files. This vulnerability can lead to information disclosure, denial of service, and other security issues.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jgit:org.eclipse.jgit | ≥ 7.2.0.202503040940-r&&< 7.2.1.202505142326-r | 7.2.1.202505142326-rorg.eclipse.jgit:org.eclipse.jgit:7.2.1.202505142326-r |
| ☕Maven | org.eclipse.jgit:org.eclipse.jgit | ≥ 7.1.0.202411261347-r&&< 7.1.1.202505221757-r | 7.1.1.202505221757-rorg.eclipse.jgit:org.eclipse.jgit:7.1.1.202505221757-r |
| ☕Maven | org.eclipse.jgit:org.eclipse.jgit | ≥ 7.0.0.202409031743-r&&< 7.0.1.202505221510-r | 7.0.1.202505221510-rorg.eclipse.jgit:org.eclipse.jgit:7.0.1.202505221510-r |
| ☕Maven | org.eclipse.jgit:org.eclipse.jgit | ≥ 6.1.0.202203080745-r&&< 6.10.1.202505221210-r | 6.10.1.202505221210-rorg.eclipse.jgit:org.eclipse.jgit:6.10.1.202505221210-r |
| ☕Maven | org.eclipse.jgit:org.eclipse.jgit | ≥ 6.0.0.202110060947-m1&&< 6.0.0.202111291000-r | 6.0.0.202111291000-rorg.eclipse.jgit:org.eclipse.jgit:6.0.0.202111291000-r |
| ☕Maven | org.eclipse.jgit:org.eclipse.jgit | all versions | 5.13.4.202507202350-rorg.eclipse.jgit:org.eclipse.jgit:5.13.4.202507202350-r |
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update org.eclipse.jgit:org.eclipse.jgit to 7.2.1.202505142326-r or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-4949 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-4949 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-4949. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
This vulnerability is rated Moderate for Red Hat products. A flaw in Eclipse JGit allows for XML External Entity (XXE) attacks when parsing specially crafted XML files. This can lead to local denial of service in affected Red Hat products that utilize JGit's ManifestParser or AmazonS3 class for git transport. The…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4.10.7 for Spring Boot 3.4.10 | org.eclipse.jgit | RHSA-2025:18028 |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | eap7-eclipse-jgit-0:5.13.5.202508271544-1.r_redhat_00001.1.el7eap | RHSA-2026:6011 |
| Red Hat JBoss Enterprise Application Platform 7.4.24 | org.eclipse.jgit/org.eclipse.jgit:5.13.5.202508271544-r-redhat-00001 | RHSA-2026:4924 |
| Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7 | eap7-eclipse-jgit-0:5.13.5.202508271544-2.r_redhat_00001.1.el7eap | RHSA-2026:4915 |
| Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8 | eap7-eclipse-jgit-0:5.13.5.202508271544-2.r_redhat_00001.1.el8eap | RHSA-2026:4916 |
| Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9 | eap7-eclipse-jgit-0:5.13.5.202508271544-2.r_redhat_00001.1.el9eap | RHSA-2026:4917 |
| Red Hat JBoss Enterprise Application Platform 8 | org.eclipse.jgit | RHSA-2025:22190 |
| Red Hat JBoss Enterprise Application Platform 8.0 | org.eclipse.jgit | RHSA-2025:22777 |
Frequently Asked Questions
Is CVE-2025-4949 in your dependencies?
O3 Security finds CVE-2025-4949 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.