CVE-2026-65014: n8n before 2.28.0 Authentication Bypass via test-webhook

Published Jul 22, 2026
·
Updated

Impact The DELETE /${restEndpoint}/test-webhook/:id route is registered before the authentication middleware is applied, allowing any unauthenticated network caller who knows a workflow ID to cancel that workflow's active test webhook registration.

The impact is limited to disrupting in-progress test sessions. Production webhooks, persistent workflow state, and stored data are not affected.

Patches Users should upgrade to the patched version once available to remediate the vulnerability.

Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict network access to the n8n instance to fully trusted users only. - Place the n8n instance behind a reverse proxy or firewall that requires authentication before reaching the REST API.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Other sources

n8n before 2.28.0 (and before 2.27.4 on the 2.27.x branch) registers the DELETE /${restEndpoint}/test-webhook/:id endpoint before authentication middleware is applied, allowing any unauthenticated network caller who knows a workflow ID to cancel that workflow's active test webhook registration. The impact is limited to disrupting in-progress test sessions; production webhooks, persistent workflow state, and stored data are not affected.

MITRE

Affected Software

4 affected componentsFixes available
n8n n8n<2.28.0, <2.27.4
npm/n8n<2.27.4
2.27.4
n8n N8n Node.js>=2.27.0<2.27.4
n8n N8n Node.js>=2.27.0<2.27.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.27.4
  2. Compensating control

    Place the n8n instance behind a reverse proxy or firewall that requires authentication before reaching the REST API.

  3. Compensating control

    Restrict network access to the n8n instance to fully trusted users only (limit who can reach the REST API endpoints).

Event History

Jul 22, 2026
CVE Published
via MITRE·11:21 AM
Data Sourced
via MITRE·11:21 AM
DescriptionWeakness
Data Sourced
via NVD·12:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:18 PM
Affected Software
Advisory Published
via GitHub·10:36 PM
Data Sourced
via GitHub·10:36 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-65014?

CVE-2026-65014 has a medium severity rating of 6.3 on the CVSS scale.

2

What type of vulnerability is CVE-2026-65014?

CVE-2026-65014 is an authentication bypass vulnerability that allows unauthorized access to certain functions.

3

How do I fix CVE-2026-65014?

To fix CVE-2026-65014, upgrade to n8n version 2.28.0 or later, where the authentication middleware issue has been resolved.

4

What is the impact of CVE-2026-65014?

The impact of CVE-2026-65014 allows any unauthenticated user to cancel an active test webhook if they know the corresponding workflow ID.

5

Who is affected by CVE-2026-65014?

CVE-2026-65014 affects all versions of n8n prior to 2.28.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203