AI Threat Alert

CVE-2026-103245

MEDIUM
Published October 1, 2026

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 fail to verify the x-webflow-signature HMAC in the Webflow Trigger node webhook handler. Unauthenticated attackers can send forged webhook requests with attacker-controlled payloads to trigger workflows and...

Full CISO analysis pending enrichment.

How severe is it?

CVSS 3.1
5.3 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
N/A

What is the attack surface?

AV AC PR UI S C I A
AV Network
AC Low
PR None
UI None
S Unchanged
C None
I Low
A None

What should I do?

No patch available

Monitor for updates. Consider compensating controls or temporary mitigations.

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-103245?

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 fail to verify the x-webflow-signature HMAC in the Webflow Trigger node webhook handler. Unauthenticated attackers can send forged webhook requests with attacker-controlled payloads to trigger workflows and manipulate downstream actions like record creation or API calls.

Is CVE-2026-103245 actively exploited?

No confirmed active exploitation of CVE-2026-103245 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-103245?

No patch is currently available. Monitor vendor advisories for updates.

What is the CVSS score for CVE-2026-103245?

CVE-2026-103245 has a CVSS v3.1 base score of 5.3 (MEDIUM).

What are the technical details?

Original Advisory

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 fail to verify the x-webflow-signature HMAC in the Webflow Trigger node webhook handler. Unauthenticated attackers can send forged webhook requests with attacker-controlled payloads to trigger workflows and manipulate downstream actions like record creation or API calls.

Weaknesses (CWE)

CWE-347 Improper Verification of Cryptographic Signature Primary CWE-347 Improper Verification of Cryptographic Signature

CWE-347 — Improper Verification of Cryptographic Signature: The product does not verify, or incorrectly verifies, the cryptographic signature for data.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

Timeline

Published
October 1, 2026
Last Modified
October 1, 2026
First Seen
October 1, 2026
Back to Threat Feed