Vulnerability in Eclipse Jetty (CVE-2026-19864)
Summary
Vulnerability in Eclipse Jetty (CVE-2026-19864). Confidential information can be exposed externally. Exploitable via SessionAuthentication.
Original description
The description as published by the source.
Eclipse Jetty's SessionAuthentication retains authentication credentials in a serializable object. When the credentials contain a plaintext password and the authenticated session is persisted to a session data store, the password may consequently be written to persistent storage in plaintext.
An attacker with sufficient privileges to read the persisted session data may obtain the plaintext passwords of authenticated users.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-19864 has been found in Eclipse Jetty.
Attackers can target a specific entry point like SessionAuthentication over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Eclipse Jetty CVE-2026-19864" on the vendor's site.
CVE-2026-19864 (Eclipse Jetty) — CWE-312 / CVSS v3 4.4
Attack vector: local / no user interaction
Attack surface: SessionAuthentication
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-312) exists in Eclipse Jetty. Attackers reach the vulnerable code path via SessionAuthentication.
Check the vendor advisory for the affected versions of Eclipse Jetty. Attack surface: SessionAuthentication.
Severity: Medium (CVSS 4.4/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Eclipse Jetty を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-19864 jetty12
- Ubuntu UBUNTU-CVE-2026-19864 jetty9
References
- REDHAT Red Hat
- web emo@eclipse.org
- web emo@eclipse.org