chore: upgrade @opentelemetry/core to ^2.8.0 to address CVE-2026-54285#1413
Merged
Conversation
@opentelemetry/core is a transitive dependency requested at several exact pins (2.5.0, 2.5.1, 2.2.0, 2.0.1) and ranges (^2.5.1, ^2.0.0) via Sentry, the OpenTelemetry instrumentation packages, and PostHog. The advisory (GHSA-8988-4f7v-96qf) affects all versions < 2.8.0, so a `yarn up -R` refresh alone can't reach the patched 2.8.0 past the exact pins. Add 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. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
WalkthroughAdds a ChangesDependency resolution update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Caution Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted. Error details |
Contributor
License Audit
Weak Copyleft Packages (informational)
Resolved Packages (12)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes SOU-1365
Fixes SOU-1358
Fixes SOU-1359
Addresses CVE-2026-54285 (GHSA-8988-4f7v-96qf) — unbounded memory allocation in
@opentelemetry/core's W3C Baggageextract()path. The advisory affects all versions< 2.8.0.Why a
resolutionsoverride@opentelemetry/coreis a transitive dependency requested at several exact pins (2.5.0,2.5.1,2.2.0,2.0.1) and ranges (^2.5.1,^2.0.0) via Sentry, the OpenTelemetry instrumentation packages, and PostHog. Ayarn up -R @opentelemetry/corerefresh moves the caret ranges to2.8.0but cannot get past the exact pins (e.g.@opentelemetry/instrumentation-http@0.211.0pins@opentelemetry/core@2.5.0).Since every requested version is in the affected range, this adds a root
resolutionsoverride pinning@opentelemetry/coreto^2.8.0, consistent with the existing@opentelemetry/resourcesoverride. After the change,yarn why @opentelemetry/corecollapses to a single2.8.0instance, so Dependabot alert #235 will clear.Note on duplicate issues
SOU-1358, SOU-1359, and SOU-1365 are all the same CVE against the same package (all tied to Dependabot alert #235). Prior PRs #1340/#1341/#1343 used this identical fix but were closed as mutual duplicates, so nothing ever merged and
mainstill shipped the vulnerable versions. This single PR resolves all three.Verification
yarn installclean;yarn why @opentelemetry/core→ single2.8.0instance, no< 2.8.0requesters remain.@opentelemetry/coreimports in app source (purely transitive).@sourcebot/backend(the flagged Sentry → instrumentation-http → core path) builds clean withtsc.🤖 Generated with Claude Code
Summary by CodeRabbit