Skip to content

fix(deps): bump brace-expansion to patch CVE-2026-69152 - #51

Merged
ashirman merged 1 commit into
mainfrom
fix/brace-expansion-cve-2026-69152
Aug 25, 2026
Merged

fix(deps): bump brace-expansion to patch CVE-2026-69152#51
ashirman merged 1 commit into
mainfrom
fix/brace-expansion-cve-2026-69152

Conversation

@revopushbot

Copy link
Copy Markdown
Contributor

Patches GHSA-rgw5-rvv9-x895 / CVE-2026-69152 — high-severity DoS in brace-expansion via unbounded intermediate arrays (bypasses the earlier CVE-2026-14257 mitigation).

The advisory covers two ranges (<1.1.18 and >=2.0.0 <2.1.4) and both were present in the tree, so both are bumped:

Path Before After
node_modules/brace-expansion (via minimatch@^3) 1.1.17 1.1.18
node_modules/mocha/node_modules/brace-expansion 2.1.3 2.1.4

Lockfile-only change — both are transitive deps and the new versions satisfy the existing ^1.1.7 / ^2.0.2 ranges, so no package.json edit is needed.

Verification

  • npm audit — the high-severity brace-expansion entry is gone. Remaining are 3 pre-existing low findings unrelated to this CVE (body-parser <1.20.6, and diff/mocha, dev-only).
  • npm run build (tsc) — clean.

Note on the diff

npm also dropped four "peer": true markers (@types/node, @typescript-eslint/parser, acorn, eslint) while re-resolving the tree. That's npm-generated metadata drift rather than a hand edit — it reappears on any npm install. Happy to revert those lines if you'd prefer the diff limited strictly to the two version bumps.

🤖 Generated with Claude Code

Resolves GHSA-rgw5-rvv9-x895 (high, DoS via unbounded intermediate
arrays) in both vulnerable trees:

- node_modules/brace-expansion: 1.1.17 -> 1.1.18
- node_modules/mocha/node_modules/brace-expansion: 2.1.3 -> 2.1.4

Lockfile-only change; both are transitive deps and the new versions
satisfy the existing ^1.1.7 / ^2.0.2 ranges.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ashirman
ashirman merged commit e9e62ab into main Aug 25, 2026
2 checks passed
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.

2 participants