CVE-2026-43823 swift-crypto vulnerability
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.
Quick answer
Apple swift-crypto should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- < 4.5.1
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-43823 affects swift-crypto and involves denial of service. A remote or untrusted peer may consume excessive resources or crash the affected service. Prioritize internet-facing, privileged, automation, and production deployments. Upgrade swift-crypto to 4.5.1 or a later vendor-supported fixed release.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses swift-crypto.
- Compare the installed version with the recorded affected range: < 4.5.1.
- Upgrade swift-crypto to 4.5.1 or a later vendor-supported fixed release.
- Until patched, limit untrusted files and peers, apply resource limits, and isolate the affected parser or service.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to swift-crypto; remove access that is not required.
- Review application, system, proxy, and audit logs for requests and behavior linked to the affected feature and CVE.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-43823 in place.
- Use a safe regression test to confirm the affected denial of service path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Trusted references
FAQ
What is affected by CVE-2026-43823?
Apple swift-crypto versions listed as affected should be reviewed: < 4.5.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.