
Image: Bun
Why it mattersAny team running Bun in production should upgrade. The change sits in the parts of the runtime that touch untrusted bytes first.
A JavaScript runtime reads the first byte from the network. It parses the certificates. Bun just rebuilt every one of those parts.
Bun 1.4.5 is a security release. The announcement on Bun's own blog is by Bun maintainer Dylan Conway. It lists the surfaces that changed: HTTP/3, HTTP/1.1, TLS, DNS and Zstandard. Those cover the Bun.serve, Bun.connect, Bun.dns and Bun.zstdDecompress APIs. They cover the node:tls, node:https, node:http, node:quic, node:dns and node:zlib modules. They cover fetch and DecompressionStream. Bun says every protocol under them was reviewed.
The underlying updates, straight from the release page:
- lsquic, the QUIC library, moves from 4.9.4 to 4.11.2.
- c-ares, the async DNS resolver, moves from 1.34.8 to 1.34.9.
- SQLite moves from 3.53.4 to 3.54.1.
- llhttp, the HTTP parser, moves from 9.4.2 to 9.4.4.
- BoringSSL, the TLS stack, moves from the August 2026 snapshot to the November 2026 snapshot.
Bun's note about SQLite is worth reading twice. SQLite 3.54 no longer lets ALTER TABLE add, rename or drop a column named rowid, oid or _rowid_. It also runs the setAuthorizer() callback for functions used inside DEFAULT expressions. On macOS, Bun uses the system SQLite. A project that migrates column names on that platform may now behave differently.
The bug fixes under the headline
Four fixes in node:crypto and node:tls line up Bun's behaviour with Node.js. RSA signatures with SHA-3, SHA-512/224, SHA-512/256 and RIPEMD-160 no longer throw ERR_OSSL_RSA_UNKNOWN_ALGORITHM_TYPE. An expired certificate from an unknown issuer now reports CERT_HAS_EXPIRED, matching Node. The allowPartialTrustChain flag with CRL now requires the chain to end at a self-issued certificate, again matching Node.
Custom root certificates are validated more strictly. Bun says a few legacy roots that Node also rejects are now rejected here too. Bun's own bundled roots are not affected.
The release also lists "various stability issues in HTTP/3 and node:quic" as fixed. Bun does not name specific CVEs on this release page. The record on the blog is the list of dependency version bumps and the behaviour changes above.
For a team on Bun
A security release in a runtime deserves a different review than a monthly dependency bump. The ones that matter change HTTP parsing, certificate chain building or DNS resolution. This release changes all three.
For a team already running Bun, the upgrade path is the standard one and the public APIs behave the same. For a team running a hosted service that pins a runtime version, the Docker tag is what to move. A team on a legacy root certificate Node also rejects may lose that root. Measure first, then upgrade.
Source
- Bun, Bun v1.4.5, by Dylan Conway.
- GitHub, oven-sh/bun v1.4.5 release page.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.


