# CVE-2026-18661: In Eclipse Jetty, across various versions of `jetty-annotations`, and `jetty-eeN-annotations`, the Jakarta Spec authoritative url-pattern ru

> Attackers can bypass security constraints in Eclipse Jetty when specific web.xml and annotation configurations are used, potentially accessing protected resources.

- **Severity:** High 8.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-18661, GHSA-gvw6-wq7h-rwp3, GHSA-v6xf-996f-c35f, UBUNTU-CVE-2026-18661

## What is CVE-2026-18661?

CVE-2026-18661 is a high-severity missing authorization vulnerability, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-18661?


## How do I fix CVE-2026-18661?

Apply the vendor's patch.

## Is CVE-2026-18661 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18661 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18661 and fix it if it is affected.

What it is: CVE-2026-18661 is a high-severity missing authorization vulnerability, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18661 exists.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18661/ (Markdown: https://insights.sbomify.com/CVE-2026-18661/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18661
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18661
- OSV: https://osv.dev/vulnerability/CVE-2026-18661

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18661/
Summaries are generated and may contain mistakes; the official description above is the record.