Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-19864 Overview
Eclipse Jetty's SessionAuthentication class retains authentication credentials in a serializable object. When those credentials include a plaintext password and the authenticated session is persisted to a session data store, the password is written to persistent storage in cleartext. An attacker with sufficient privileges to read the persisted session data can then recover the plaintext passwords of authenticated users. The flaw is categorized as [CWE-312] Cleartext Storage of Sensitive Information.
Critical Impact
Plaintext user passwords may be exposed to any actor with read access to the Jetty session data store, enabling credential theft and downstream account compromise.
Affected Products
- Eclipse Jetty (versions tracked in the vendor security advisory)
- Applications using Jetty's SessionAuthentication with persistent session stores
- Jetty deployments configured with session persistence to disk, databases, or distributed caches
Discovery Timeline
- 2026-10-15 - CVE-2026-19864 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-19864
Vulnerability Analysis
Jetty uses the SessionAuthentication object to track authenticated users across HTTP requests. The class implements java.io.Serializable, allowing session state to be persisted or replicated across cluster nodes. The authentication object carries user credentials in a form that includes the original plaintext password rather than only a derived identifier or hashed representation.
When session persistence is enabled through a SessionDataStore such as a file-based store, JDBC store, or distributed cache, the serialized form of SessionAuthentication is written out verbatim. Any entity able to read the backing store can extract user passwords without needing to perform cryptographic recovery.
The issue is a cleartext storage weakness rather than a protocol or memory corruption bug. Exploitation does not require interaction with the running Jetty server; access to the persisted artifact is sufficient.
Root Cause
The root cause is the inclusion of the plaintext password field within the serialized representation of SessionAuthentication. The class does not mark the sensitive field transient, does not substitute a one-way token during serialization, and does not require the session store to apply encryption at rest. Downstream persistence layers therefore receive and store the credential in cleartext.
Attack Vector
The attack vector is local and requires high privileges, as reflected in the CVSS vector. A typical attack path involves an actor with read access to the session data store: a database operator with query access to the session table, a backup administrator with access to session file snapshots, a shared-tenant user on a misconfigured cache, or an adversary who has already gained a foothold on the server hosting the store. Once the serialized session blob is retrieved, the attacker deserializes it or parses the embedded strings to extract the password, then reuses the credential against Jetty or any other service where the user has reused the password.
No public proof-of-concept exploit is listed for this issue, and it is not present in the CISA Known Exploited Vulnerabilities catalog. See the Jetty GitHub Security Advisory and the Eclipse CVE Assignment Work Item for vendor-authored technical detail.
Detection Methods for CVE-2026-19864
Indicators of Compromise
- Serialized org.eclipse.jetty.security.SessionAuthentication objects present in session data stores, backups, or exported session dumps.
- Readable password strings discovered when inspecting session blobs with a hex viewer, strings utility, or Java deserializer.
- Unexpected read access to the session store by accounts outside the application service identity.
Detection Strategies
- Enumerate deployed Jetty versions in your estate and compare them against the fixed versions in the vendor advisory.
- Inspect application configuration for SessionDataStore implementations such as FileSessionDataStore, JDBCSessionDataStore, or clustered caches, and confirm whether SessionAuthentication is in use.
- Scan session persistence artifacts for serialized Jetty authentication objects and flag any that contain readable credential fields.
Monitoring Recommendations
- Audit access logs on databases, file systems, and caches that back Jetty session storage, and alert on reads by non-application principals.
- Monitor backup and snapshot workflows that export session data to secondary storage or external media.
- Alert on new or modified SessionDataStore configuration in application deployment pipelines.
How to Mitigate CVE-2026-19864
Immediate Actions Required
- Upgrade Jetty to the patched release identified in the Jetty GitHub Security Advisory.
- Rotate the passwords of any users whose sessions were persisted while the vulnerable code path was active.
- Restrict read access to session data stores to the application service account only, and review existing permissions on backups.
- Purge or re-encrypt existing persisted session artifacts that may contain plaintext credentials.
Patch Information
Refer to the vendor advisory GHSA-q6wx-j9wr-fj7f for the list of fixed versions and the corresponding commit references. The Eclipse Foundation tracks the coordinated fix in the Eclipse CVE Assignment Work Item 229.
Workarounds
- Disable session persistence where it is not required, keeping sessions only in memory for the lifetime of the JVM.
- Use an authentication mechanism that does not propagate the plaintext password into the session, such as form login configurations backed by token-based identity.
- Enable encryption at rest on the storage backing the SessionDataStore, and ensure keys are not accessible to the same principals that can read the stored sessions.
- Shorten session lifetimes and invalidate sessions promptly on logout to reduce the window during which credentials sit in persistent storage.
# Configuration example: disable persistent session storage in Jetty
# by configuring a NullSessionDataStore for the session handler
# See the Jetty documentation for the version in use before applying.
#
# <Set name="sessionDataStore">
# <New class="org.eclipse.jetty.server.session.NullSessionDataStore"/>
# </Set>
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

