# CVE-2026-10050

## Summary

- **CVE ID:** CVE-2026-10050
- **Severity:** HIGH
- **CVSS Score:** 8.7 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N)
- **CWE:** CWE-173, CWE-303
- **Published:** Aug 4, 2026
- **Last Modified:** Aug 4, 2026

## Description

In Eclipse Jetty, the Digest authentication server-side component uses ISO-8859-1 to encode the password as bytes.



This was done because the initial specification for HTTP did not specify explicitly a charset, and it was assumed to be ISO-8859-1 for historical reasons.



If the password contains characters that cannot be represented in ISO-8859-1, they are silently replaced by `?`. This happens with passwords that contain Chinese, Cyrillic or Greek characters, for example: `αβ123` converts to `??123`.



An attacker can send a request with a digest `Authorization` header crafted with a password made of only `?` characters; the server would match any password of the same length that contains non-ISO-8859-1 characters.



Recent HTTP Digest [RFC-7616](https://datatracker.ietf.org/doc/html/rfc7616) supports a `charset` parameters that defaults to UTF-8 that allows for correct encoding/decoding of passwords.

## Affected Products

- Eclipse Foundation — Eclipse Jetty - EE8 (12.0.0)
- Eclipse Foundation — Eclipse Jetty - EE8 (12.1.0)
- Eclipse Foundation — Eclipse Jetty - EE9 (12.0.0)
- Eclipse Foundation — Eclipse Jetty - EE9 (12.1.0)
- Eclipse Foundation — Eclipse Jetty (9.4.0)
- Eclipse Foundation — Eclipse Jetty (10.0.0)
- Eclipse Foundation — Eclipse Jetty (11.0.0)
- Eclipse Foundation — Eclipse Jetty (12.0.0)
- Eclipse Foundation — Eclipse Jetty (12.1.0)

## References

- [CNA](https://github.com/jetty/jetty.project/security/advisories/GHSA-2fvj-hgj9-j2gr)
- [CNA](https://gitlab.eclipse.org/security/cve-assignment/-/work_items/120)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.48%
- **EPSS Percentile:** 40.1

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-11._