CVE-2026-43823
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk36th percentile - higher than 36% of all known CVEs
Summary
In the swift-crypto library before version 4.5.1, when initializing an RSA public key from DER or PEM bytes fails, a double-free occurs. This can cause a crash on future memory allocations. The issue manifests when BoringSSL cannot decode the key.
Risk Assessment
A double-free can crash the application, leading to denial of service and potential system instability.
Recommendation
Update swift-crypto to version 4.5.1 or later, which includes a fix for the double-free.
Other vulnerabilities in swift-crypto
See all- CVE-2026-86983Low risk· EPSS 5%
A remote attacker may be able to terminate a process that passes attacker-controlled input to the P-384 VOPRF API without bounding its length. This vulnerability is addressed in swift-crypto version 5.0.3.
- CVE-2026-28815High
A remote attacker can supply a short X-Wing HPKE encapsulated key and trigger an out-of-bounds read in the C decapsulation path, potentially causing a crash or memory disclosure depending on runtime protections. This issue is fixed in swift-crypto version 4.3.1.
Original NVD description (English source)
When initializing an RSA public key from DER or PEM bytes throws an error, the EVP_PKEY* 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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS