Node.js 27.0.0-alpha.0.1.1 ships a macOS notarization fix and a Linux security change slipping by unnoticed
The second alpha of Node's new annual release line quietly hardens Linux binaries while fixing a macOS Gatekeeper annoyance that's bothered developers for years.
Node.js just shipped the second alpha version of the upcoming 27 series. The only official "notable" change is a macOS notarization fix. Not a feature. A fix for whether Apple will even let your downloaded binary run.
The change, landed by Ulises Gascón, makes the tarball build submit bin/node to Apple's notary service via notarytool, then verify a ticket actually came back, failing the build if it doesn't. The .pkg installer had long been properly notarized and stapled. The tarballs never were. Download the portable .tar.gz, run node, and occasionally Gatekeeper would wave you off with an "unidentified developer" warning.
The real change that didn't get the spotlight
While only one item earned the "notable" badge, the commit list tells a different story. The most consequential change here never grabbed a headline: PIE is now enabled on Linux.
Position Independent Executable. It reads like an acronym for acronyms, but the payoff is real. Modern distros ship PIE so their ASLR actually does something useful. Node's own glibc x64 binaries didn't. macOS got PIE back in 2020.
The performance cost? Maintainer Marcos Collina measured it directly. Roughly +1 ms, about 4%, of per-process startup, with no measurable steady-state or HTTP-throughput impact. The cost is just the dynamic loader doing relative relocations.
The upside is more concrete. Per the original proposal, had PIE already been in place, a recent exploit (referenced as CVE-2026-111497) would probably have rated "High" instead of "Critical." That's the kind of math that makes security engineers nod approvingly.
A --shared-simdutf tweak by Yao Zi also keeps shared builds from bundling the vendored copy of the Unicode library, trimming size and dodging duplication. The usual churn rounds out the build: nghttp3 to 1.19.0, mk-ca-bundle to 1.35, V8 backports, a batch of docs clarifications, and deflake fixes for flaky tests.
What 27 actually is
This is the first release line under Node's brand-new annual model. One major per year, landing in April, with every release now becoming LTS. The old odd/even split is gone. Version numbers track the calendar year: 27 rides into 2027.
The Alpha phase runs roughly October through March. It exists so library authors can catch breaking changes months before 27 ships. These builds deliberately allow semver-major changes and get run through CITGM, which tests real open-source packages against the upcoming Node to breakage early.
The supported production lines right now are Node 26 "Lithium" (Active LTS), 24 "Krypton," and 22 "Jod." Node 27 is alpha only, and it is not an upgrade.
The 27 line is already carrying roughly 100 semver-major commits toward the April 2027 Current release. A few will bite. The default heap limit shifts to half of physical RAM, clamped between 256 MB and 4 GB, and memory held by Buffer and ArrayBuffer now counts toward it. The serialization format behind v8.serialize(), structuredClone(), and postMessage() is changing too, and data written by Node 27 won't read back on older versions.
Then OpenSSL 4.1.0 ships in the bundle, and the module bump to 153 means your native addons have to be rebuilt from scratch. On the HTTP side, keepAliveTimeout jumps from 5s to 65s. Intel Macs lose more ground as well — no darwin-x64 tarball ships for the 27 Alpha at all.
Head here to the release announcement.
