dbcve.org
JettyApplication · Eclipse

CVE-2026-10051

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 12.0.36 / 12.1.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Eclipse Jetty, a first HTTP/1.1 request with trailers causes the server to retain the trailers in subsequent requests performed over the same connection. Subsequent request that do not have trailers report the trailers of the first request. Subsequent request that do have trailers report the union of trailers of the first request and the current request.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In Eclipse Jetty's HTTP/1.1 connection handler, trailer headers from an initial request are incorrectly retained in connection state and leaked into subsequent requests on the same persistent connection. Requests without trailers incorrectly receive prior trailers, and requests with trailers receive a union of old and new trailers, causing potential cross-request data contamination.

MitigationUpdate Eclipse Jetty to a version that properly resets trailer state between HTTP/1.1 requests on persistent connections, or disable HTTP keep-alive if patching is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JettyApplication
Affected:>= 12.0.0, < 12.0.36>= 12.1.0, < 12.1.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Jetty version
    Check the Jetty JAR files in your deployment, or inspect your build/pom dependencies for the jetty-version artifact. Common locations: lib/ directory, WEB-INF/lib, or Maven/Gradle dependencies.
    Affected if The version is >= 12.0.0 and < 12.0.36, OR >= 12.1.0 and < 12.1.10
  2. Confirm HTTP/1.1 connector is active
    Review your server startup configuration (start.d/, ini files, or embedded server code) for HttpConnectionFactory using HTTP/1.1 protocol. Look for ServerConnector with HttpConfiguration.
    Affected if An HTTP/1.1 connector is configured and running
  3. Verify keep-alive is enabled
    Check your HttpConfiguration or connector settings for keepAlive=true (this is the default for HTTP/1.1). Inspect the connector configuration for explicit keep-alive or idle timeout settings.
    Affected if HTTP keep-alive (persistent connections) is enabled, which is the default behavior for HTTP/1.1
  4. Check for trailer header usage
    Review your application code and servlet filters for handling of HTTP trailer headers (Transfer-Encoding: chunked with trailing headers). Search for javax.servlet.http.HttpServletRequest methods related to trailers.
    Affected if The application processes or relies on HTTP trailer headers in requests

Your environment is affected if you are running a Jetty version in the affected ranges AND you use HTTP/1.1 with keep-alive enabled, which allows trailer state from one request to leak into subsequent requests on the same connection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.0.36 / 12.1.10 or later
Fixed in 12.0.3612.1.10
Interim mitigation

Update Eclipse Jetty to a version that properly resets trailer state between HTTP/1.1 requests on persistent connections, or disable HTTP keep-alive if patching is not immediately feasible.

Recommended fix High confidence

Upgrade to Jetty 12.0.36 (for 12.0.x users) or Jetty 12.1.10 (for 12.1.x users)

  1. Identify your current Jetty 12.x version by checking your project dependencies or JAR file names
  2. Determine which minor version branch you are on (12.0.x or 12.1.x)
  3. Update your dependency management (Maven pom.xml, Gradle build.gradle, or container base image) to specify version 12.0.36 if on the 12.0.x branch
  4. Update your dependency management to specify version 12.1.10 if on the 12.1.x branch
  5. Run your build tool to resolve new dependencies (mvn clean install or gradle build)
  6. Test your application thoroughly in a staging environment before deploying to production
  7. Deploy the updated application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jetty Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10051 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data