# CVE-2025-47270: nimiq-network-libp2p Uncontrolled Resource Consumption vulnerability


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 May 2025
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-3v6r-9cr8-q433

## What is CVE-2025-47270?

CVE-2025-47270 is a high-severity vulnerability in nimiq core-rs-albatross, published on 12 May 2025. 

### Official description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. The `nimiq-network-libp2p` subcrate of nimiq/core-rs-albatross is vulnerable to a Denial of Service (DoS) attack due to uncontrolled memory allocation. Specifically, the implementation of the `Discovery` network message handling allocates a buffer based on a length value provided by the peer, without enforcing an upper bound. Since this length is a `u32`, a peer can trigger allocations of up to 4 GB, potentially leading to memory exhaustion and node crashes. As Discovery messages are regularly exchanged for peer discovery, this vulnerability can be exploited repeatedly. The patch for this vulnerability is formally released as part of v1.1.0. The patch implements a limit to the discovery message size of 1 MB and also resizes the message buffer size incrementally as the data is read. No known workarounds are available.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-47270?


## How do I fix CVE-2025-47270?

No fix has been published for CVE-2025-47270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-47270 being exploited?

There is no known exploitation of CVE-2025-47270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47270 and fix it if it is affected.

What it is: CVE-2025-47270 is a high-severity vulnerability in nimiq core-rs-albatross, published on 12 May 2025. 
Exploitation: There is no known exploitation of CVE-2025-47270 in the wild and no public exploit code.

Affected product: nimiq core-rs-albatross. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47270/ (Markdown: https://insights.sbomify.com/CVE-2025-47270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47270
- OSV: https://osv.dev/vulnerability/CVE-2025-47270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47270/
Summaries are generated and may contain mistakes; the official description above is the record.