Software's conformance to standards and its certification is not the pinnacle to shoot for. It is the absolute lowest bar.

Security release pre-alert:

We will release new versions of Node.js 22, 24, and 26 release lines on or shortly, after 2026-11-11 in order to address security vulnerabilities.

The highest severity issue fixed in this release is HIGH.
nodejs.org/en/blog/vulner…

Security is a first-class topic at @NodeConfEU 2026. @_panva on post-quantum cryptography in Node.js, Zbyszek Tenerowicz on getting ahead of supply-chain attacks, Mikola Lysenko on deleting all CVEs. The conference we need right now in the @nodejs space.

This is possible on nightly now and the next 26.x release possibly tomorrow. Node.js loads OpenSSL STORE provider backed keys. In these examples a tiny KMS one i'm cooking up, in CI we're testing with pkcs11-provider.

The URL input being resolved with a STORE is what's new.

🥁 𝐒𝐩𝐞𝐚𝐤𝐞𝐫 𝐀𝐧𝐧𝐨𝐮𝐧𝐜𝐞𝐦𝐞𝐧𝐭🎙️
Thrilled to have @_panva on the NodeConf EU 2026 stage! He'll tell us the story of "𝐏𝐨𝐬𝐭-𝐐𝐮𝐚𝐧𝐭𝐮𝐦 𝐂𝐫𝐲𝐩𝐭𝐨𝐠𝐫𝐚𝐩𝐡𝐲 𝐢𝐧 𝐍𝐨𝐝𝐞.𝐣𝐬".
🎟️Don't miss it out, secure your tickets nodeconf.eu

Did you move off of Node.js v20.x yet? There are only a couple weeks util its EOL. Save yourself the headache of scrambling to upgrade next year and jump straight to v24.x LTS

v24.x has a host of improvements I contributed that are not present on v22.x:
- Post-Quantum Digital Signatures and Key Agreement/Encapsulation in node:crypto and Web Cryptography
- (backport ready and pending) raw private/public/seed key gen and import formats

⚠️ Update: The Node.js project's security bug bounty program is being paused.

Reporting remains unchanged, and so does our commitment to security.

More details here: nodejs.org/en/blog/announ…

Introducing CWS, CSS Web Signatures. A security token scheme that runs entirely in the browser's style engine. No JavaScript. No WebAssembly. No server-side computation.

Spec + interactive demo: panva.github.io/CS24

CS24 provides exactly 0 bits of security. The key is displayed on screen, believed to be the least secure key storage mechanism ever devised. The 24-bit key space is exhaustible in milliseconds, though "somewhat longer using CSS."

The payload supports 3 ASCII characters. Messages like "Hi!", "lol", and "why" are covered. Longer messages are left as future work that SHOULD NOT be undertaken.

panva.github.io/CS24/rfc-cs24.…

yay or nay?

When it comes to JWTs issued for "yourself" the JWE format is far superior to JWS. Just let go of the HMAC JWS algorithms and use JWE direct encryption instead.

You get confidentiality and it forces use of correct-length keys.

await new jose.EncryptJWT > await new jose.SignJWT

Time to catch up with wicg.github.io/webcrypto-mode… @bunjavascript @deno_land @Cloudflare

WPTs are available. Browsers started going through their implementations.

These algorithms power HPKE implementations (github.com/panva/hpke)

HPKE vector validation in *your* browser (and the implementation project's github actions pipeline)

panva.github.io/hpke/

Let's get some ⭐⭐⭐ going 🙏
github.com/panva/hpke

Hybrid Public Key Encryption (HPKE) for Node.js, Browser, Cloudflare Workers, Deno, Bun, and other Web-interoperable runtimes.

Fully tree-shakeable. Fully typed. Extensible.

my new project's build script, tsc is then only used to emit declarations and a source map, the published files are index.(js, ts, d.ts(.map))