← back to feed
CVE-2026-19863

CVE-2026-19863

validatedZero produced an exploit or a check.

GHSA-6m7j-pjmp-crgq ↗EUVD-2026-101993 ↗

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 org.eclipse.jetty:jetty-ethereum >= 12.1.0, <= 12.1.12
CWE-288 Authentication Bypass Using an Alternate Path or Channel
ETK-2026-1669Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.3cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
+1h01mTTV
18mAI 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+61magent stopped
0
+15min
+30min
+45min

description

Jetty deployments using EthereumAuthenticator may expose protected resources to unauthenticated requests. An attacker must request a protected path that includes the configured login path as a later path segment; explicitly forbidden routes are not affected.

mitigation

Change route and login-path configuration so protected paths cannot contain the configured login path as a later segment. Explicitly forbid sensitive routes where appropriate, and monitor the advisory for a fixed release.

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.54%44th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 09:39Z
Δ 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:39Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-19863

this entry in the feed

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

{
  "etk_id": "ETK-2026-1669",
  "cve_id": "CVE-2026-19863",
  "display_id": "CVE-2026-19863",
  "ghsa_id": "GHSA-6m7j-pjmp-crgq",
  "euvd_id": "EUVD-2026-101993",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Jetty EthereumAuthenticator",
  "summary": "Jetty deployments using EthereumAuthenticator may expose protected resources to unauthenticated requests. An attacker must request a protected path that includes the configured login path as a later path segment; explicitly forbidden routes are not affected.",
  "mitigation": "Change route and login-path configuration so protected paths cannot contain the configured login path as a later segment. Explicitly forbid sensitive routes where appropriate, and monitor the advisory for a fixed release.",
  "vendor": "Eclipse Foundation",
  "product": "org.eclipse.jetty:jetty-ethereum",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.1.0, <= 12.1.12"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.eclipse.jetty:jetty-ethereum",
      "purl": null
    }
  ],
  "cwes": [
    288
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0054,
  "epss_percentile": 0.4437,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 17.735779316666665,
  "t0_at": "2026-10-15T09:39:26.083000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-15T10:40:40.924456+00:00",
      "days": 0.042532887222222225,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T09:39:26.083000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-15T09:39:26.083000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T09:39:26.083000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-19863"
    }
  }
}

published 2026-10-15 10:22Z
last change 2026-10-21 05:31Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.