# CVE-2025-26819: Denial of service in Monero

> Attackers can cause denial of service against Monero nodes by exploiting missing response limits on HTTP server connections.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** DEBIAN-CVE-2025-26819, GHSA-w9f7-3m82-hj3j, UBUNTU-CVE-2025-26819

## What is CVE-2025-26819?

CVE-2025-26819 is a high-severity denial of service vulnerability in getmonero Monero, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Monero through 0.18.3.4 before ec74ff4 does not have response limits on HTTP server connections.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Getmonero Monero.

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

Apply the vendor's patch.

## Is CVE-2025-26819 being exploited?

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

## Other vulnerabilities in getmonero Monero

- [CVE-2018-3972](https://insights.sbomify.com/CVE-2018-3972/): Deserialization in Epee (critical 10.0)
- [CVE-2020-26947](https://insights.sbomify.com/CVE-2020-26947/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26819 is a high-severity denial of service vulnerability in getmonero Monero, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26819 in the wild and no public exploit code.

Affected product: getmonero Monero. 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-26819/ (Markdown: https://insights.sbomify.com/CVE-2025-26819/index.md)
```

## Sources

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

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