CVE-2025-49595: n8n Vulnerable to Denial of Service via Malformed Binary Data Requests
CVE-2025-49595 is a denial of service in n8n, the workflow automation tool. An authenticated user can send GET requests with an empty filesystem URI to the /rest/binary-data endpoint and exhaust resources. Versions before 1.99.0 are affected; upgrade to 1.99.0.
Published Jul 3, 2025 · Analysis Nov 1, 2026
What an attacker can do
The /rest/binary-data endpoint serves binary data by an ID that begins with a storage prefix. The advisory says empty filesystem URIs, filesystem:// and filesystem-v2://, were accepted. The pull request describes the effect: malformed IDs were not rejected and caused expensive metadata lookups on the binary data root directory. The change is in packages/cli/src/controllers/binary-data.controller.ts. The fix adds strict checking of URI patterns.
The attacker must be authenticated (the CVSS 3.1 vector has PR:H, high privileges), so this is not an anonymous internet attack. The advisory confirms the effect on n8n.cloud, which returned HTTP/2 524 timeout responses. For a self-hosted team, the risk is an account with access, a stolen session or an insider holding the instance down with repeated requests. Impact is availability only; no data is exposed. Because n8n often orchestrates AI agents and business automations, its downtime stops those workflows too.
Who is affected
The npm package n8n before 1.99.0, self-hosted or cloud. Check your version:
npm ls n8nFor Docker installs, run n8n --version inside the container, or read the version in the UI's about dialog.
n8n
- Ecosystem
- npm
- Affected
- < 1.99.0
- Fixed in
- 1.99.0
- Check
npm ls n8n
How to fix it
Upgrade to n8n 1.99.0 or later:
npm install -g [email protected]Docker users should pull a tag at or above 1.99.0. The advisory gives no workaround. Until you upgrade, limit who holds accounts on the instance and restrict network access to it.
How to tell if you were hit
Review the reverse proxy or access logs for GET requests to /rest/binary-data whose query string carries an ID of filesystem:// or filesystem-v2:// with nothing after it. Look for bursts of these from a single account, followed by slow responses, 524 or 5xx errors, and high CPU or disk activity on the n8n host.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Denial of Service vulnerability in /rest/binary-data endpoint when processing empty filesystem URIs (filesystem:// or filesystem-v2://).
Impact
This is a Denial of Service (DoS) vulnerability that allows authenticated attackers to cause service unavailability through malformed filesystem URI requests. The vulnerability affects:
- The
/rest/binary-dataendpoint - 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.
Patches
The issue has been patched in 1.99.0. All users should upgrade to this version or later.
The fix introduces strict checking of URI patterns.
Patch commit: https://github.com/n8n-io/n8n/pull/16229
Credited to pfelilpe, LucianoSorrentino95, agustedone, ivov, ffaggiani.
Questions
- Which n8n version fixes CVE-2025-49595?
1.99.0. All users should upgrade to that version or later.
- Can an anonymous visitor exploit it?
No. The advisory describes authenticated attackers, and the CVSS 3.1 vector requires high privileges.
- Does it expose workflow data or credentials?
No. The impact is on availability only, through resource exhaustion on the /rest/binary-data endpoint.
- Is n8n Cloud affected?
The advisory says it confirmed HTTP/2 524 timeout responses on n8n.cloud instances.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More n8n vulnerabilities
All n8n entriesCVE-2026-86073
n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution
medium5.9Sep 10, 2026CVE-2026-86074
n8n: Instance AI Credential Setup Accepts Unvalidated Probe URL from Fetched Content
medium5.9Sep 10, 2026CVE-2026-86075
n8n: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint
high8.7Sep 10, 2026CVE-2026-86076
n8n: Expression Sandbox Escape via Class-Field Sanitizer Rebinding Can Lead to Code Execution
high8.7Sep 10, 2026CVE-2026-86077
n8n: Anonymous Approval-Gate Bypass via Reused resumeToken over the Chat WebSocket
medium6.3Sep 10, 2026CVE-2026-86078
n8n: Prototype Pollution via Workflow Structure Summary Can Lead to Denial of Service
medium6.0Sep 10, 2026
