Skip to content
TrustList
Security advisories

OpenSSL fixes three Low flaws, with 4.1.1, 4.0.4 and 3.5.10 due 1 December

Editorial

By TrustList Editorial

The QUIC server memory flaw CVE-2026-124709 is reachable in the default configuration; the TLS 1.3 Suite B read and the PEM use-after-free need unusual application settings.

About OpenSSL fixes three Low flaws, with 4.1.1, 4.0.4 and 3.5.10 due 1 December

OpenSSL fixes three Low flaws, with 4.1.1, 4.0.4 and 3.5.10 due 1 December

17 November 2026: The OpenSSL project has disclosed three vulnerabilities, all rated Low, in its TLS, PEM and QUIC code: CVE-2026-124709, a QUIC server memory leak reachable in the default configuration; CVE-2026-35190, an out-of-bounds read in TLS 1.3 key-share handling; and CVE-2026-107493, a use-after-free in PEM certificate reading. None is reported as exploited. The fixes are already in the public repository, and releases carrying them are scheduled for 1 December 2026.

Not yet independently verified. This rests on the OpenSSL project's own advisory of 17 November 2026, read on 20 November. The fixed releases are scheduled, not yet published, and the advisory notes that its online version may be updated. We will update this when it can be confirmed, and remove this note.

The one that reaches default servers

CVE-2026-124709 affects QUIC servers built on OpenSSL 4.1, 4.0 and 3.5. When a server rejects a stream the client opened, and the client resets that stream before the rejection is sent, OpenSSL keeps the stream's state for the life of the connection. A client that completes a handshake and keeps opening and resetting streams can grow server memory until the process runs out and every connection on it drops.

The advisory says the default configuration reaches this path once a connection has a default stream, as the project's own tutorial server does. Each retained stream costs about 300 bytes and the client's stream credit limits the pace, which is why the project rates it Low. Servers that accept long-lived QUIC connections from the internet are the ones to patch first.

Two flaws behind unusual settings

CVE-2026-35190 only affects servers whose application calls SSL_CTX_set_cert_flags() with the Suite B flag and leaves TLS 1.3 on. A client offering only non-Suite B groups, such as X25519, makes the server read past a fixed array. Nothing is disclosed; on builds with sanitizers or hardened allocators the read can crash the process. The stock s_server -suiteB_128 option is not affected, and OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected.

CVE-2026-107493 is in PEM_X509_INFO_read_bio_ex() and the three related functions. If an application passes in an existing stack of entries and the read fails on malformed PEM data, OpenSSL frees every entry but leaves the pointers in the stack. OpenSSL's own callers, including TLS loading of CA certificates, always pass NULL and are safe. This one reaches back to 1.0.2.

Versions to move to

  • OpenSSL 4.1: upgrade to 4.1.1
  • OpenSSL 4.0: upgrade to 4.0.4
  • OpenSSL 3.5: upgrade to 3.5.10
  • OpenSSL 3.0, 1.1.1 and 1.0.2 (PEM flaw only, premium support customers): 3.0.24, 1.1.1zk and 1.0.2zt

All three issues are outside the FIPS module boundary. OpenSSL 3.1, 3.2, 3.3, 3.4 and 3.6 are out of support and were not analysed, so systems on those branches have no stated fix. Teams that ship OpenSSL inside appliances or containers should expect their vendors' builds to follow the 1 December releases rather than arrive with them.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in