CVE-2026-18661
8.8HighPublished 15 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-863
Impact
Unauthenticated attackers can bypass servlet security constraints and access restricted endpoints remotely. They only need network access to reach endpoints mapped to multi-pattern servlets.
Root cause
Eclipse Jetty fails to enforce Jakarta Spec URL pattern rules when a servlet defines multiple url-patterns in web.xml and security-constraint applies to only a subset alongside @ServletSecurity annotations.
Affected systems
Versions not listed — check the vendor advisory.
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade jetty-annotations and jetty-eeN-annotations once patched versions are confirmed in the vendor advisory. As an interim workaround, ensure all url-patterns for a given servlet are explicitly and uniformly covered by security-constraint blocks in web.xml rather than relying on mixed @ServletSecurity annotations.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
In Eclipse Jetty, across various versions of `jetty-annotations`, and `jetty-eeN-annotations`, the Jakarta Spec authoritative url-pattern rules for mixed `@ServletSecurity` annotation, and `web.xml` defined `security-constraint` on the same `url-pattern` were not being applied if the `web.xml` had more than 1 `url-pattern` for a servlet, and had a `security-constraint` applying to only some of those `url-pattern` definitions.