Skip to main content
Vulnerability Database/CVE-2026-18659

CVE-2026-18659: Eclipse Jetty Auth Bypass Vulnerability

CVE-2026-18659 is an authentication bypass flaw in Eclipse Jetty that allows attackers to circumvent Jakarta Spec constraints using HTTP method substrings. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-18659 Overview

Eclipse Jetty contains an authorization bypass vulnerability affecting the jetty-security, jetty-eeN-security, and jetty-eeN-servlet modules. Attackers can bypass Jakarta Specification security constraints defined using http-method-omission by sending requests with HTTP method names that are substrings of the configured methods. The flaw maps to [CWE-863: Incorrect Authorization] and permits unauthenticated network access to protected resources.

Critical Impact

Remote unauthenticated attackers can bypass method-based access control constraints and reach endpoints that administrators intended to restrict.

Affected Products

  • Eclipse Jetty jetty-security module
  • Eclipse Jetty jetty-eeN-security modules (Jakarta EE variants)
  • Eclipse Jetty jetty-eeN-servlet modules (Jakarta EE variants)

Discovery Timeline

  • 2026-10-15 - CVE-2026-18659 published to the National Vulnerability Database (NVD)
  • 2026-10-15 - Last updated in NVD database

Technical Details for CVE-2026-18659

Vulnerability Analysis

The Jakarta Servlet Specification allows administrators to define security constraints using http-method-omission, which applies protections to all HTTP methods except those explicitly listed. Jetty's constraint matching logic compares incoming request method names against the omitted set using substring semantics rather than exact equality.

An attacker can craft a request using a non-standard method name that is a substring of a protected or omitted method and bypass the constraint check. Because the vulnerability lives in the authorization layer, exploitation requires no credentials and no user interaction over the network.

The issue affects both the core jetty-security module and the Jakarta EE variants (jetty-eeN-security, jetty-eeN-servlet), so deployments across multiple Jetty release lines are exposed.

Root Cause

The constraint evaluator performs loose string matching instead of strict HTTP method comparison. When Jetty resolves whether a method is omitted from a constraint, substring matches satisfy the check, violating the Jakarta Specification semantics that require exact method matching.

Attack Vector

Exploitation occurs over the network against any Jetty-hosted application that relies on http-method-omission constraints for access control. An attacker issues an HTTP request using a method name chosen to be a substring of a defined method, bypassing the constraint and reaching the protected servlet or resource. See the GitHub Security Advisory GHSA-53x7-f9fc-h7qr for complete technical specifics.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-18659

Indicators of Compromise

  • HTTP access logs containing non-standard or truncated method tokens such as GE, POS, or PU directed at protected servlet paths.
  • Successful 2xx responses to endpoints that should return 401 or 403 for the requesting principal.
  • Repeated requests from a single source cycling through variant HTTP method strings against the same URI.

Detection Strategies

  • Baseline the set of HTTP method tokens observed in production traffic and alert on any method that is not a registered IANA value.
  • Parse Jetty NCSARequestLog output to identify requests whose method is a substring of a standard method but not an exact match.
  • Correlate successful responses against sensitive URIs with the originating method token to surface constraint bypasses.

Monitoring Recommendations

  • Forward Jetty access logs and application authorization decisions to a centralized analytics platform for retrospective hunting.
  • Enable upstream reverse proxy or Web Application Firewall (WAF) logging of raw request-line method strings.
  • Alert on anomalous spikes in 405 Method Not Allowed or unexpected 200 OK responses on constraint-protected routes.

How to Mitigate CVE-2026-18659

Immediate Actions Required

  • Upgrade Eclipse Jetty to the fixed release identified in the GitHub Security Advisory GHSA-53x7-f9fc-h7qr.
  • Audit web.xml and programmatic security configurations for http-method-omission usage and inventory affected endpoints.
  • Review access logs for the past 90 days for anomalous HTTP method tokens targeting protected paths.

Patch Information

Eclipse maintainers published fixes referenced in the GitHub Security Advisory GHSA-53x7-f9fc-h7qr and the Eclipse CVE Assignment Work Item #214. Apply the vendor-recommended patched version for each Jetty release line in use.

Workarounds

  • Replace http-method-omission constraints with explicit http-method definitions that enumerate every permitted method.
  • Enforce an allow-list of standard HTTP methods (GET, POST, PUT, DELETE, HEAD, OPTIONS, PATCH) at an upstream reverse proxy or WAF.
  • Reject requests whose method token does not exactly match an IANA-registered HTTP method before they reach the Jetty container.
bash
# Example NGINX reverse proxy configuration to reject non-standard HTTP methods
if ($request_method !~ ^(GET|POST|PUT|DELETE|HEAD|OPTIONS|PATCH)$) {
    return 405;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.