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 supports a charset parameters that defaults to UTF-8 that allows for correct encoding/decoding of passwords.
{
"cna_assigner": "eclipse",
"cwe_ids": [
"CWE-173",
"CWE-303"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/10xxx/CVE-2026-10050.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "9.4.0"
},
{
"last_affected": "9.4.62"
},
{
"introduced": "10.0.0"
},
{
"last_affected": "10.0.30"
},
{
"introduced": "11.0.0"
},
{
"last_affected": "11.0.30"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
]
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "12.0.0"
},
{
"fixed": "12.0.36"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "12.1.0"
},
{
"fixed": "12.1.10"
}
],
"source": "CPE_RANGE"
}
]
}