CVE-2026-18661: Eclipse jetty-annotations vulnerability

Published Oct 15, 2026
·
Updated

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.

Affected Software

2 affected components
Eclipse jetty-annotations
Eclipse jetty-eeN-annotations

Event History

Oct 15, 2026
CVE Published
via MITRE·09:01 AM
Data Sourced
via MITRE·09:01 AM
Description

Frequently Asked Questions

1

Which deployments should be prioritized for review?

Review applications using Eclipse Jetty’s jetty-annotations or jetty-eeN-annotations modules that combine @ServletSecurity annotations with web.xml security constraints for the same URL pattern.

2

How can I identify a potentially affected servlet configuration?

Inspect web.xml for servlets with more than one url-pattern where a security-constraint applies to only some of those patterns. The issue applies when that servlet also uses a mixed @ServletSecurity annotation and web.xml security-constraint configuration on the same URL pattern.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203