CVE-2026-43823

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Double-free when parsing RSA public key fails · Advisory · apple/swift-crypto · GitHub

https://github.com/apple/swift-crypto/security/advisories/GHSA-8q93-f6xh-4f6f

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-main-24.18.0-0.5.hum12026-07-25redhat
redhatswift-lang-main-6.3.3-0.1.1.hum12026-07-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-28 02:52 UTCVendor advisory
  2. 2026-07-27 15:05 UTCEG score recompute
  3. 2026-07-27 14:13 UTCEPSS rescore
  4. 2026-07-27 02:40 UTCEG score recompute
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:53 UTCEG score recompute
  8. 2026-07-26 03:07 UTCEG score recompute
  9. 2026-07-25 14:18 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 18:22 UTCEG score recompute▲ 7.50
  12. 2026-07-23 18:21 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  13. 2026-07-23 16:11 UTCNVD update
  14. 2026-07-23 14:57 UTCEG score recompute
  15. 2026-07-23 14:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-43823?
CVE-2026-43823 is a high vulnerability published on July 23, 2026. 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…
When was CVE-2026-43823 disclosed?
CVE-2026-43823 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43823 actively exploited?
CVE-2026-43823 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.9% of all scored CVEs.
What is the CVSS score of CVE-2026-43823?
CVE-2026-43823 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-43823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43823, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43823

Explore →

Is Your Infrastructure Affected by CVE-2026-43823?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs