How severe is GHSA-3gh6-v5v9-6v9j?

GHSA-3gh6-v5v9-6v9j has a CVSS score of 3.5/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3gh6-v5v9-6v9j?

GHSA-3gh6-v5v9-6v9j affects the following packages: org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty.ee10:jetty-ee10-servlets (Maven), org.eclipse.jetty.ee9:jetty-ee9-servlets (Maven), org.eclipse.jetty.ee8:jetty-ee8-servlets (Maven). Ecosystems affected: Maven.

How do I fix GHSA-3gh6-v5v9-6v9j?

Update org.eclipse.jetty:jetty-servlets to 9.4.52 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gh6-v5v9-6v9j is resolved across your whole dependency graph.

How do I detect GHSA-3gh6-v5v9-6v9j in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-servlets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3gh6-v5v9-6v9j if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-3gh6-v5v9-6v9j?

O3 pinpoints whether GHSA-3gh6-v5v9-6v9j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3gh6-v5v9-6v9j actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-3gh6-v5v9-6v9j, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-3gh6-v5v9-6v9j?

GHSA-3gh6-v5v9-6v9j has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 59th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3gh6-v5v9-6v9j?

GHSA-3gh6-v5v9-6v9j is classified as CWE-149 (CWE-149). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3gh6-v5v9-6v9j published, and has it been updated?

GHSA-3gh6-v5v9-6v9j was published on September 14, 2023 and was last updated on February 4, 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-3gh6-v5v9-6v9j

LOW

Jetty vulnerable to errant command quoting in CGI Servlet

Also known asCVE-2023-36479

Published

Sep 14, 2023

Updated

Feb 4, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk59th percentile-0.42%

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

6 pkgs affected

☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty.ee10:jetty-ee10-servlets☕org.eclipse.jetty.ee9:jetty-ee9-servlets☕org.eclipse.jetty.ee8:jetty-ee8-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

If a user sends a request to a org.eclipse.jetty.servlets.CGI Servlet for a binary with a space in its name, the servlet will escape the command by wrapping it in quotation marks. This wrapped command, plus an optional command prefix, will then be executed through a call to Runtime.exec. If the original binary name provided by the user contains a quotation mark followed by a space, the resulting command line will contain multiple tokens instead of one. For example, if a request references a binary called file” name “here, the escaping algorithm will generate the command line string “file” name “here”, which will invoke the binary named file, not the one that the user requested.

if (execCmd.length() > 0 && execCmd.charAt(0) != '"' && execCmd.contains(" "))
execCmd = "\"" + execCmd + "\"";

Exploit Scenario

The cgi-bin directory contains a binary named exec and a subdirectory named exec” commands, which contains a file called bin1. The user sends to the CGI servlet a request for the filename exec” commands/bin1. This request will pass the file existence check on lines 194 through 205. The servlet will add quotation marks around this filename, resulting in the command line string “exec” commands/bin1”. When this string is passed to Runtime.exec, instead of executing the bin1 binary, the server will execute the exec binary with the argument commands/file1”. In addition to being incorrect, this behavior may bypass alias checks, and it may cause other unintended behaviors if a command prefix is configured.

If the useFullPath configuration setting is off, the command need not pass the existence check. The attack would not rely on a binary and subdirectory having similar names, and the attack will succeed on a much wider variety of directory structures.

Impact

Users of the org.eclipse.jetty.servlets.CGI Servlet with a very specific command structure may have the wrong command executed.

Patches

No patch. In Jetty 9.x, 10.x, and 11.x the org.eclipse.jetty.servlets.CGI has been deprecated. In Jetty 12 (all environments) the org.eclipse.jetty.servlets.CGI has been entirely removed.

Workarounds

The org.eclipse.jetty.servlets.CGI Servlet should not be used. Fast CGI support is available instead.

References

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 9.0.0&&< 9.4.52	9.4.52
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 10.0.0&&< 10.0.16	10.0.16
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 11.0.0&&< 11.0.16	11.0.16
☕Maven	`org.eclipse.jetty.ee10:jetty-ee10-servlets`	all versions	12.0.0-beta2
☕Maven	`org.eclipse.jetty.ee9:jetty-ee9-servlets`	all versions	12.0.0-beta2
☕Maven	`org.eclipse.jetty.ee8:jetty-ee8-servlets`	all versions	12.0.0-beta2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Eclipse Jetty Canonical Repository is the canonical repository for the J…

github.comNVDSep 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-servlets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.eclipse.jetty:jetty-servlets to 9.4.52 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gh6-v5v9-6v9j 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 pinpoints whether GHSA-3gh6-v5v9-6v9j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3gh6-v5v9-6v9j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

If a user sends a request to a `org.eclipse.jetty.servlets.CGI` Servlet for a binary with a space in its name, the servlet will escape the command by wrapping it in quotation marks. This wrapped command, plus an optional command prefix, will then be executed through a call to Runtime.exec. If the original binary name provided by the user contains a quotation mark followed by a space, the resulting command line will contain multiple tokens instead of one. For example, if a request references a binary called file” name “here, the escaping algorithm will generate the command line string “file” na

O3 Security · Impact-Aware SCA

Is GHSA-3gh6-v5v9-6v9j in your dependencies?

O3 detects GHSA-3gh6-v5v9-6v9j 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 dependencies How O3 SCA works

GHSA-3gh6-v5v9-6v9j

EPSS Exploitation Probability

Blast Radius

Description

Exploit Scenario

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-3gh6-v5v9-6v9j in your dependencies?