Skip to content

OpenSSL’s November advisory: map exposure before the December 1 releases

קראו בעברית

Checked November 11, 2026.

On November 10, OpenSSL disclosed five Low-severity issues. Patches are in its public repository; releases containing them are scheduled for December 1, 2026. Teams can use this interval to identify exposed applications and prepare a tested update.

What needs checking

  • QUIC: CVE-2026-88822 concerns automatic peer-address detection; CVE-2026-95691 involves retransmitted CRYPTO frames. Impacts include connection failures, denial of service and limited information disclosure.
  • AES-GCM-SIV: CVE-2026-88823 affects fragmented additional authenticated data containing an empty update; CVE-2026-95692 concerns incorrect nonce lengths. These can undermine authentication or cause an out-of-bounds read.
  • CMS encryption: CVE-2026-107496 can hang encryption when an application accepts an attacker-controlled EC recipient certificate with group order 1. It is not a TLS handshake flaw.

Version boundaries

The first four issues affect the supported 4.1, 4.0 and 3.5 branches. The CMS issue also affects 3.0, 1.1.1 and 1.0.2; in 4.0 and later, it requires the enable-ec_explicit_curves build option.

Planned fixed releases are 4.1.1, 4.0.4 and 3.5.10. The advisory lists 3.0.24, 1.1.1zk and 1.0.2zt for premium-support customers. It says the FIPS modules are unaffected, but applications can still use affected code outside that module boundary. OpenSSL did not analyse the unsupported 3.1, 3.2, 3.3, 3.4 and 3.6 branches.

A practical preparation list

Our recommended next steps:

  1. Locate the actual dependency. Record the application's library and package source, including bundled copies. Ask its maintainer which listed paths are reachable and whether a vendor backport is available.
  2. Make the update reviewable. Record an owner, affected path, supplier's fix reference and planned test. Test a representative QUIC connection or CMS encryption flow where relevant.
  3. Use your supported delivery route. Do not substitute a repository checkout for a supported production package without a deployment review.
  4. Verify after rollout. Check the vendor release and the running process. A calendar date alone does not prove that a fix reached your application.

Scope: this is an advisory-based review, not a test of your installation or a claim of exploitation.

Primary sources

Post a Comment

Previous Post Next Post