Debian has backported fixes from the Node.js project's June and July 2026 security releases into its own Node.js packages: DSA-6517-1 for Debian 13 (trixie) on 26 September 2026 and DLA-4809-1 for Debian 12 (bookworm) on 1 October. They cover HTTP/2 memory and use-after-free bugs, TLS hostname-verification bypasses and Permission Model escapes. If you deploy Node.js applications from Debian's nodejs package, this update applies to you.
At a glance
| Item | Details |
|---|---|
| Source package | nodejs (binary packages nodejs and libnode115 on trixie, libnode108 on bookworm) |
| Fixed versions | 20.19.2+dfsg-1+deb13u3 (trixie), 18.20.4+dfsg-1~deb12u3 (bookworm) |
| Advisories | DSA-6517-1 (26 Sep 2026, 17 CVEs), DLA-4809-1 (1 Oct 2026, 11 CVEs) |
| Example CVEs | CVE-2026-48618, CVE-2026-48933, CVE-2026-56846, CVE-2026-56848, CVE-2026-58043 |
| Severity | High (Node.js rates the most serious fixes high) |
| Known exploitation | None in CISA KEV (30 Oct 2026) |
What the vulnerabilities are
Debian sums up the trixie fixes as denial of service, permission model bypass, incorrect certificate validation or information disclosure; the bookworm DLA lists the same categories without the permission model. The underlying issues come from the Node.js June 2026 and July 2026 security releases:
- Remote crashes and memory exhaustion (high). CVE-2026-56846 lets retained HTTP/2 header blocks get around
maxSessionMemory; CVE-2026-56848 is a heap use-after-free when HTTP/2 sending is re-entered during receive; CVE-2026-48933 aborts the process through an integer overflow in WebCrypto AES. CVE-2026-58042 can abortdns.resolveAny()on responses with many A records. - TLS identity checks. CVE-2026-48618 (high) can bypass wildcard-depth hostname checks through Unicode dot separators. CVE-2026-48928, CVE-2026-48934 and CVE-2026-56850 concern SNI case matching, session reuse with a different server name and reuse of mTLS identities across certificates.
- Permission Model. CVE-2026-58043 (high) can over-grant filesystem access under
--permission. This matters only if you use Node's--permissionflags to restrict what code can access. - HTTP client behaviour. CVE-2026-48930 (NUL bytes in hostnames) and CVE-2026-48931 (a response-queue race in
http.Agent).
Why Debian's Node.js is different
Debian 13 ships Node.js 20 and Debian 12 ships Node.js 18. According to the Node.js release schedule, upstream support for Node.js 18 ended on 30 April 2025 and for Node.js 20 on 30 April 2026, and the June and July 2026 posts announce new versions only for the 22.x, 24.x and 26.x lines, noting that end-of-life versions are always affected when a security release occurs. Debian keeps its own packages patched by backporting, which takes time and is not always complete: on 31 October 2026 the Debian tracker listed several CVEs from Node.js's October 2026 security release, such as CVE-2026-106072 in TLS hostname verification, as still open for both releases.
Are you affected?
apt policy nodejs
node --version
dpkg -l nodejs 'libnode*' | grep '^ii'Debian's package reports v20.19.2 or v18.20.4; the Debian revision in apt policy tells you whether the fix is installed. If node --version shows 22.x or later, your Node.js does not come from Debian's archive (for example NodeSource or official binaries) and you should follow the upstream releases instead.
How to update
sudo apt update
sudo apt install --only-upgrade nodejs libnode115 # Debian 13
sudo apt install --only-upgrade nodejs libnode108 # Debian 12Restart or reboot?
No reboot. Every running Node.js process keeps the old code until it restarts, so restart your application services, for example sudo systemctl restart myapp for a systemd unit, or your process manager's restart command.
Sources
- security-tracker.debian.org/tracker/DSA-6517-1
- debian.org/security/2026/dsa-6517
- lists.debian.org/debian-security-announce/2026/msg00430.html
- security-tracker.debian.org/tracker/DLA-4809-1
- lists.debian.org/debian-lts-announce/2026/10/msg00001.html
- security-tracker.debian.org/tracker/source-package/nodejs
- nodejs.org/en/blog/vulnerability/june-2026-security-releases
- nodejs.org/en/blog/vulnerability/july-2026-security-releases
- nodejs.org/en/blog/vulnerability/october-2026-security-releases
- github.com/nodejs/Release
- raw.githubusercontent.com/nodejs/Release/main/schedule.json
- cve.org/CVERecord?id=CVE-2026-48618
- cve.org/CVERecord?id=CVE-2026-56848
- cve.org/CVERecord?id=CVE-2026-58043
- cve.org/CVERecord?id=CVE-2026-106072
- packages.debian.org/source/trixie/nodejs
- packages.debian.org/source/bookworm/nodejs
- cisa.gov/known-exploited-vulnerabilities-catalog
Comments
0 total · 0 threads