RepoJournal
Node.js

@nodejs

The Node.js runtime — every backend team's CVE source of truth

Pick a date

The Wire · Showcase

NODE CLOSES CRASH BUGS IN URL AND FFI MODULES WHILE SHIPPING BUILD INFRASTRUCTURE UPGRADES

By RepoJournal · Filed · About Node.js

Node patched a process crash in pathToFileURL() that could be triggered by malformed UNC hostnames, while simultaneous fixes to FFI garbage collection and debugger refactoring land across the core.

The url module now guards against crashes when pathToFileURL() receives malformed UNC hostnames [1], a fix that closes a real stability gap in Windows path handling. Meanwhile, the FFI binding layer got a critical safeguard: premature garbage collection of DynamicLibrary objects is now prevented [2], addressing a bug that could corrupt native bindings at runtime. The debugger saw internal housekeeping completed [3] as ProbeInspectorSession and helpers moved to separate files, finishing work that had been blocked by an unrelated test failure. On the build side, Node's infrastructure now passes correct Rust targets for macOS cross-compilation [4], ensuring arm64→x64 builds via Rosetta work with the rustc compiler. The broader build pipeline also updated gn on ppc64le and s390x machines [5] for V8 compatibility, and staged v26.x release assets [7] as the release cycle progresses. Temporal also joined the frozen intrinsics list [6], hardening the security sandbox.

Action items

References

  1. [1] url: process crash via malformed UNC hostname in pathToFileURL()
  2. [2] ffi: prevent premature GC of DynamicLibrary
  3. [3] debugger: move ProbeInspectorSession and helpers to separate files
  4. [4] build: add rust target for macOS cross compiles
  5. [5] ansible: update gn on Linux ppc64le and s390x
  6. [6] lib: add Temporal to frozen intrinsics
  7. [7] build: add expected assets for v26.x

FAQ

What changed in Node.js on May 1, 2026?
Node patched a process crash in pathToFileURL() that could be triggered by malformed UNC hostnames, while simultaneous fixes to FFI garbage collection and debugger refactoring land across the core.
What should Node.js teams do about it?
Test pathToFileURL() with Windows UNC paths in your test suite — patch is live • Verify FFI bindings aren't garbage collected prematurely if you use native modules • Watch v26.x asset staging — release machinery is warming up

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • 14 famous open source orgs
  • One wire per day
  • Public, generic
  • Read on the web, when you remember

Your wire

  • Up to 1,500 of your repos - orgs, deps, vendors
  • Morning and evening briefs
  • Action items routed to your team
  • Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.