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

Eclipse Jetty XmlParser allows arbitrary DOCTYPE declarationsGHSA-58qw-p7qm-5rvh

LOWFix: eclipse/jetty.project#10067

GHSA-58qw-p7qm-5rvh is a low-severity (CVSS 3.9) vulnerability in org.eclipse.jetty:jetty-xml. A fix is available for org.eclipse.jetty:jetty-xml — see the affected versions and patch details below.

Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected
☕org.eclipse.jetty:jetty-xml☕org.eclipse.jetty:jetty-xml☕org.eclipse.jetty:jetty-xml☕org.eclipse.jetty:jetty-xml

Real-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

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.eclipse.jetty:jetty-xml≥ 10.0.0-alpha0&&< 10.0.1610.0.16org.eclipse.jetty:jetty-xml:10.0.16
☕Mavenorg.eclipse.jetty:jetty-xml≥ 11.0.0-alpha0&&< 11.0.1611.0.16org.eclipse.jetty:jetty-xml:11.0.16
☕Mavenorg.eclipse.jetty:jetty-xml≥ 12.0.0.alpha0&&< 12.0.012.0.0org.eclipse.jetty:jetty-xml:12.0.0
☕Mavenorg.eclipse.jetty:jetty-xmlall versions9.4.52.v20230823org.eclipse.jetty:jetty-xml:9.4.52.v20230823

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.jetty:jetty-xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.eclipse.jetty:jetty-xml to 10.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-58qw-p7qm-5rvh is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### 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 se
O3 Security · Impact-Aware SCA

Is GHSA-58qw-p7qm-5rvh in your dependencies?

Find it across Maven, including transitive dependencies.

Eclipse Jetty XmlParser allows arbitrary DOCTYPE…