# CVE-2025-49595: n8n Vulnerable to Denial of Service via Malformed Binary Data Requests

> Authenticated attackers can cause service unavailability in n8n by sending malformed filesystem URI requests to the binary data endpoint.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jul 2025
- **Updated:** 3 Jul 2025
- **Also known as:** GHSA-pr9r-gxgp-9rm8

## What is CVE-2025-49595?

CVE-2025-49595 is a medium-severity denial of service vulnerability in N8n N8n, published on 3 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

n8n is a workflow automation platform. Prior to version 1.99.0, there is a denial of Service vulnerability in /rest/binary-data endpoint when processing empty filesystem URIs (filesystem:// or filesystem-v2://). This allows authenticated attackers to cause service unavailability through malformed filesystem URI requests, effecting the /rest/binary-data endpoint and n8n.cloud instances (confirmed HTTP/2 524 timeout responses). Attackers can exploit this by sending GET requests with empty filesystem URIs (filesystem:// or filesystem-v2://) to the /rest/binary-data endpoint, causing resource exhaustion and service disruption. This issue has been patched in version 1.99.0.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including n8n. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n` | npm | All versions | 1.99.0 |
| `n8n` | npm | All versions | 1.99.0 |

Products: N8n N8n.

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

Upgrade n8n to 1.99.0 or later.

## Is CVE-2025-49595 being exploited?

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

## Other vulnerabilities in N8n N8n

- [CVE-2025-68613](https://insights.sbomify.com/CVE-2025-68613/): n8n Improper Control of Dynamically-Managed Code Resources (critical 10.0, exploited in the wild)
- [CVE-2026-21877](https://insights.sbomify.com/CVE-2026-21877/): n8n is vulnerable to Remote Code Execution via Arbitrary File Write (critical 10.0)
- [CVE-2026-21858](https://insights.sbomify.com/CVE-2026-21858/): n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling (critical 10.0)
- [CVE-2026-1470](https://insights.sbomify.com/CVE-2026-1470/): n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution (critical 9.9)
- [CVE-2025-68668](https://insights.sbomify.com/CVE-2025-68668/): n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49595 is a medium-severity denial of service vulnerability in N8n N8n, published on 3 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-49595 in the wild and no public exploit code.

Affected packages and fixed versions:
- n8n (npm): affected all versions; fixed in 1.99.0
- n8n (npm): affected all versions; fixed in 1.99.0

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-49595/ (Markdown: https://insights.sbomify.com/CVE-2025-49595/index.md)
```

## Sources

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

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