fix(deps): remediate 40+ CVEs across 21 vulnerable packages#614
Open
devin-ai-integration[bot] wants to merge 7 commits intomainfrom
Open
fix(deps): remediate 40+ CVEs across 21 vulnerable packages#614devin-ai-integration[bot] wants to merge 7 commits intomainfrom
devin-ai-integration[bot] wants to merge 7 commits intomainfrom
Conversation
Direct dependency upgrades: - axios ^1.8.2 -> ^1.15.0 (6 CVEs incl. Critical CVE-2026-33853) - qs 6.12.1 -> ^6.14.2 (2 High CVEs: CVE-2025-15284, CVE-2026-2391) - eciesjs ^0.3.15 -> ^0.4.0 (removes vulnerable elliptic dependency) - pbkdf2 3.1.2 -> ^3.1.3 (2 Critical CVEs: CVE-2026-1863, CVE-2026-1864) - socket.io-client ^4.5.3 -> ^4.7.0 (fixes transitive socket.io-parser CVE) - lodash ^4.17.21 -> ^4.18.1 (High: arbitrary code injection) - @xmldom/xmldom ^0.8.10 -> ^0.8.12 (High: XML injection) - @react-native-community/cli-server-api ^17.0.0 -> ^17.0.1 (Critical: command injection) Transitive dependency resolutions added: - node-forge >= 1.4.0 (6 CVEs, Critical+High) - cipher-base >= 1.0.5 (Critical: CVSS 9.8) - sha.js >= 2.4.12 (Critical: CVSS 9.8) - sjcl >= 1.0.9 (High: improper signature verification) - fast-xml-parser >= 4.5.4 (High: XML entity expansion) - undici >= 6.24.0 (7 CVEs) - h3 >= 1.15.9 (High: HTTP request smuggling) - basic-ftp >= 5.0.5 (High: CRLF injection) - socket.io-parser >= 4.2.6 (High: resource exhaustion) - qs >= 6.14.2 (catches all transitive instances) - pbkdf2 >= 3.1.3 (catches all transitive instances) - @xmldom/xmldom >= 0.8.12 (catches all transitive instances) Also updated: - xmldom resolution from 0.7.13 to 0.8.12 - bn.js 5.2.1 -> 5.2.3 (Medium: infinite loop) Lockfile entries updated directly because yarn install cannot complete due to a pre-existing 404 on the archived react-native-tcp package. Co-Authored-By: Abhay Aggarwal <abhay.aggarwal@codeium.com>
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Properly regenerated yarn.lock via yarn install (instead of manual edits) to ensure lockfile consistency with yarn's resolver. All resolutions and dependency upgrades from package.json are now reflected in the lockfile through yarn's native resolution mechanism. Note: bn.js 5.2.1 remains unfixed (Medium: CVE-2026-2739) because a **/bn.js resolution would break bn.js 4.x consumers. Co-Authored-By: Abhay Aggarwal <abhay.aggarwal@codeium.com>
Ran yarn-deduplicate followed by yarn install to ensure the lockfile passes the CI deduplicate check (which verifies no duplicate dependency entries exist). Co-Authored-By: Abhay Aggarwal <abhay.aggarwal@codeium.com>
…gistry The GitHub archive URL for aprock/react-native-tcp#98fbc80 returns 404 (the repository has been deleted/archived). This breaks all CI jobs that run yarn install because the package cannot be fetched. Switched to react-native-tcp@4.0.0 from npm registry which is the same version (4.0.0) as the git commit previously referenced. Also ran yarn-deduplicate + yarn install to ensure lockfile consistency and idempotent deduplication. Co-Authored-By: Abhay Aggarwal <abhay.aggarwal@codeium.com>
Run 'allow-scripts auto' to add configuration for ethereumjs-util>ethereum-cryptography>secp256k1 which was detected as needing explicit allow/deny after dependency updates. Co-Authored-By: Abhay Aggarwal <abhay.aggarwal@codeium.com>
eciesjs 0.4.x uses @ecies/ciphers with package.json 'exports' subpaths (e.g., './aes') which Metro bundler cannot resolve, causing the js-bundle-size-check to fail with: 'Unable to resolve module @ecies/ciphers/aes' Reverted to eciesjs@0.3.21 (original version). The SNYK-JS-ECIESJS vulnerability (Medium 5.3) cannot be fixed without breaking React Native compatibility. Documented as accepted risk alongside bn.js. Co-Authored-By: Abhay Aggarwal <abhay.aggarwal@codeium.com>
eciesjs 0.3.21 introduced node:crypto imports that Metro bundler cannot resolve. Pinning to 0.3.16 (same version as main) to avoid breaking js-bundle-size-check. Co-Authored-By: Abhay Aggarwal <abhay.aggarwal@codeium.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
Remediates 40+ security vulnerabilities (Critical, High, and Medium severity) across 20 packages by upgrading direct dependencies and adding yarn resolutions for transitive dependencies. Also fixes a pre-existing CI blocker where
react-native-tcpreferenced a deleted GitHub archive (404).CVEs Fixed:
Additional fix:
react-native-tcpswitched from broken GitHub archive URL to npm registry4.0.0(same version, repo was deleted).Accepted risks (cannot fix):
eciesjs0.3.21 (SNYK-JS-ECIESJS-6423640, Medium 5.3) — 0.4.x uses@ecies/cipherswith package.jsonexportssubpaths that Metro bundler cannot resolvebn.js5.2.1 (CVE-2026-2739, Medium) — resolution would break bn.js 4.x consumerssharp(SNYK-JS-SHARP-5922108) — false positive, dev-only via appium-adbChanges:
package.json(7 direct upgrades, 14 resolutions, react-native-tcp fix, allow-scripts update),yarn.lock(regenerated via yarn install + yarn-deduplicate).Review & Testing Checklist for Human
yarn why node-forge,yarn why axios,yarn why @react-native-community/cli-server-apiyarn test) to check for regressionssocket.io-client4.6→4.8 touches networking codeqsupgrade doesn't break query string parsing (forced via resolution over~6.5.2range)react-native-tcpstill works after switching from git archive to npm registryNotes
CLABot(bot CLA),check-pr-labels(needs team labels),check-diff(macOS runner infra),audit:ci(main has 968 vulns),sonar-cloud-quality-gate-status(empty API response)Link to Devin session: https://app.devin.ai/sessions/2cf73bd35a1446048ed8c1e881ed1159
Requested by: @abhay-codeium
Devin Review