CVE-2026-43823: Double Free
When initializing an RSA public key from DER or PEM bytes throws an error, the EVPPKEY is double-freed: first in the catch block, then in the deinit. This can lead to a crash on future memory allocations. This double-free manifests when BoringSSL cannot decode the public key from the bytes provided. This vulnerability is addressed in swift-crypto version 4.5.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
swift-cryptoto a version that resolves this vulnerability.Fixed in 4.5.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43823?
CVE-2026-43823 has a severity rating of 7.5, classified as high.
How do I fix CVE-2026-43823?
To fix CVE-2026-43823, ensure you update your BoringSSL or swift-crypto libraries to the latest patched version.
What risks does CVE-2026-43823 pose?
CVE-2026-43823 poses a risk of application crashes due to memory management issues caused by double freeing of memory.
Which software is affected by CVE-2026-43823?
CVE-2026-43823 affects BoringSSL and swift-crypto software.
What type of vulnerability is CVE-2026-43823?
CVE-2026-43823 is classified as a double free vulnerability.