Vulnerability in @opentelemetry/core (CVE-2026-54285)
Summary
Vulnerability in @opentelemetry/core (CVE-2026-54285). Risk of unauthorized operations or information disclosure. Exploitable via baggage. Mitigation: upgrade to 2.8.0 or later.
Original description
The description as published by the source.
opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversized baggage causes memory allocation proportional to the header size without any cap. This vulnerability is fixed in 2.8.0.
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-54285 has been found in @opentelemetry/core.
Attackers can target a specific entry point like baggage over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade @opentelemetry/core to 2.8.0 or later.
If unsure, ask your IT team or search "@opentelemetry/core CVE-2026-54285" on the vendor's site.
CVE-2026-54285 (@opentelemetry/core) — CWE-770 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: baggage / TextMapGetter
Patched: 2.8.0 — apply immediately
Workaround: Ensure header size limits are configured at the server or gateway level.
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.
A vulnerability (CWE-770) exists in @opentelemetry/core. Attackers reach the vulnerable code path via baggage without authentication.
Check the vendor advisory for the affected versions of @opentelemetry/core. Attack surface: baggage / TextMapGetter.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.8.0.
Workaround: Ensure header size limits are configured at the server or gateway level.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@opentelemetry/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@opentelemetry/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@opentelemetry/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Ensure header size limits are configured at the server or gateway level.パッチが適用されるまでの応急処置として、Ensure header size limits are configured at the server or gateway level. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @opentelemetry/core to 2.8.0ステージング環境で 2.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com