Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45292 medium CVSS 5.3

Vulnerability in io.opentelemetry:opentelemetry-api (CVE-2026-45292)

Summary

Vulnerability in io.opentelemetry:opentelemetry-api (CVE-2026-45292). Risk of unauthorized operations or information disclosure. Exploitable via W3CBaggagePropagator. Mitigation: upgrade to 1.62.0 or later.

Original description

The description as published by the source.

Overview

A vulnerability affects the baggage propagation implementation in
opentelemetry-api and opentelemetry-extension-trace-propagators. Parsing oversized baggage
causes unbounded memory allocation and CPU consumption. Because baggage is automatically
re-injected into every outgoing request, the effect can fan out to downstream services that
never received the original malicious request.

Technical Details

  • W3CBaggagePropagator did not enforce any limit on the total size or entry count of the
    baggage header. The parser iterated character-by-character through the entire value
    regardless of length.
  • JaegerPropagator and OtTracePropagator had the same gap in their respective baggage
    extraction paths.
  • The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; none of
    these limits were enforced.

Impact

The practical availability impact for most deployments is limited. Every major Java HTTP server
enforces its own header size limit (Tomcat, Jetty, Netty, Vert.x, and gRPC-Java all default to
8 KiB), constraining what an external attacker can deliver before the application is reached.
The risk is higher when transport-layer limits are absent — e.g., a compromised internal service
communicating over a non-HTTP or custom transport.

Remediation

Update to version 1.62.0 or later (#8380).
The fix enforces limits consistent with the W3C Baggage specificatio…

Source: GitHub Security Advisories (Global) 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-45292 has been found in io.opentelemetry:opentelemetry-api.
Attackers can target a specific entry point like W3CBaggagePropagator over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade io.opentelemetry:opentelemetry-api to 1.62.0 or later.
If unsure, ask your IT team or search "io.opentelemetry:opentelemetry-api CVE-2026-45292" on the vendor's site.

CVE-2026-45292 (io.opentelemetry:opentelemetry-api) — CWE-770 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: W3CBaggagePropagator / baggage / JaegerPropagator / OtTracePropagator
Patched: 1.62.0 — apply immediately
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

A vulnerability (CWE-770) exists in io.opentelemetry:opentelemetry-api. Attackers reach the vulnerable code path via W3CBaggagePropagator without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of io.opentelemetry:opentelemetry-api. Attack surface: W3CBaggagePropagator / baggage / JaegerPropagator / OtTracePropagator.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.62.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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・依存マニフェストで io.opentelemetry:opentelemetry-api を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade io.opentelemetry:opentelemetry-api to 1.62.0

    ステージング環境で 1.62.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

maven io.opentelemetry:opentelemetry-api
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.62.0"}]}]
maven io.opentelemetry:opentelemetry-extension-trace-propagators
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.62.0"}]}]

References

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