Skip to content

chore: upgrade Node.js to 24.22.3 for October and November 2026 security releases #258

Open

Description

@Alessandro100

Summary

Update (2026-11-12): target bumped from 24.22.1 to 24.22.3. Node.js shipped a second security release on 2026-11-10 (16 fixes, 7 high, mostly HTTP/2, HTTPS and TLS). 24.22.3 contains both the October and November fixes. PR: #264

The Node.js October 21, 2026 and November 10, 2026 security releases fix several high-severity CVEs that affect the version we build and run on (24.12.0). The fixed version for our release line is 24.22.3.

We are not currently exposed through our own code (see Impact), so this is
routine maintenance rather than an incident. It should be done before we add
any server-side fetching of user- or producer-supplied URLs.

Advisories:

Affected CVEs

October 2026 (fixed in 24.22.1)

CVE Severity Issue
CVE-2026-111497 High (possible RCE) Brotli decoder out-of-bounds write when decompressing malformed input via node:zlib
CVE-2026-105483 High tls.checkServerIdentity() does not treat fullwidth-digit IPs as IPs (24.x / 26.x only)
CVE-2026-106069 High Leading-zero IPv4 literals parsed inconsistently, so a certificate can be validated against the wrong IP
CVE-2026-105482 High dns.resolve*() / dns.reverse() truncate hostnames at a NUL byte, which can defeat allowlists

The same release also updates Undici and c-ares, and removes the compromised
eMudhra intermediate CA from Node's bundled CA store.

November 2026 (fixed in 24.22.3)

16 flaws in total, 7 rated high. The ones affecting 24.x that are publicly described:

CVE Severity Issue
CVE-2026-123865 High Client can make a default HTTP/2 server hold memory and file descriptors permanently
CVE-2026-123874 High Memory corruption when serving files via HTTP/2 respondWithFile() / respondWithFD()
CVE-2026-126051 High TLS server crash when using SNICallback, OCSP/session hooks, or server.addContext()
CVE-2026-123872 High TLS 1.2 renegotiation lets a client move to a stricter hostname's client-cert rules without meeting them
CVE-2026-123863 n/a Unauthenticated crash of a default HTTP/2 server that replies before the request body arrives
CVE-2026-123864 n/a HTTPS server memory leak across connections (can include TLS private keys) with a specific flushHeaders()/end() pattern; plain node:http not affected
CVE-2026-123866 n/a HTTP/2 memory disclosure to the client (client-triggerable on 24.22.0+)
CVE-2026-123875 Medium Cancelling HTTP/2 file downloads can crash the server

Current state

Impact

Low today. Exploiting these requires attacker-controlled input to reach the
vulnerable code on the server:

  • Brotli (111497): Node's fetch decompresses Content-Encoding: br
    responses automatically. All server-side fetches go to hardcoded, trusted
    hosts over HTTPS (Mobility Feed API, Google auth, Google Sheets). Incoming
    request bodies are not decompressed. The only direct node:zlib use
    (api/gtfs-diff-v2 route) compresses with gzip and does not decompress.
  • TLS (105483, 106069): no server-side code connects to user-supplied
    hosts or IP literals.
  • DNS (105482): node:dns is not used.
  • HTTP/2, HTTPS, TLS server (November): the app does not create its own
    http2, https or tls servers. Next.js serves over plain node:http
    and Vercel's edge terminates TLS and HTTP/2 in front of the functions.

This changes if the server starts fetching URLs it does not control (for
example, the GTFS diff tool downloading producer feeds). At that point the
Brotli issue in particular becomes directly reachable.

Tasks

Acceptance criteria

  • CI workflows build on Node 24.22.3 and pass
  • Production runtime is confirmed to be on 24.22.3 or later

Activity

  1. added
    tech-debtShortcuts, workarounds, or code that needs refactoring or cleanup
    on Oct 26, 2026
  2. changed the title [-]chore: upgrade Node.js to 24.22.1 for October 2026 security release[/-] [+]chore: upgrade Node.js to 24.22.3 for October and November 2026 security releases[/+] on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    tech-debtShortcuts, workarounds, or code that needs refactoring or cleanup

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions