# CVE-2025-68949: n8n has a Webhook Node IP Whitelist Bypass via Partial String Matching

> Attackers can bypass webhook IP whitelists in n8n due to partial string matching, allowing unauthorized access to restricted workflows.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-w96v-gf22-crwp

## What is CVE-2025-68949?

CVE-2025-68949 is a medium-severity authentication bypass vulnerability in N8n N8n, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

n8n is an open source workflow automation platform. From 1.36.0 to before 2.2.0, the Webhook node’s IP whitelist validation performed partial string matching instead of exact IP comparison. As a result, an incoming request could be accepted if the source IP address merely contained the configured whitelist entry as a substring. This issue affected instances where workflow editors relied on IP-based access controls to restrict webhook access. Both IPv4 and IPv6 addresses were impacted. An attacker with a non-whitelisted IP could bypass restrictions if their IP shared a partial prefix with a trusted address, undermining the intended security boundary. This vulnerability is fixed in 2.2.0.

Weakness: CWE-284 (Improper Access Control), CWE-134 (Use of Externally-Controlled Format String)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n` | npm | From 1.36.0 | 2.2.0 |
| `n8n` | npm | From 1.36.0 | 2.2.0 |

Products: N8n N8n.

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

Upgrade n8n to 2.2.0 or later.

## Is CVE-2025-68949 being exploited?

There is no known exploitation of CVE-2025-68949 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-68949 and fix it if it is affected.

What it is: CVE-2025-68949 is a medium-severity authentication bypass vulnerability in N8n N8n, published on 13 Jan 2026. 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-68949 in the wild and no public exploit code.

Affected packages and fixed versions:
- n8n (npm): affected from 1.36.0; fixed in 2.2.0
- n8n (npm): affected from 1.36.0; fixed in 2.2.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-68949/ (Markdown: https://insights.sbomify.com/CVE-2025-68949/index.md)
```

## Sources

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

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