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.
Published: 2026-08-04
Score: 8.7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw causes Jetty to encode passwords using ISO-8859-1, silently replacing unsupported characters with ‘?’; an attacker can craft a Digest Authorization header with a password consisting only of ‘?’ characters, and the server will match it against any non‑ISO‑8859‑1 password of the same length. This allows remote authentication as any user whose password contains non‑ASCII characters, representing an authentication bypass vulnerability. The weakness falls under the Critical Security Weaknesses CWE‑173 (Lossy Encoding) and CWE‑303 (Improper Authentication).

Affected Systems

The Eclipse Foundation’s Jetty web server, including the standard Jetty distribution, Jetty EE8, and Jetty EE9 are affected. No specific version numbers are given, so any instance running these products should be assumed vulnerable until a patch is applied.

Risk and Exploitability

With a CVSS score of 8.7 this vulnerability is considered high severity. No EPSS score is available and it is not listed in CISA’s KEV catalog, yet the simplicity of the attack path means it can be executed remotely from any client capable of sending a HTTP Digest Authorization request. The attacker only needs the target username and can then authenticate by sending the specially crafted header.

Generated by OpenCVE AI on August 4, 2026 at 20:02 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update Jetty to the latest release that implements RFC–7616 charset UTF‑8 handling for Digest authentication.
  • If an immediate update is not possible, configure the Jetty server to reject or reject Digest requests that contain non‑ISO‑8859‑1 characters by enforcing the charset parameter or disabling Digest authentication entirely.
  • Implement a password policy that restricts users to ASCII‑only characters or otherwise prevents the use of non‑ASCII characters in passwords until the patch is deployed.

Generated by OpenCVE AI on August 4, 2026 at 20:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-2fvj-hgj9-j2gr Eclipse Jetty Digest Authentication: ISO-8859-1 lossy encoding allows authentication bypass via character substitution
History

Wed, 05 Aug 2026 10:00:00 +0000

Type Values Removed Values Added
First Time appeared Eclipse
Eclipse jetty
Vendors & Products Eclipse
Eclipse jetty

Tue, 04 Aug 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 04 Aug 2026 11:15:00 +0000

Type Values Removed Values Added
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.
Title Digest authentication lossy encoding
Weaknesses CWE-173
CWE-303
References
Metrics cvssV4_0

{'score': 8.7, 'vector': '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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: eclipse

Published:

Updated: 2026-08-04T12:46:38.770Z

Reserved: 2026-05-29T07:26:26.368Z

Link: CVE-2026-10050

cve-icon Vulnrichment

Updated: 2026-08-04T12:45:22.819Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-04T11:22:43.883

Modified: 2026-08-08T00:38:56.660

Link: CVE-2026-10050

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T09:45:06Z

Weaknesses
  • CWE-173

    Improper Handling of Alternate Encoding

  • CWE-303

    Incorrect Implementation of Authentication Algorithm