Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
3.9

Jetty XmlParser may allow remote server calls or crash

published 12 days ago
Summary

Jetty’s XmlParser component can be tricked into loading external data, which could let an attacker cause the server to reach out to internal systems or crash by sending specially crafted XML. This risk only appears when an attacker can already place malicious files on the server, such as a compromised web application. To reduce the chance of abuse, configure the parser to disallow external entities or use a hardened version of Jetty, and avoid processing untrusted XML files.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.24 docker hardened images janusgraph-1.0 All versions
Docker Hardened Images:Alpine:3.24 docker hardened images janusgraph-1.1 All versions
Docker Hardened Images:Debian:13 docker hardened images druid-36-fips All versions
Docker Hardened Images:Debian:13 docker hardened images druid-36 All versions
Docker Hardened Images:Debian:13 docker hardened images druid-37-fips All versions
Docker Hardened Images:Debian:13 docker hardened images druid-37 All versions
Docker Hardened Images:Debian:13 docker hardened images janusgraph-1.0 All versions
Docker Hardened Images:Debian:13 docker hardened images janusgraph-1.1 All versions
Original advisory text
### From the reporter
### From the reporter

> `XmlParser` is vulnerable to XML external entity (XXE) vulnerability.
> XmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit
> this vulnerability in order to achieve SSRF or cause a denial of service.
> One possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the
> WAR includes a malicious web.xml.

### Impact
There are no circumstances in a normally deployed Jetty server where potentially hostile XML is given to the XmlParser class without the attacker already having arbitrary access to the server. I.e. in order to exploit `XmlParser` the attacker would already have the ability to deploy and execute hostile code. Specifically, Jetty has no protection against malicious web application and potentially hostile web applications should only be run on an isolated virtualisation.

Thus this is not considered a vulnerability of the Jetty server itself, as any such usage of the jetty XmlParser is equally vulnerable as a direct usage of the JVM supplied SAX parser. No CVE will be allocated to this advisory.

However, any direct usage of the `XmlParser` class by an application may be vulnerable. The impact would greatly depend on how the application uses `XmlParser`, but it could be a denial of service due to large entity expansion, or possibly the revealing local files if the XML results are accessible remotely.

### Patches
Ability to configure the SAXParserFactory to fit the needs of your particular XML parser implementation have been merged as part of PR #10067

### Workarounds
Don't use Jetty's `XmlParser` to parse data from users.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker partial control (estimated)
Severity
3.9 Low
Timeline
Published10 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta