0.0
NA
CVE-2026-43823
Swift-Crypto RSA Double Free Vulnerability
Description

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.

INFO

Published Date :

July 23, 2026, 3:17 p.m.

Last Modified :

July 23, 2026, 3:28 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-43823 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Apple swift-crypto
Solution
Update swift-crypto to version 4.5.1 to fix the double-free vulnerability.
  • Update swift-crypto to version 4.5.1.
  • Apply relevant security patches.
  • Test the application for stability.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-43823.

URL Resource
https://github.com/apple/swift-crypto/security/advisories/GHSA-8q93-f6xh-4f6f
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-43823 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-43823 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-43823 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-43823 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 23, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'Apple', 'product': 'swift-crypto', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '4.5.1', 'versionType': 'custom'}]}]
    Added Description 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.
    Added Reference https://github.com/apple/swift-crypto/security/advisories/GHSA-8q93-f6xh-4f6f
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.