You have reached the beginning of time!

Securing the Ecosystem: How the NodeSource Team Responded to the eMudhra Compromise

The week of October 20th brought an unexpected challenge for the web ecosystem following the eMudhra certificate authority compromise, where intermediate keys were exposed. In response, members of our team rallied quickly to assist with upstream patches for Node.js and ensure downstream protections for N|Solid users. This post is a look back at those demanding few days, and a word of sincere thanks to everyone across the community and our team who contributed their time, focus, and technical care to see this response through.

Note: If your organization needs support with your Node estate, reach out, NodeSource can help.

Driving Open Source Security Upstream

Our commitment to security starts at the core of the open-source ecosystem. When the eMudhra vulnerability was disclosed, Node.js releases on October 21st (versions 26.12.1, 24.22.1, and 22.23.4) quickly updated the CA bundle to remove two emSign roots. Because Node.js can also be configured to trust external or operating system certificate stores that might still contain these compromised roots, an additional patch was written to ensure Node.js forcefully rejects any TLS chain containing one of the eight compromised public keys, regardless of the underlying trust store.

Being able to support this critical upstream effort was made possible through our partnership with the OpenJS Foundation. This initiative supports the Node.js Security Engineer in Residence role, helping ensure dedicated focus when urgent security events arise. We are deeply grateful for our team members and fellow core maintainers who dropped everything on short notice, working through complex dependency trees and tight timelines to coordinate fixes under embargo.

Securing the Ecosystem via NodeSource Distributions

Maintaining the official NodeSource Node.js Binary Distributions means our infrastructure team bears a shared responsibility to the millions of developers reliant on these pipelines. When upstream patches landed, team members worked diligently to package and test hardened binaries across multiple Linux environments, helping deliver fixes to community package managers as swiftly and safely as possible.

Translating Upstream Fixes to N|Solid Deployments

In parallel with the public distributions, engineering teams turned their attention to the N|Solid runtime updates. Thanks to early coordination during regular maintainer calls, the team was able to plan out the necessary update paths cleanly alongside the public releases.

For N|Solid v6.3.9 (spanning Node.js 22 and 24), our engineers carefully integrated the upstream Node.js 24.22.1 and 22.23.4 changes, while conducting additional dependency reviews across the N|Solid stack to ensure complete coverage.

Intelligent Remediation and VEX Exceptions

Rather than applying automated patches indiscriminately, the team prioritized thorough investigation—tracing code paths to understand real-world impact and documenting findings clearly for users. For this release, the team addressed three specific dependency security items:

  • CVE-2026-93748: Mitigated by updating npm’s http-cache-semantics dependency to version 4.3.0.

  • CVE-2026-104844: Mitigated by updating postcss-selector-parser to version 7.1.7.

  • CVE-2026-93687: Flagged in the braces dependency of our ncm-ng package. After a thorough investigation of how this dependency is utilized, our team determined the vulnerability does not affect N|Solid. Rather than making an unnecessary code change, we documented this assessment as an OpenVEX exception, which we distribute alongside N|Solid.

Alongside these security updates, N|Solid v6.3.9 also ships with multiple in-progress improvements to tracing, StatsD, event loop metrics, profiling configuration, and worker handling, alongside OpenTelemetry C++, gRPC, and protobuf upgrades.

Following code reviews, extensive QA testing, and release publishing, team members spent thoughtful time in support channels—answering questions, providing context, and helping teams navigate the update smoothly. From initial pull requests to final customer check-ins, we are immensely proud of and thankful for the dedication, technical rigor, and spirit of collaboration shown by everyone involved.

The NodeSource platform offers a high-definition view of the performance, security and behavior of Node.js applications and functions.

Start for Free