fix(deps): bump postcss to 8.5.18 to resolve GHSA-r28c-9q8g-f849#9352
Merged
Conversation
Bumps the existing postcss pin in the root package.json `resolutions` and `overrides` blocks from 8.5.12 to 8.5.18 to fix a path traversal vulnerability in postcss's source-map auto-loading (CVSS 7.5), which was blocking BitGoJS's "Publish @bitgo-beta" workflow's vulnerability-severity gate. No breaking changes; all consumer semver ranges (e.g. web-demo's postcss@^8.2.14) remain satisfied by 8.5.18. TICKET: INF-2186
zahin-mohammad
force-pushed
the
fix/postcss-cve-ghsa-r28c-9q8g-f849
branch
from
July 24, 2026 20:11
7d8354e to
89830d7
Compare
Contributor
|
lgtm ( cant approve due to HITL checks ) |
mohammadalfaiyazbitgo
approved these changes
Jul 24, 2026
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
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.
Requested by Zahin Mohammad · Slack thread
Description
This PR bumps the pinned
postcssversion from8.5.12to8.5.18to resolve GHSA-r28c-9q8g-f849, a path traversal vulnerability in postcss's source-map auto-loading (CVSS 7.5), fixed upstream in[email protected].This vulnerability was blocking BitGoJS's "Publish @bitgo-beta" workflow's vulnerability-severity gate.
Issue Number
INF-2186
Type of change
What changed
postcsspin in rootpackage.json'sresolutionsblock from8.5.12to8.5.18.postcsspin in rootpackage.json'soverridesblock from8.5.12to8.5.18.modules/web-demo/package.json, whose directpostcss@^8.2.14dependency range already allows8.5.18(any<9.0.0), and will now resolve to8.5.18via the root override/resolution.How Has This Been Tested?
yarn installat the repo root and confirmedpostcssresolves to a single unified8.5.18entry in the resultingyarn.lock, with no other postcss version present.yarn.lockdiff is small and expected: the postcss entry (version + integrity hash), itsnanoiddependency range bump (postcss now requiresnanoid@^3.3.12), and a handful of incidental transitive-dependency resolution shifts from re-runningyarn install(e.g.body-parser,qs,raw-body) unrelated to this change.Checklist
Generated by Claude Code