Skip to content

chore: bump test Dockerfile to Node 22.23.4 (DII-2727) - #1224

Open
kridai wants to merge 1 commit into
mainfrom
DII-2727-node22-distrust-emudhra
Open

kridai wants to merge 1 commit into
mainfrom
DII-2727-node22-distrust-emudhra

Conversation

@kridai

@kridai kridai commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Rule 1 (Universal Patching) change for twilio-node, tracked in DII-2727 (SEV0 eMudhra incident). Role assessment: not impacted for runtime and build endpoints (Twilio APIs chain to DigiCert; npm registry to Google Trust Services/GlobalSign; none eMudhra).

Dockerfile: FROM node:20 -> FROM node:22.23.4.

  • Node 20 is EOL and is not patched.
  • 22.23.4 (published 2026-10-21) contains tls: reject chains containing blocked public keys nodejs/node#66871 (tls: reject chains containing blocked public keys, the Node-level blocklist for the compromised eMudhra intermediates) and the NSS 3.131.1 root update. I confirmed the #66871 commit is an ancestor of the v22.23.4 tag. It is also the Node version used by the platform's patched base-node/22 image.

Verification

  • Built the image locally: node v22.23.4.

node:20 is EOL and not patched. Move the Dockerfile to Node 22.23.4, which
includes the Node-level blocklist for the compromised eMudhra intermediates
(nodejs/node#66871) and the NSS 3.131.1 root update.

Refs DII-2727

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@kridai
kridai force-pushed the DII-2727-node22-distrust-emudhra branch from 70ec214 to 9aaef3e Compare October 27, 2026 09:33
@kridai kridai changed the title chore: bump test Dockerfile to Node 22.23.4 and distrust emSign roots (DII-2727) chore: bump test Dockerfile to Node 22.23.4 (DII-2727) Oct 27, 2026
@kridai
kridai marked this pull request as ready for review October 28, 2026 07:37

This branch has not been deployed

No deployments
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.

1 participant