How severe is GHSA-gwcr-j4wh-j3cq?

GHSA-gwcr-j4wh-j3cq has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-gwcr-j4wh-j3cq?

GHSA-gwcr-j4wh-j3cq affects the following packages: org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty:jetty-servlets (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gwcr-j4wh-j3cq?

Update org.eclipse.jetty:jetty-servlets to version 9.4.41 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-gwcr-j4wh-j3cq actively exploited in the wild?

No public exploit code has been indexed for GHSA-gwcr-j4wh-j3cq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gwcr-j4wh-j3cq?

GHSA-gwcr-j4wh-j3cq has an EPSS (Exploit Prediction Scoring System) score of 90.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-gwcr-j4wh-j3cq?

GHSA-gwcr-j4wh-j3cq is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-gwcr-j4wh-j3cq?

A Nuclei detection template exists for GHSA-gwcr-j4wh-j3cq, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-gwcr-j4wh-j3cq published, and has it been updated?

GHSA-gwcr-j4wh-j3cq was published on June 10, 2021 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-gwcr-j4wh-j3cq

MEDIUM

Jetty Utility Servlets ConcatServlet Double Decoding Information Disclosure Vulnerability

Also known asCVE-2021-28169

Published

Jun 10, 2021

Updated

Mar 13, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

90.3%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

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.

Blast Radius

3 pkgs affected

☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets

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

Requests to the ConcatServlet and WelcomeFilter are able to access protected resources within the WEB-INF directory. For example a request to the ConcatServlet with a URI of /concat?/%2557EB-INF/web.xml can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.

This occurs because both ConcatServlet and WelcomeFilter decode the supplied path to verify it is not within the WEB-INF or META-INF directories. It then uses this decoded path to call RequestDispatcher which will also do decoding of the path. This double decoding allows paths with a doubly encoded WEB-INF to bypass this security check.

Impact

This affects all versions of ConcatServlet and WelcomeFilter in versions before 9.4.41, 10.0.3 and 11.0.3.

Workarounds

If you cannot update to the latest version of Jetty, you can instead deploy your own version of the ConcatServlet and/or the WelcomeFilter by using the code from the latest version of Jetty.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-servlets`	all versions	9.4.41
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 10.0.0&&< 10.0.3	10.0.3
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 11.0.0&&< 11.0.3	11.0.3

Frequently Asked Questions

Requests to the `ConcatServlet` and `WelcomeFilter` are able to access protected resources within the `WEB-INF` directory. For example a request to the `ConcatServlet` with a URI of `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application. This occurs because both `ConcatServlet` and `WelcomeFilter` decode the supplied path to verify it is not within the `WEB-INF` or `META-INF` directories. It then uses this decoded path to call `RequestDispatcher` which will also do decoding of the path. This double

O3 Security · Impact-Aware SCA

Is GHSA-gwcr-j4wh-j3cq in your stack?

O3 detects GHSA-gwcr-j4wh-j3cq across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

5.3/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction