CVE-2026-10050

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 22, 2026

Last Modified

August 8, 2026

Advisory Details (2)

Auto-updated Sep 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Eclipse Jetty Digest Authentication: ISO-8859-1 lossy encoding allows authentication bypass via character substitution (CWE-173) · Advisory · jetty/jetty.project · GitHub

https://github.com/jetty/jetty.project/security/advisories/GHSA-2fvj-hgj9-j2gr
generic

[Eclipse Jetty] Digest authentication lossy encoding (#120) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/120

Vendor Advisories for CVE-2026-10050(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 5 ecosystems)
Maven(3)
PackageVulnerable rangeFixed inDependents
org.eclipse.jetty.ee8:jetty-ee8-security12.1.0 ... 12.1.9 (10 versions)12.1.10—
org.eclipse.jetty.ee9:jetty-ee9-security12.1.0 ... 12.1.9 (10 versions)12.1.10—
org.eclipse.jetty:jetty-security12.1.0 ... 12.1.9 (10 versions)12.1.10—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
jetty1212.0.17-3 ... 12.0.33-1 (6 versions)——
jetty99.4.57-1 ... 9.4.58-2 (6 versions)——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
jetty1212.0.17-3 ... 12.0.33-1 (6 versions)——
jetty99.4.57-1 ... 9.4.58-2 (6 versions)——
Debian:11(1)
PackageVulnerable rangeFixed inDependents
jetty99.4.39-3 ... 9.4.58-2 (35 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jetty99.4.50-4 ... 9.4.58-2 (18 versions)——

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-08 22:00 UTCEPSS rescore
  2. 2026-09-08 01:53 UTCVendor advisory
  3. 2026-09-07 21:39 UTCEG score recompute
  4. 2026-09-07 21:39 UTCVendor advisory
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 17:28 UTCEG score recompute
  7. 2026-09-06 17:28 UTCVendor advisory
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 12:54 UTCVendor advisory
  10. 2026-09-06 08:39 UTCVendor advisory
  11. 2026-09-06 04:01 UTCVendor advisory
  12. 2026-09-05 23:46 UTCVendor advisory
  13. 2026-09-05 19:33 UTCEG score recompute
  14. 2026-09-05 19:33 UTCVendor advisory
  15. 2026-09-05 07:05 UTCVendor advisory
  16. 2026-09-04 17:53 UTCEG score recompute
  17. 2026-09-04 17:53 UTCVendor advisory
  18. 2026-09-04 13:39 UTCEG score recompute
  19. 2026-09-04 13:39 UTCVendor advisory
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 14:11 UTCEPSS rescore
  22. 2026-09-01 23:36 UTCEG score recompute
  23. 2026-09-01 13:53 UTCEPSS rescore
  24. 2026-09-01 04:39 UTCEPSS rescore
  25. 2026-08-30 23:09 UTCEG score recompute
Show 58 more
  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 05:09 UTCEG score recompute
  3. 2026-08-30 01:21 UTCEPSS rescore
  4. 2026-08-30 00:48 UTCEG score recompute
  5. 2026-08-28 21:40 UTCEPSS rescore
  6. 2026-08-27 14:46 UTCEG score recompute
  7. 2026-08-27 14:24 UTCEPSS rescore
  8. 2026-08-26 14:56 UTCEG score recompute
  9. 2026-08-25 15:38 UTCEG score recompute
  10. 2026-08-25 13:48 UTCEPSS rescore
  11. 2026-08-24 18:14 UTCEG score recompute
  12. 2026-08-24 12:10 UTCEG score recompute
  13. 2026-08-23 01:51 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 00:26 UTCEG score recompute
  16. 2026-08-21 23:48 UTCEPSS rescore
  17. 2026-08-20 22:57 UTCEG score recompute
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-19 20:42 UTCEG score recompute
  20. 2026-08-19 17:03 UTCEPSS rescore
  21. 2026-08-18 19:09 UTCEG score recompute
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 14:16 UTCEG score recompute
  24. 2026-08-16 16:58 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 04:16 UTCEG score recompute
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 02:45 UTCEG score recompute
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 01:20 UTCEG score recompute
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-12 15:31 UTCEG score recompute
  33. 2026-08-12 13:50 UTCEPSS rescore
  34. 2026-08-11 13:49 UTCEG score recompute
  35. 2026-08-11 13:42 UTCEPSS rescore
  36. 2026-08-11 01:07 UTCEG score recompute
  37. 2026-08-10 23:59 UTCEPSS rescore
  38. 2026-08-09 14:58 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 17:50 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 00:55 UTCEG score recompute▲ 0.40
  43. 2026-08-08 00:54 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  44. 2026-08-07 18:00 UTCEG score recompute
  45. 2026-08-06 16:58 UTCEG score recompute
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-06 04:27 UTCEG score recompute
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-04 14:55 UTCEG score recompute
  50. 2026-08-04 13:26 UTCEG score recompute
  51. 2026-08-04 13:13 UTCEG score recompute
  52. 2026-08-04 11:25 UTCEG score recompute
  53. 2026-08-04 11:15 UTCEG score recompute▲ 8.70
  54. 2026-08-04 11:13 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7
  55. 2026-08-01 04:50 UTCEG score recompute
  56. 2026-07-29 07:20 UTCEG score recompute
  57. 2026-07-23 03:04 UTCEG score recompute
  58. 2026-07-22 23:23 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-10050?
CVE-2026-10050 is a critical vulnerability published on July 22, 2026. 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…
When was CVE-2026-10050 disclosed?
CVE-2026-10050 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on August 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10050 actively exploited?
CVE-2026-10050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.0% of all scored CVEs.
What is the CVSS score of CVE-2026-10050?
CVE-2026-10050 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-10050?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10050, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10050

Explore →

Is Your Infrastructure Affected by CVE-2026-10050?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs