Advisory record · GHSA-gcq9-qqwx-rgj3

Out-of-memory vulnerability in github.com/libp2p/go-libp2p

CVSS 7.5 HighEPSS 0.0095 · 62nd percentile

Published by the GitHub Advisory Database at 13 Sept 2023, 16:37 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.40.27.4
Identifiers
GHSA-gcq9-qqwx-rgj3 · CVE-2023-40583 · GO-2023-2024
Weakness (CWE)
CWE-400
Published
13 Sept 2023
Updated
20 May 2024

Machine-written summary

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

The github.com/libp2p/go-libp2p package before 0.27.4 is vulnerable to memory exhaustion. A remote attacker can send a node messages containing signed peer records from randomly generated peers, causing the node to retain arbitrary amounts of data that is never garbage collected, which can lead to an out-of-memory condition. Upgrade to go-libp2p version 0.27.4 or later.

Written 10 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.0095, the 62nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 13 Sept 2023. New records show when each source confirmed them.

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.