HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 10050 digest authentication lossy encoding
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 8.7CVE-2026-10050GHSA-2FVJ-HGJ9-J2GR

Digest authentication lossy encodingCVE-2026-10050

Answer in brief

CVE-2026-10050 records a High severity (CVSS 8.7) vulnerability in Digest authentication lossy encoding. The current sources do not mark it as known exploited. The current feed maps Eclipse Foundation/Eclipse Jetty (generic), Eclipse Foundation/Eclipse Jetty - EE8 (generic), Eclipse Foundation/Eclipse Jetty - EE9 (generic), org.eclipse.jetty.ee8:jetty-ee8-security (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 4, 2026Updated Sep 7, 2026Source checked Nov 3, 2026First seen by HOL Aug 4, 2026Material review Sep 7, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 8.7
Exploitation
Not marked as known exploited
Affected software
22 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Eclipse Foundation/Eclipse Jetty (generic), Eclipse Foundation/Eclipse Jetty - EE8 (generic), Eclipse Foundation/Eclipse Jetty - EE9 (generic), org.eclipse.jetty.ee8:jetty-ee8-security (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Eclipse Foundation/Eclipse Jettygeneric9.4.0 || 10.0.0 || 11.0.0 || 12.0.0 || 12.1.0Not reported
Eclipse Foundation/Eclipse Jetty - EE8generic12.0.0 || 12.1.0Not reported
Eclipse Foundation/Eclipse Jetty - EE9generic12.0.0 || 12.1.0Not reported
org.eclipse.jetty.ee8:jetty-ee8-securitymaven>=12.0.0 <12.0.3612.0.36
org.eclipse.jetty.ee8:jetty-ee8-securitymaven>=12.1.0 <12.1.1012.1.10
org.eclipse.jetty.ee8:jetty-ee8-securitymaven>=12.0.0,<=12.0.3512.0.36
org.eclipse.jetty.ee8:jetty-ee8-securitymaven>=12.1.0,<=12.1.912.1.10
org.eclipse.jetty.ee9:jetty-ee9-securitymaven>=12.0.0 <12.0.3612.0.36
org.eclipse.jetty.ee9:jetty-ee9-securitymaven>=12.1.0 <12.1.1012.1.10
org.eclipse.jetty.ee9:jetty-ee9-securitymaven>=12.0.0,<=12.0.3512.0.36
org.eclipse.jetty.ee9:jetty-ee9-securitymaven>=12.1.0,<=12.1.912.1.10
org.eclipse.jetty:jetty-securitymaven>=11.0.0 <11.0.3111.0.31
org.eclipse.jetty:jetty-securitymaven>=12.1.0 <12.1.1012.1.10
org.eclipse.jetty:jetty-securitymaven>=9.4.0.v20161208,<=9.4.58.v202508149.4.63
org.eclipse.jetty:jetty-securitymaven>=10.0.0,<=10.0.2610.0.31
org.eclipse.jetty:jetty-securitymaven>=11.0.0,<=11.0.2611.0.31
org.eclipse.jetty:jetty-securitymaven>=12.0.0,<=12.0.3512.0.36
org.eclipse.jetty:jetty-securitymaven>=12.1.0,<=12.1.912.1.10
org.eclipse.jetty:jetty-securitymaven>=12.0.0 <12.0.3612.0.36
org.eclipse.jetty:jetty-securitymaven>=9.4.0.v20161208 <9.4.639.4.63
org.eclipse.jetty:jetty-securitymaven>=10.0.0 <10.0.3110.0.31

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Eclipse Foundation/Eclipse Jetty, Eclipse Foundation/Eclipse Jetty - EE8, Eclipse Foundation/Eclipse Jetty - EE9.
  2. 2Review the reported fix. Update org.eclipse.jetty.ee8:jetty-ee8-security to 12.0.36; org.eclipse.jetty.ee8:jetty-ee8-security to 12.1.10; org.eclipse.jetty.ee8:jetty-ee8-security to 12.0.36; org.eclipse.jetty.ee8:jetty-ee8-security to 12.1.10; org.eclipse.jetty.ee9:jetty-ee9-security to 12.0.36; org.eclipse.jetty.ee9:jetty-ee9-security to 12.1.10; org.eclipse.jetty.ee9:jetty-ee9-security to 12.0.36; org.eclipse.jetty.ee9:jetty-ee9-security to 12.1.10; org.eclipse.jetty:jetty-security to 11.0.31; org.eclipse.jetty:jetty-security to 12.1.10; org.eclipse.jetty:jetty-security to 9.4.63; org.eclipse.jetty:jetty-security to 10.0.31; org.eclipse.jetty:jetty-security to 11.0.31; org.eclipse.jetty:jetty-security to 12.0.36; org.eclipse.jetty:jetty-security to 12.1.10; org.eclipse.jetty:jetty-security to 12.0.36; org.eclipse.jetty:jetty-security to 9.4.63; org.eclipse.jetty:jetty-security to 10.0.31 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 4, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Sep 7, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 4, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • Source referencegitlab.eclipse.org
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source 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.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-173, CWE-303
Source
CVE List V5
Source checked
Nov 3, 2026
References
11 linked sources
Open source record