Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-10051 high CVSS 7.5

Information Disclosure in org.eclipse.jetty:jetty-server (CVE-2026-10051)

Summary

Vulnerability in org.eclipse.jetty:jetty-server (CVE-2026-10051). Confidential information can be exposed externally. Exploitable via POST /upload. Mitigation: upgrade to 12.1.10 or later.

Original description

The description as published by the source.

Description

FINDING — MEDIUM (HTTP/1.1 keep-alive connections with trailers)
HttpConnection._trailers Cross-Request Leakage (Never Reset Between Requests)

Location:
jetty-core/jetty-server/src/main/java/org/eclipse/jetty/server/internal/
HttpConnection.java:107, 1157-1161, 1170

Detail:
_trailers (line 107) is a connection-scoped HttpFields.Mutable field.
parsedTrailer() (line 1157) populates it when request N carries HTTP trailers.
messageComplete() (line 1170) checks "if (_trailers != null)" — evaluates true
from request N's data — and stamps it onto request N+1.

Grep confirms: ZERO occurrences of "_trailers = null" in entire HttpConnection.java.

Scenario:
Request N: POST /upload (trailers: X-Checksum: abc123)
Request N+1: GET /data (no trailers)
app: request.getTrailers() on N+1 → returns {X-Checksum: abc123} ← STALE

Application logic branching on getTrailers() != null produces incorrect behavior.
Not cross-connection (same keep-alive connection only).

More dangerous scenario: TOCTOU — trailer passes check, target swapped before use.

Workarounds

Do not rely on HTTP request trailers for security-sensitive logic, or disable persistent connections by closing the connection after each HTTP/1.1 request.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-10051 has been found in org.eclipse.jetty:jetty-server.
Attackers can target a specific entry point like POST /upload over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade org.eclipse.jetty:jetty-server to 12.1.10 or later.
If unsure, ask your IT team or search "org.eclipse.jetty:jetty-server CVE-2026-10051" on the vendor's site.

CVE-2026-10051 (org.eclipse.jetty:jetty-server) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /upload / GET /data
Patched: 12.1.10 — apply immediately
Workaround: Do not rely on HTTP request trailers for security-sensitive logic, or disable persistent connections by closing the connection after each HTTP/1.1 request.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in org.eclipse.jetty:jetty-server. Attackers reach the vulnerable code path via POST /upload without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.eclipse.jetty:jetty-server. Attack surface: POST /upload / GET /data.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 12.1.10.

🛡️ Workaround

Workaround: Do not rely on HTTP request trailers for security-sensitive logic, or disable persistent connections by closing the connection after each HTTP/1.1 request.

🔍 Detection

Search webserver/proxy logs for unusual POST /upload requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.eclipse.jetty:jetty-server を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /upload' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /upload への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply temporary workaround mitigate 
    Do not rely on HTTP request trailers for security-sensitive logic, or disable persistent connections by closing the connection after each HTTP/1.1 request.

    パッチが適用されるまでの応急処置として、Do not rely on HTTP request trailers for security-sensitive logic, or disable persistent connections by closing the connection after each HTTP/1.1 request. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch 
    Upgrade org.eclipse.jetty:jetty-server to 12.1.10

    ステージング環境で 12.1.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  5. 5
    Post-deployment verification verify 
    Replay attack against POST /upload on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.eclipse.jetty:jetty-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1.10"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details