# CVE-2026-19864: Eclipse Jetty's `SessionAuthentication` retains authentication credentials in a serializable object.

> Attackers with read access to persisted session data can obtain plaintext passwords of authenticated users in Eclipse Jetty.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-19864, GHSA-q6wx-j9wr-fj7f, UBUNTU-CVE-2026-19864

## What is CVE-2026-19864?

CVE-2026-19864 is a medium-severity vulnerability, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

Apply the vendor's patch.

## Is CVE-2026-19864 being exploited?

There is no known exploitation of CVE-2026-19864 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19864 is a medium-severity vulnerability, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19864 in the wild and no public exploit code.

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-19864/ (Markdown: https://insights.sbomify.com/CVE-2026-19864/index.md)
```

## Sources

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

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