What is CVE-2025-4949?A critical-severity flaw in Jgit, explained.
CVE-2025-4949 is a critical-severity flaw (CVSS 9.8) in Jgit from Eclipse, published on 21 May 2025. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.8%. If you run an affected version, plan in the vendor’s fix.
Published 21 May 2025. Record last updated 16 October 2025. We keep this page's data up to date.
What is CVE-2025-4949? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
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.
What kind of flaw is it?
- CWE-611Improper Restriction of XML External Entity Reference
- CWE-827Improper Control of Document Type Definition
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2025-4949 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.8%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2025-4949 scores 55. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2025-4949 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2025-4949? One product.
The published record lists 1 product from 1 vendor. Versions are shown as published: "before 5.13.4" means every version up to, but not including, 5.13.4. If you run one of these, check your version, then go to the fix below.
How do I fix CVE-2025-4949? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2025-4949 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 exper...
- Matched to
- Jgit on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2025-4949 is a critical-severity flaw in Jgit from Eclipse, published on 21 May 2025. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2025-4949 is 55 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.8%. That can change at any time, which is why we keep watching.
For Jgit from Eclipse: before 5.13.4, 6.0.0 to before 6.10.1.202505221210, 7.0.0 to before 7.0.1.202505221510, 7.1.0 to before 7.1.1.202505221757, 7.2.0 to before 7.2.1.202505142326.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.