7.5High
Apple Swift-Crypto
CVE-2026-43823
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.
What this means for your business
- It affects Apple Swift-Crypto. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.3% chance of attack attempts being seen in the next 30 days, ranking above 17% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Apple Swift-Crypto, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 7.5 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Weakness
- CWE-415
- Assigned by
- product-security@apple.com
Dates
- Published
- 2026-07-23
- Last modified
- 2026-09-04
- Sources
- NVD
Affected products
- Apple Swift-Crypto3.2.0 - 4.5.1
As listed in the NVD configuration data. Not a statement about your estate.