go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p versions 0.27.8, 0.28.2, and 0.29.1 restrict RSA keys to <= 8192 bits. To protect one's application, it is necessary to update to these patch releases and to use the updated Go compiler in 1.20.7 or 1.19.12. There are no known workarounds for this issue.
CVE-2023-39533
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.3%, top 31% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 2%
- EPSS %ILE
- 73%
- KEV
- Not listed
Published
August 8, 2023
Last Modified
September 1, 2026
Advisory Details (9)
Auto-updated Sep 1, 2026NRDAX-T0205 - Pre-Handshake Crypto CPU Burn · NRDAX
https://nrdax.com/techniques/NRDAX-T0205-pre-handshake-crypto-cpu-burncommit e30fcf7dfd47 (libp2p/go-libp2p)
Fix landed in libp2p/go-libp2p commit e30fcf7dfd47 — awaiting tagged release
https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92dcommit 445be526aea4 (libp2p/go-libp2p)
Fix landed in libp2p/go-libp2p commit 445be526aea4 — awaiting tagged release
https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00commit 0cce607219f3 (libp2p/go-libp2p)
Fix landed in libp2p/go-libp2p commit 0cce607219f3 — awaiting tagged release
https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbbcommit 2350afd2e8ab (golang/go)
Fix landed in golang/go commit 2350afd2e8ab — awaiting tagged release
https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017update qtls to restrict RSA keys in certificates to <= 8192 bits
Patch available: quic-go/quic-go v0.42.0 (PR #4012 merged 2023-08-03)
https://github.com/quic-go/quic-go/pull/4012core/crypto: restrict RSA keys to <= 8192 bits
Patch available: libp2p/go-libp2p v0.35.3 (PR #2454 merged 2023-08-03)
https://github.com/libp2p/go-libp2p/pull/2454crypto/tls: verifying certificate chains containing large RSA keys is slow [CVE-2023-29409] · Issue #61460 · golang/go · GitHub
https://github.com/golang/go/issues/61460libp2p nodes vulnerable to attack using large RSA keys · Advisory · libp2p/go-libp2p · GitHub
https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjggVendor Advisories for CVE-2023-39533(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/libp2p/go-libp2p | 0.29.0 | 0.29.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
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 6× in last 7d / 30× 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 178 total refreshes for this CVE.
- 2026-09-18 19:25 UTCEPSS rescore
- 2026-09-17 19:25 UTCEPSS rescore
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 05:11 UTCEPSS rescore
- 2026-09-13 16:44 UTCEPSS rescore
- 2026-09-12 14:58 UTCEPSS rescore
- 2026-09-11 14:50 UTCEPSS rescore
- 2026-09-11 09:34 UTCEPSS rescore
- 2026-09-08 21:58 UTCEPSS rescore
- 2026-09-07 15:59 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:26 UTCEPSS rescore
- 2026-09-04 13:58 UTCEPSS rescore
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-01 22:20 UTCVendor advisory
- 2026-09-01 21:43 UTCEG score recompute
- 2026-09-01 21:43 UTCVendor advisory
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-08-30 19:15 UTCEPSS rescore
- 2026-08-30 01:20 UTCEPSS rescore
- 2026-08-28 21:39 UTCEPSS rescore
- 2026-08-27 14:23 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-26 14:44 UTCEPSS rescore
- 2026-08-26 14:43 UTCEPSS rescore
- 2026-08-25 13:46 UTCEPSS rescore
- 2026-08-23 00:17 UTCEPSS rescore
- 2026-08-21 23:47 UTCEPSS rescore
- 2026-08-20 22:53 UTCEPSS rescore
- 2026-08-19 17:02 UTCEPSS rescore
- 2026-08-19 17:02 UTCEPSS rescore
- 2026-08-18 13:46 UTCEPSS rescore
- 2026-08-17 13:45 UTCEPSS rescore
- 2026-08-17 10:55 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescore
- 2026-08-16 02:12 UTCEPSS rescore
- 2026-08-15 01:28 UTCEPSS rescore
- 2026-08-15 01:28 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-12 13:48 UTCEPSS rescore
- 2026-08-11 13:39 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-08 16:35 UTCEPSS rescore
- 2026-08-07 16:25 UTCEPSS rescore
- 2026-08-06 13:45 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:07 UTCEPSS rescore
- 2026-08-03 10:34 UTCEPSS rescore
- 2026-08-03 10:34 UTCEPSS rescore
- 2026-08-02 05:28 UTCOSV refresh
- 2026-08-02 02:25 UTCEPSS rescore
- 2026-08-02 02:25 UTCEPSS rescore
- 2026-08-01 04:14 UTCEPSS rescore
- 2026-08-01 04:13 UTCEPSS rescore
- 2026-07-30 16:26 UTCEPSS rescore
- 2026-07-30 16:26 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-28 15:34 UTCEPSS rescore
- 2026-07-28 15:34 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-25 14:16 UTCEPSS rescore
- 2026-07-24 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:25 UTCEG score recompute
- 2026-07-22 23:12 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-20 17:06 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 13:19 UTCOSV refresh
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-09 19:08 UTCEPSS rescore
- 2026-07-08 15:13 UTCEPSS rescore
- 2026-07-07 13:44 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-05 02:29 UTCEPSS rescore
Frequently asked(5)
What is CVE-2023-39533?
When was CVE-2023-39533 disclosed?
Is CVE-2023-39533 actively exploited?
What is the CVSS score of CVE-2023-39533?
How do I remediate CVE-2023-39533?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-39533
Is Your Infrastructure Affected by CVE-2023-39533?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.