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 82% 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 — 3 sources updated 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
18%
KEV
Not listed

Published

July 23, 2026

Last Modified

September 4, 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

Vendor Advisories for CVE-2026-43823(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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.

Data Freshness Timeline

(refreshed 21× in last 7d / 87× 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.

Showing the most recent 100 of 195 total refreshes for this CVE.

  1. 2026-09-18 22:33 UTCEG score recompute
  2. 2026-09-18 22:33 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:06 UTCEG score recompute
  5. 2026-09-18 03:06 UTCVendor advisory
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-17 02:02 UTCEG score recompute
  8. 2026-09-17 02:02 UTCVendor advisory
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 06:47 UTCEG score recompute
  11. 2026-09-16 06:47 UTCVendor advisory
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-14 16:15 UTCVendor advisory
  14. 2026-09-14 04:19 UTCEG score recompute
  15. 2026-09-14 04:19 UTCVendor advisory
  16. 2026-09-13 16:47 UTCEPSS rescore
  17. 2026-09-13 16:33 UTCVendor advisory
  18. 2026-09-13 04:47 UTCVendor advisory
  19. 2026-09-12 17:00 UTCEG score recompute
  20. 2026-09-12 17:00 UTCVendor advisory
  21. 2026-09-12 15:01 UTCEPSS rescore
  22. 2026-09-12 05:12 UTCVendor advisory
  23. 2026-09-11 16:45 UTCEG score recompute
  24. 2026-09-11 16:45 UTCVendor advisory
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:37 UTCEPSS rescore
  2. 2026-09-11 03:09 UTCVendor advisory
  3. 2026-09-10 15:10 UTCEG score recompute
  4. 2026-09-10 15:10 UTCVendor advisory
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-09 08:56 UTCEG score recompute
  7. 2026-09-09 08:56 UTCVendor advisory
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 21:30 UTCEG score recompute
  10. 2026-09-07 21:30 UTCVendor advisory
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 08:31 UTCVendor advisory
  14. 2026-09-05 19:28 UTCEG score recompute
  15. 2026-09-05 19:28 UTCVendor advisory
  16. 2026-09-05 06:59 UTCVendor advisory
  17. 2026-09-04 18:42 UTCEG score recompute
  18. 2026-09-04 18:42 UTCVendor advisory
  19. 2026-09-04 13:16 UTCEG score recompute
  20. 2026-09-04 13:16 UTCVendor advisory
  21. 2026-09-04 05:06 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 23:22 UTCEG score recompute
  24. 2026-09-01 23:22 UTCVendor advisory
  25. 2026-09-01 13:54 UTCEPSS rescore
  26. 2026-08-31 00:17 UTCEG score recompute
  27. 2026-08-31 00:17 UTCVendor advisory
  28. 2026-08-30 19:17 UTCEPSS rescore
  29. 2026-08-30 12:31 UTCEG score recompute
  30. 2026-08-30 12:31 UTCVendor advisory
  31. 2026-08-30 01:22 UTCEPSS rescore
  32. 2026-08-30 00:33 UTCEG score recompute
  33. 2026-08-30 00:33 UTCVendor advisory
  34. 2026-08-28 21:41 UTCEPSS rescore
  35. 2026-08-27 21:56 UTCEG score recompute
  36. 2026-08-27 21:56 UTCVendor advisory
  37. 2026-08-27 14:25 UTCEPSS rescore
  38. 2026-08-27 10:10 UTCVendor advisory
  39. 2026-08-26 19:55 UTCEG score recompute
  40. 2026-08-26 19:55 UTCVendor advisory
  41. 2026-08-26 14:46 UTCEPSS rescore
  42. 2026-08-26 05:40 UTCVendor advisory
  43. 2026-08-25 17:50 UTCEG score recompute
  44. 2026-08-25 17:50 UTCVendor advisory
  45. 2026-08-25 13:49 UTCEPSS rescore
  46. 2026-08-25 06:04 UTCVendor advisory
  47. 2026-08-24 18:17 UTCEG score recompute
  48. 2026-08-24 18:17 UTCVendor advisory
  49. 2026-08-24 06:30 UTCVendor advisory
  50. 2026-08-23 18:44 UTCVendor advisory
  51. 2026-08-23 06:58 UTCEG score recompute
  52. 2026-08-23 06:58 UTCVendor advisory
  53. 2026-08-23 00:19 UTCEPSS rescore
  54. 2026-08-22 19:11 UTCVendor advisory
  55. 2026-08-22 07:25 UTCEG score recompute
  56. 2026-08-22 07:25 UTCVendor advisory
  57. 2026-08-21 23:49 UTCEPSS rescore
  58. 2026-08-21 19:39 UTCVendor advisory
  59. 2026-08-21 07:53 UTCEG score recompute
  60. 2026-08-21 07:53 UTCVendor advisory
  61. 2026-08-20 22:55 UTCEPSS rescore
  62. 2026-08-20 20:06 UTCVendor advisory
  63. 2026-08-20 08:20 UTCVendor advisory
  64. 2026-08-19 20:33 UTCEG score recompute
  65. 2026-08-19 20:33 UTCVendor advisory
  66. 2026-08-19 17:04 UTCEPSS rescore
  67. 2026-08-19 08:25 UTCVendor advisory
  68. 2026-08-18 20:39 UTCEG score recompute
  69. 2026-08-18 20:39 UTCVendor advisory
  70. 2026-08-18 13:48 UTCEPSS rescore
  71. 2026-08-18 08:51 UTCVendor advisory
  72. 2026-08-17 20:24 UTCEG score recompute
  73. 2026-08-17 20:24 UTCVendor advisory
  74. 2026-08-17 13:47 UTCEPSS rescore
  75. 2026-08-17 07:13 UTCVendor advisory

Related CVEs(same vendor + same CWE)

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, with the most recent update on September 4, 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.5% 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