Advisory record · GHSA-876p-8259-xjgg

libp2p nodes vulnerable to attack using large RSA keys

CVSS 7.5 HighEPSS 0.015 · 75th percentile

Published by the GitHub Advisory Database at 9 Aug 2023, 13:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/libp2p/go-libp2pGo<0.27.8 || >=0.28.0, <0.28.2 || >=0.29.0, <0.29.10.27.8, 0.28.2, 0.29.1
Identifiers
GHSA-876p-8259-xjgg · CVE-2023-39533 · GO-2023-2000
Weakness (CWE)
CWE-770
Published
9 Aug 2023
Updated
1 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The go-libp2p package (github.com/libp2p/go-libp2p) is vulnerable before 0.27.8, from 0.28.0 before 0.28.2, and from 0.29.0 before 0.29.1. A remote peer can send large RSA keys during the Noise handshake or x509 extension verification, forcing the node to spend significant time on signature checks, which can exhaust resources. Upgrade to 0.27.8, 0.28.2, or 0.29.1, and also use Go 1.20.7 or 1.19.12 or later. No workarounds are listed.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.015, the 75th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:48 UTC First seen by agentprime
  2. 31 Oct 2026, 14:48 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.