CVE-2026-18661

validatedZero produced an exploit or a check.

GHSA-gvw6-wq7h-rwp3 ↗EUVD-2026-101954 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Eclipse Foundation Eclipse Jetty >= 12.1.0, <= 12.1.11; >= 12.0.0, <= 12.0.38; >= 11.0.0, <= 11.0.32; >= 10.0.0, <= 10.0.32; >= 9.4.0, <= 9.4.64
ETK-2026-1660Zero's internal tracking ID, independent of the CVE number., permanent identifier
+37mTTV
14mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+37magent stopped
0
+10min
+20min
+30min
+40min

description

Eclipse Jetty annotation modules may fail to enforce intended URL access restrictions for affected servlet deployments. An attacker may access routes that should be restricted when a servlet uses both annotation-based security and web.xml rules, has multiple URL mappings, and only some mappings are covered by a descriptor-based constraint.

mitigation

Avoid this mixed security configuration: do not combine annotation-based servlet security with selective web.xml constraints on a multi-mapped servlet. Review affected mappings and enforce authorization consistently for every exposed URL pattern.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.34%25th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 09:01Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-15 09:01Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-18661

{
  "etk_id": "ETK-2026-1660",
  "cve_id": "CVE-2026-18661",
  "display_id": "CVE-2026-18661",
  "ghsa_id": "GHSA-gvw6-wq7h-rwp3",
  "euvd_id": "EUVD-2026-101954",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Security-constraint precedence error in Eclipse Jetty annotations",
  "summary": "Eclipse Jetty annotation modules may fail to enforce intended URL access restrictions for affected servlet deployments. An attacker may access routes that should be restricted when a servlet uses both annotation-based security and web.xml rules, has multiple URL mappings, and only some mappings are covered by a descriptor-based constraint.",
  "mitigation": "Avoid this mixed security configuration: do not combine annotation-based servlet security with selective web.xml constraints on a multi-mapped servlet. Review affected mappings and enforce authorization consistently for every exposed URL pattern.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse Jetty",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.1.0, <= 12.1.11"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.eclipse.jetty.ee11:jetty-ee11-annotations",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.1.0, <= 12.1.11",
        ">= 12.0.0, <= 12.0.38"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.eclipse.jetty.ee10:jetty-ee10-annotations",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.1.0, <= 12.1.11",
        ">= 12.0.0, <= 12.0.38"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.eclipse.jetty.ee9:jetty-ee9-annotations",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.1.0, <= 12.1.11",
        ">= 12.0.0, <= 12.0.38"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.eclipse.jetty.ee8:jetty-ee8-annotations",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.0.0, <= 11.0.32",
        ">= 10.0.0, <= 10.0.32",
        ">= 9.4.0, <= 9.4.64"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.eclipse.jetty:jetty-annotations",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0034,
  "epss_percentile": 0.2549,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 14.197273,
  "t0_at": "2026-10-15T09:01:28.668000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-15T09:38:53.312719+00:00",
      "days": 0.025979684247685184,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T09:01:28.668000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-15T09:01:28.668000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T09:01:28.668000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-18661"
    }
  }
}

published 2026-10-15 09:24Z
last change 2026-10-21 17:00Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.