← Back
CVE-2026-54285
medium
CVSS 5.3
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-770) exists in @opentelemetry/core. Attackers reach the vulnerable code path via ``baggage`` without authentication.
📍 Affected scope
@opentelemetry/core — . Attack surface: `baggage` / `TextMapGetter`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.8.0**.
🛡️ Workaround
Workaround: Ensure header size limits are configured at the server or gateway level.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply 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. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade @opentelemetry/core to 2.8.0ステージング環境で 2.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@opentelemetry/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.0"}]}]