[joaoloureirop]

GitHub Actions were on Node 20, CircleCI was on cimg/node:18.13.0-browsers, and .nvmrc tracked lts/*. Node 18 and 20 are EOL and were not patched for CVE-2026-111497.

This pins Node.js 26.12.1 in .nvmrc, the Android, iOS, and Detox GitHub Actions workflows, and the CircleCI image (cimg/node:26.12.1-browsers). Node 26 entered Active LTS on 28 October 2026.

Node 26.12.1 does not ship Corepack, so those workflows install it with npm install -g corepack before corepack enable.

@lavamoat/allow-scripts 3.x depends on yargs 17.7.2, whose require entry is ESM and crashes yarn install on Node 26. The dependency is pinned to 5.1.0, which depends on yargs 17.7.3.

Refs: MCWP-1125
https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
https://github.com/nodejs/Release/blob/main/README.md

[socket-security]

Warning

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Priority	Alert  (click "▶" to expand/collapse)	Action
	Potential code anomaly (AI signal): npm resolve is 85.0% likely to have a medium risk anomaly Notes: This manifest uses a non-registry, relative-path dependency ('resolve': '../../../') which is a significant supply-chain risk because it allows arbitrary local code to be pulled in and executed without registry protections. Combined with the 'lerna bootstrap' postinstall script (which can trigger other lifecycle scripts across the monorepo), this setup increases the chance of untrusted code execution and other malicious behavior. Inspect the target of the relative path, all bootstrap-linked packages, and any lifecycle scripts before running npm install in an untrusted environment. Confidence: 0.85 Severity: 0.80 From: package.json → npm/@lavamoat/allow-scripts@5.1.0 → npm/resolve@1.22.12 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/resolve@1.22.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Potential code anomaly (AI signal): npm yargs is 65.0% likely to have a medium risk anomaly Notes: The code fragment serves as a standard CLI command-definition utility with a notable security consideration: if an untrusted builder function is supplied, it can execute arbitrary code via the builder callback. There is no evidence of malware, exfiltration, or obfuscated techniques in this fragment. In trusted use, risk remains low; in contexts allowing untrusted inputs, this fragment requires strict input validation or sandboxing to mitigate arbitrary code execution. The recommended security posture is to avoid invoking untrusted builder callbacks or to constrain them to benign shapes and to sanitize or restrict what those builders can access. Confidence: 0.65 Severity: 0.60 From: package.json → npm/@lavamoat/allow-scripts@5.1.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn

View full report

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​lavamoat/​allow-scripts@​3.4.3 ⏵ 5.1.0	+1			+1

View full report