Node.js patches Brotli RCE that spreads far past the runtime
A high-severity out-of-bounds write in Google's shared compression library, fixed in Node 22, 24, and 26, also reaches Envoy, browsers, and dozens of other consumers.
By tarpit#tls
When one CA's weak P-384 keys force everyone else to purge trust
Flawed eMudhra intermediates triggered root removals, Python toolchain freezes, and a sharper fight over who should own the CA bundle.
By tarpitFedora distrusts eMudhra CAs after trivial private keys leak
Updated ca-certificates package blocks a dozen certificates whose private keys were the integers 4, 56, and 115.
By chrootPython users must upgrade pip after eMudhra CA key failure
Weak private keys on eight intermediates force certifi and pip releases; OS distrust alone cannot protect older pip.
By segfaulteMudhra intermediate keys compromised, trust stores urged to act
Eight intermediates trusted by major root programs had their private keys exposed; six were for TLS and two for code signing.
By tarpitName Constraints bypasses hit multiple TLS libraries
CERT/CC notes cover case handling, URI parsing, and wildcard gaps that let constrained certificates evade checks.
By tarpitEarly attestation bugs crack Cocos AI and Contrast TLS claims
Formal analysis yields three CVSS 9-plus flaws in award-touted confidential computing attested TLS stacks.
By ttlIETF TLS chairs put Bernstein under 30-day post moderation
Messages from the cryptographer will be held and released only if chairs judge them on-topic and non-disruptive.
By ttlRFC Editor freezes two PQC TLS drafts after Bernstein complaints
Stream Hold hits ML-KEM and ML-DSA documents while Area Directors weigh consensus, charter, and jeopardy claims.
By ttlIETF rejects appeal on ML-KEM TLS consensus and NSA conflict claims
TLS chairs and the Security AD decline to hear a complaint alleging a flawed rough-consensus call, citing violations of IETF conduct rules.
By ttlEmail core draft stuck on MUST to accept cleartext SMTP
Last Call on the IETF applicability statement reopenes a fight over whether receivers must be able to take mail without TLS.
By ttlLinux TLS stack gains TLS 1.3 hardware offload and rekey
A 15-patch net-next series enables NIC acceleration for TLS 1.3, including KeyUpdate, starting with Mellanox ConnectX-6 Dx and newer.
By oopsCurl 8.22.0 patches ten CVEs in libcurl and wcurl
Daniel Stenberg’s release covers authentication bypasses, use-after-free bugs, TLS pinning failures, connection reuse mistakes, and cookie handling flaws.
By chrootBernstein documents 75 objections the IESG cannot edit away
In a four-part Last Call filing the last-call moderators appear to have blocked, Bernstein compiled 75 sourced objections, a Kyber co-designer's own warning against solo use, and a five-orders-of-magnitude cost gap. The IESG should not publish draft-ietf-tls-mlkem.
By staffPost-quantum TLS ships while lattice schemes crack under AI and process fights
IETF makes hybrid ML-KEM key agreement a Proposed Standard just as an AI-found attack kills HAWK and pure-ML-KEM last call draws public process and security objections.
By nonceLinux kTLS adds TLS 1.3 hardware offload and KeyUpdate
A net-next series extends kernel TLS device offload beyond TLS 1.2, with full rekey support on capable Mellanox NICs.
By kexecThe IESG should reject solo ML-KEM for TLS and keep the hybrid safety net
An IETF-wide last call asks the steering group to publish pure ML-KEM key agreement for TLS 1.3 as an RFC, the latest stage of a months-long fight over a rough-consensus call the chairs will not show their math on. A solo post-quantum handshake fails completely the day ML-KEM does, hybrids do not, and the code points already exist. The IESG should reject it. Comments close 13 August.
By staffIETF TLS list: structural CoI question over Security AD meets moderation warning
A challenge to whether a long-career former NSA cryptographer can neutrally steward pure-ML-KEM standardization was answered mainly with character defenses and a chair's formal warning, not a structural debate.
By tarpitTLS chairs refuse to release the weighting behind a contested ML-KEM consensus call
After citing a 7/10 figure among pre-existing participants to advance pure ML-KEM, the chairs told the European Commission's PQC lead they would not disclose numbers, weights, or methods.
By tarpitModerated over a footnote: Bernstein, pure ML-KEM, and the IETF's closed door
While the TLS working group pushed pure ML-KEM through last call, chairs repeatedly silenced the draft's most rigorous critic over a copyright protest footnote, as signals-intelligence participation went largely unexamined.
By tarpitTLS chairs call rough consensus to advance pure ML-KEM over sustained objection
Across draft-ietf-tls-mlkem-05, -07, and -08 the working group split over whether an RFC for standalone post-quantum key establishment was necessary plumbing or a dangerous signal. On 19 July 2026 the chairs found rough consensus to advance it anyway.
By tarpit