Update npm package @opentelemetry/core to v2.8.0 [SECURITY]

[hash-worker]

This PR contains the following updates:

Package	Change	Age	Confidence
@opentelemetry/core (source)	2.7.1 → 2.8.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2026-54285

Overview

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.

Impact

The practical availability impact for most Node.js deployments is limited. Node.js enforces a default --max-http-header-size of 16,384 bytes on the total combined size of all HTTP headers, constraining what an external attacker can deliver before the propagator is reached. Additionally, the header is already in memory (parsed by the HTTP layer) by the time it reaches the propagator - the additional allocation is the overhead of splitting into entry objects, not an unbounded read.

The risk is higher when transport-layer limits are absent - e.g., non-HTTP transports (messaging systems, custom TextMapGetter implementations) or deployments that have raised --max-http-header-size.

Remediation

Update @opentelemetry/core to version 2.8.0 or later. The fix enforces limits consistent with the W3C Baggage specification at the propagator level:

• Maximum total baggage size: 8,192 bytes
• Maximum number of entries: 180
• Maximum per-entry size: 4,096 bytes

Headers that exceed these limits are truncated at the point the limit is reached.

Workarounds

Ensure header size limits are configured at the server or gateway level. The default Node.js HTTP header limit (16 KB) mitigates external attack vectors independently of this fix. For non-HTTP transports receiving baggage from untrusted sources, validate input size before passing it to the propagator.

References

• W3C Baggage Specification - Limits
• opentelemetry-java: GHSA-rcgg-9c38-7xpx
• opentelemetry-go: GHSA-mh2q-q3fh-2475

Credit

Reported by tonghuaroot.

---

Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/core)

v2.8.0

Compare Source

🚀 Features

• feat(sdk-trace-base): pretty-print SpanImpl, Tracer, and BasicTracerProvider via util.inspect so they render through diag and console.log #​6690 @​mcollina
• feat(sdk-metrics): implement metric reader self-observability metrics #​6449 @​anuraaga
• feat(core): add hrTimeToSeconds #​6449 @​anuraaga

🐛 Bug Fixes

• fix(core): limit processing of incoming "baggage" header to 8192 bytes @​pichlermarc

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • "before 4am every weekday,every weekend"

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hash	Error		Jun 17, 2026 3:25am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
hashdotdesign-tokens	Ignored	Preview	Jun 17, 2026 3:25am
petrinaut	Skipped		Jun 17, 2026 3:25am

[hash-worker]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

error This project's package.json defines "packageManager": "yarn@4.16.0". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

[cursor]

PR Summary

Low Risk
Scope is two package.json version pins with no logic changes; remaining OpenTelemetry packages stay on 2.7.1, which is a typical patch-level dependency update pattern.

Overview
Bumps @opentelemetry/core from 2.7.1 to 2.8.0 in apps/hash-api and libs/@local/hash-backend-utils only—no application or instrumentation code changes.

This picks up the upstream fix for CVE-2026-54285, where inbound W3C baggage headers were parsed without the same size/entry limits as outbound injection, which could allow excessive memory use on extract() in some deployment setups.

^{Reviewed by Cursor Bugbot for commit d6f8145. Bugbot is set up for automated code reviews on this repo. Configure here.}