Skip to content

chore: upgrade @opentelemetry/core to ^2.8.0 to address CVE-2026-54285#1343

Closed
linear-code[bot] wants to merge 2 commits into
mainfrom
linear/sou-1365-sourcebot-devsourcebot-cve-2026-54285-opentelemetry-9f8b
Closed

chore: upgrade @opentelemetry/core to ^2.8.0 to address CVE-2026-54285#1343
linear-code[bot] wants to merge 2 commits into
mainfrom
linear/sou-1365-sourcebot-devsourcebot-cve-2026-54285-opentelemetry-9f8b

Conversation

@linear-code

@linear-code linear-code Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Fixes SOU-1365

Note

This duplicates #1340 (SOU-1358) and #1341 (SOU-1359), which already address the same CVE with an identical fix. The sibling PRs are on different branches that this session cannot push to or edit, so this PR exists only to link SOU-1365. Close it in favor of whichever sibling merges.

Addresses CVE-2026-54285 (unbounded memory allocation in W3C Baggage propagation). @opentelemetry/core is a transitive dependency requested at several exact pins (2.5.0, 2.2.0, 2.0.1) and ranges (^2.5.1, ^2.0.0) via Sentry, the OpenTelemetry instrumentation packages, and PostHog, so a yarn up -R refresh can't reach the patched 2.8.0. This adds a root resolutions override pinning @opentelemetry/core to ^2.8.0, consistent with the existing @opentelemetry/resources override.

After the change yarn why @opentelemetry/core collapses to a single 2.8.0 instance.

@github-actions

Copy link
Copy Markdown
Contributor

License Audit

❌ Audit failed to produce results. Check the workflow logs for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant