CVE-2025-68949

n8n: Webhook Node IP Whitelist Bypass via Partial String Matching

Workarounds

Users unable to upgrade immediately should avoid relying solely on IP whitelisting for webhook security. Recommended mitigations include:

• Adding authentication mechanisms such as shared secrets, HMAC signatures, or API keys.
• Avoiding short or prefix-based whitelist entries.
• Enforcing IP filtering at the network layer (for example, via reverse proxies or firewalls).

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.

CVE-2025-68949 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.0); upgrading removes the vulnerable code path.

Kodem intelligence

This issue has been patched in version 2.2.0.

Users are advised to upgrade to v2.2.0 or later, where IP whitelist validation uses strict IP comparison logic rather than partial string matching.

1. What is CVE-2025-68949? CVE-2025-68949 is a medium-severity security vulnerability in n8n (npm), affecting versions >= 1.36.0, < 2.2.0. It is fixed in 2.2.0.
2. How severe is CVE-2025-68949? CVE-2025-68949 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2025-68949? n8n (npm) versions >= 1.36.0, < 2.2.0 is affected.
4. Is there a fix for CVE-2025-68949? Yes. CVE-2025-68949 is fixed in 2.2.0. Upgrade to this version or later.
5. Is CVE-2025-68949 exploitable, and should I be worried? Whether CVE-2025-68949 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-68949 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-68949? Upgrade n8n to 2.2.0 or later.

Other vulnerabilities in n8n