OpenSSL 4.1.0-beta1
2026-09-24T08:51:57Z•3043aae29cc84cf105e9c141d1d4458160f79ae9383425bddcaa5f396551b4c3
CVE-2026-14456CVE-2026-14457CVE-2026-18798CVE-2026-34182CVE-2026-45447CVE-2026-54874CVE-2026-54876CVE-2026-63072CVE-2026-63073CVE-2026-63074CVE-2026-63075CVE-2026-63076CVE-2026-75803AEADCMPCMSDTLSOpenSSLOpenSSL-3.0.xOpenSSL-3.4.xOpenSSL-3.5.xOpenSSL-3.6.xOpenSSL-4.0.xOpenSSL-4.1.0PKCS7QUICcertificate-validationcryptographic-librarydenial-of-servicedouble-freeheap-buffer-overflowmemory-safetysecurity-updateuse-after-free
What happened
OpenSSL release feed covering OpenSSL 4.1.0 alpha/beta feature previews and multiple security patch releases across supported branches. The 2026-08-25 patches address memory-safety issues, denial-of-service conditions, cryptographic verification flaws, format-string handling, and AEAD forgery risks. The highest stated severity is High in OpenSSL 4.0.1; other listed patch releases describe their most severe issue as Moderate. Organizations should prioritize upgrading affected OpenSSL installations, particularly those using QUIC, DTLS, CMS, CMP, PKCS7, RPK, OCSP, or AEAD functionality.
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- openssl_releases
- Record identifier
- 3043aae29cc84cf105e9c141d1d4458160f79ae9383425bddcaa5f396551b4c3
- Enrichment time
- 2026-09-24T08:51:57Z
- AI-assisted enrichment
- Yes
This record may overlap with other records. Its enrichment can be incomplete or wrong, and machine assistance was used. Validate consequential decisions against the linked source and your own environment.