Bun 1.4.5 patches TLS, DNS and HTTP/3 bugs in one security release
Bun's latest update bumps BoringSSL, lsquic, c-ares and llhttp, fixing a crypto bug and several TLS and HTTP/3 stability issues along the way.
Bun 1.4.5 shipped on 19 November as what the Bun team calls a security release, bumping the bundled versions of BoringSSL, lsquic, c-ares, SQLite and llhttp. The affected surface is wide: Bun.serve, Bun.connect, Bun.dns, and the node:tls, node:https, node:http, node:quic, node:dns and node:zlib compatibility layers, plus fetch and DecompressionStream.
Some of the specific fixes: RSA signatures using SHA-3, SHA-512/224, SHA-512/256 or RIPEMD-160 used to throw ERR_OSSL_RSA_UNKNOWN_ALGORITHM_TYPE in node:crypto; expired certificates from an unknown issuer now correctly report CERT_HAS_EXPIRED, matching Node’s behaviour; and custom root certificates go through stricter validation, so some legacy ones may now be rejected. Bun’s own bundled roots aren’t affected. The release notes also mention unspecified stability fixes in HTTP/3 and node:quic.
bun upgrade
Why it matters: if you’re running Bun.serve or anything that touches TLS, HTTP/3 or DNS in production, this is worth pulling in promptly. Bun itself is labelling it a security release, which is reason enough to update even without more detail.
The caveat: the release notes don’t give CVE numbers, severity ratings, or say whether any of these bugs were being exploited. Treat it as “the vendor says update,” not a scored, disclosed vulnerability.