OpenSSL's November Fixes Are a Build-Inventory Problem
OpenSSL published several fixes in November 2026, including issues that reach into QUIC, PEM certificate parsing, and CMS message encryption. Two are rated Low, while the CMS infinite-loop issue CVE-2026-107496 is rated High with a 7.5 score. The ratings differ, but the operational question is the same: which applications are using an affected OpenSSL build in a path that processes attacker-controlled input?
Three different failure modes
CVE-2026-95691 covers retransmitted QUIC CRYPTO frames that can cause a denial of service or disclose one byte of heap-adjacent data to a peer. The affected release ranges include OpenSSL 3.5 before 3.5.10, 4.0 before 4.0.4, and 4.1 before 4.1.1. The FIPS module is not affected because the QUIC implementation sits outside its boundary.
CVE-2026-107493 is a use-after-free in PEM_X509_INFO_read_bio_ex() when a caller supplies an existing stack and reading fails. Malformed PEM data can trigger the cleanup path, but only applications that pass the caller-owned stack are affected. OpenSSL itself does not use that pattern. Fixed builds include 3.5.10, 4.0.4, and 4.1.1, with corresponding fixes in older maintained branches.
CVE-2026-107496 is an infinite loop in CMS_encrypt() or CMS_encrypt_ex() when encrypting to an EC certificate whose group order is 1. An attacker who can choose the recipient certificate can keep the application consuming CPU. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds, which narrows the effective exposure for some deployments.
The first issue is network-protocol logic. The second is parser cleanup. The third is application-level cryptographic input. A vulnerability scanner that only checks the library version will identify candidates, but an operator still needs to know whether the application calls the relevant APIs and whether untrusted input can reach them.
Inventory beyond the package manager
List OpenSSL versions in base images, language runtimes, daemons, appliances, build agents, and statically linked binaries. A host package may be patched while a bundled application still carries an older library. Container images can also inherit an old libssl from a parent layer even when the application package was rebuilt.
Use the runtime loader output where possible:
openssl version -a ldd "$(command -v openssl)" For statically linked software, dependency manifests and binary symbols may be the only evidence. Record the vendor, build, and support branch for third-party appliances that embed OpenSSL.
Verify the behavior that matters
Update to the fixed build for each supported branch. Then test the application path that corresponds to the advisory. A QUIC service should reject malformed retransmitted CRYPTO frames without leaking data. A PEM import endpoint should fail cleanly on malformed input. A CMS encryption service should reject an EC certificate with group order 1 instead of looping.
Do not treat "Low" as "ignore indefinitely." Low severity often means a narrow precondition, not that the affected code is unreachable. The CMS issue demonstrates how an attacker-controlled certificate can turn a library edge case into an availability problem for a mail gateway, document-signing service, or encrypted-message workflow.

