[MGMT-358] Bump vulnerable transitive npm deps (zerkel) - #32
Open
honeycomb-cheesecake wants to merge 1 commit into
Open
[MGMT-358] Bump vulnerable transitive npm deps (zerkel)#32honeycomb-cheesecake wants to merge 1 commit into
honeycomb-cheesecake wants to merge 1 commit into
Conversation
Resolved via narrow, in-range `npm update <pkg>` bumps (no code changes, package.json unchanged): - minimatch 3.1.2->3.1.5, 5.1.6->5.1.9, 9.0.5->9.0.9 (CVE-2026-26996, CVE-2026-27904, CVE-2026-27903 - ReDoS) - brace-expansion 1.1.12->1.1.18, 2.0.2->2.1.4 (CVE-2026-69152, CVE-2026-14257, CVE-2026-33750, CVE-2026-13149 - DoS) - glob 10.4.5->10.5.0 (mocha's nested copy; browserify's own glob@7.2.0 picked up glob's unrelated 7.2.3 patch as a side effect of the same `npm update glob` pass) (CVE-2025-64756 - CLI command injection) - js-yaml 4.1.0->4.3.1 (CVE-2026-59869, CVE-2026-53550, CVE-2025-64718, and the unlabeled "!!omap quadratic CPU" finding - all covered by the 4.3.1 range) - shell-quote 1.7.3->1.10.0 (CVE-2026-9277, CVE-2026-13311) - picomatch 2.3.1->2.3.2 (CVE-2026-33671, CVE-2026-33672) - bn.js 4.12.0->4.12.5, 5.2.1->5.2.5 (CVE-2026-2739) - diff 5.2.0->5.2.2 (CVE-2026-24001) Blocked - no clean, non-breaking fix available, left unresolved: - underscore 1.1.7 (CVE-2026-27601): pulled in via jison -> nomnom, and nomnom's own package.json pins underscore to the exact "1.1.x" line (no later patch exists in that line; jumping to underscore's latest, 1.13.8, is outside nomnom's declared compatibility and would need an override that fights nomnom's own manifest). - serialize-javascript 6.0.2 (CVE-2020-7660, CVE-2026-34043): pulled in via mocha, which pins ^6.0.2; no fix exists within the 6.x line, only a major bump to 7.1.0 (outside mocha's declared compatible range). - elliptic 6.6.1 (CVE-2025-14505): 6.6.1 is already the latest published release; no fixed version exists yet upstream (also affects the low-severity bn.js/browserify-sign/create-ecdh/crypto-browserify advisory "effects" entries in `npm audit`, which all trace back to this same elliptic finding). Verified: `npm ci` installs cleanly from the updated lockfile with no ELSPROBLEMS/invalid entries, and `npm test` (mocha) passes all 1103 tests unchanged. `npm audit` vulnerability count drops from 18 to 10, with the remaining 10 all attributable to the three blocked libraries above. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
Resolves Datadog-flagged CVE findings for MGMT-358.
Fixed
minimatch3.1.2/5.1.6/9.0.5 → 3.1.5/5.1.9/9.0.9 — CVE-2026-26996, CVE-2026-27904, CVE-2026-27903brace-expansion1.1.12/2.0.2 → 1.1.18/2.1.4 — CVE-2026-69152, CVE-2026-14257, CVE-2026-33750, CVE-2026-13149glob(mocha's nested copy) 10.4.5 → 10.5.0 — CVE-2025-64756js-yaml4.1.0 → 4.3.1 — CVE-2026-59869, CVE-2026-53550, CVE-2025-64718, plus the unlabeled omap findingshell-quote1.7.3 → 1.10.0 — CVE-2026-9277, CVE-2026-13311picomatch2.3.1 → 2.3.2 — CVE-2026-33671, CVE-2026-33672bn.js4.12.0/5.2.1 → 4.12.5/5.2.5 — CVE-2026-2739diff5.2.0 → 5.2.2 — CVE-2026-24001Applied via targeted
npm update <pkg>(notoverrides, which has a documented limitation collapsing version-scopedname@versionkeys when the same child dependency recurs under multiple differently-versioned parents).package.jsonuntouched, onlypackage-lock.jsonchanged.Not fixed
underscore1.1.7 (CVE-2026-27601) — via jison→nomnom; nomnom pinsunderscore: "1.1.x"exactly, no later patch exists in that line.serialize-javascript6.0.2 (CVE-2020-7660, CVE-2026-34043) — via mocha, pinned^6.0.2; no fix in 6.x, only a major bump to 7.1.0.elliptic6.6.1 (CVE-2025-14505) — already the latest published release; no fix exists upstream yet. Drives the remaining low-severity bn.js/browserify-sign/create-ecdh/crypto-browserify findings too.Verification
npm ciinstalls cleanly from the updated lockfile.npm test(mocha) passes all 1103 tests.npm auditcount dropped from 18 to 10, with the remaining 10 all attributable to the three blocked libraries.