How severe is CVE-2023-36479?

CVE-2023-36479 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 CVE-2023-36479?

CVE-2023-36479 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 CVE-2023-36479?

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 CVE-2023-36479 is resolved across your whole dependency graph.

How do I detect CVE-2023-36479 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 CVE-2023-36479 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 CVE-2023-36479?

O3 pinpoints whether CVE-2023-36479 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 CVE-2023-36479 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-36479, 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 CVE-2023-36479?

CVE-2023-36479 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.

When was CVE-2023-36479 published, and has it been updated?

CVE-2023-36479 was published on September 15, 2023 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2023-36479: Jetty vulnerable to errant command quoting in C…

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

Eclipse Jetty Canonical Repository is the canonical repository for the Jetty project. Users of the CgiServlet with a very specific command structure may have the wrong command executed. 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. This issue was patched in version 9.4.52, 10.0.16, 11.0.16 and 12.0.0-beta2.

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

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 CVE-2023-36479 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 CVE-2023-36479 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 CVE-2023-36479. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Eclipse Jetty Canonical Repository is the canonical repository for the Jetty project. Users of the CgiServlet with a very specific command structure may have the wrong command executed. 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 wi

O3 Security · Impact-Aware SCA

Is CVE-2023-36479 in your dependencies?

O3 detects CVE-2023-36479 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

CVE-2023-36479