Loading story…
n8n published security advisories for multiple supported release branches after disclosure of several vulnerabilities, including a critical flaw tracked as CVE-2026-56348. The CVE affects versions before 2.20.0 and allows an authenticated user to abuse the POST /rest/dynamic-node-parameters/options endpoint to bypass Allowed HTTP Request Domains restrictions, causing the server to send credential-bearing HTTP requests to unauthorized hosts and potentially exfiltrate sensitive authentication data. The issue is remotely exploitable and impacts environments where users can access affected dynamic node functionality.
The broader advisory set also covers additional n8n weaknesses in releases prior to 2.28.1, 2.27.4, and 1.123.61, including another Allowed HTTP Request Domains bypass through the AI Agents MCP Connector, prototype pollution via workflow credentials that can lead to unauthenticated user and project enumeration, cross-issuer token exchange account binding caused by subject-only identity resolution, and a shared credential header leak through HTTP request pagination expressions. The Canadian Centre for Cyber Security urged administrators to review the advisories, upgrade to the patched versions, restrict access to exposed endpoints where possible, and monitor for unauthorized outbound requests that could indicate credential leakage.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
On June 27, 2026, a public oss-sec disclosure reported that n8n's GET /rest/workflows/from-url endpoint still allowed authenticated SSRF in default configurations, affecting versions up to 2.19.x and later versions when N8N_SSRF_PROTECTION_ENABLED was unset. The researcher said the protection was opt-in and defaulted to false, recommended enabling the flag and applying egress filtering, and noted no CVE or GHSA had been issued.
On June 24, 2026, n8n published security advisories covering multiple vulnerabilities across supported version branches. The affected releases were versions prior to 2.28.1, prior to 2.27.4, and prior to 1.123.61, including issues involving domain restriction bypass, prototype pollution, token exchange account binding, and credential header leakage.
CVE-2026-56348 was published as a critical vulnerability affecting n8n before version 2.20.0. The flaw in the POST /rest/dynamic-node-parameters/options endpoint allows authenticated users to bypass Allowed HTTP Request Domains restrictions and potentially exfiltrate credentials to unauthorized hosts.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
seclists.org
Open sourcecyber.gc.ca
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A critical server-side request forgery flaw in the **n8n** workflow automation platform, tracked as `CVE-2026-56348`, allowed any authenticated user to bypass the product’s Allowed HTTP Request Domains restriction and coerce the server into sending stored credentials to attacker-controlled hosts. The issue affected all versions before `2.20.0` and stemmed from missing credential permission validation in the `refineResourceIds()` path behind the `POST /rest/dynamic-node-parameters/options` endpoint, enabling exposure of API keys, OAuth tokens, and passwords without confirming `credential:read` access. n8n fixed the vulnerability by adding credential access checks through `CredentialsFinderService` and returning a `ForbiddenError` when validation fails, while no public proof-of-concept had been reported at disclosure. Separately, the Canadian Centre for Cyber Security issued an advisory urging organizations to review n8n’s latest vendor notices and apply updates affecting versions prior to `1.123.64`, `2.29.8`, and `2.30.1`, underscoring continued patching requirements across multiple release branches.
Jul 12, 2026
Government cyber agencies in Belgium and Canada warned that **n8n** released security updates to address multiple **critical vulnerabilities** that could allow attackers to compromise workflow automation instances, particularly those exposed to the internet. The advisories emphasize that n8n often orchestrates actions across interconnected systems, increasing blast radius if compromised, and urge administrators to **patch immediately** to protect confidentiality, integrity, and availability. The Belgian CCB advisory highlights three critical CVEs—**CVE-2026-27495**, **CVE-2026-27577**, and **CVE-2026-27497** (each scored **CVSS 9.4**) affecting n8n versions prior to **2.10.1 / 2.9.3 / 1.123.22**, including issues mapped to **CWE-94 (code injection)** and **CWE-89 (SQL injection)**. It describes **sandbox escape leading to arbitrary code execution** in the JavaScript Task Runner (notably impacting the default internal Task Runner mode) and abuse of crafted workflow expressions by authenticated users with workflow modification permissions; Canada’s Cyber Centre advisory (AV26-176) additionally enumerates impacted components and attack classes including **RCE via Merge Node**, **expression sandbox escape to RCE**, **JavaScript Task Runner sandbox escape**, **unauthenticated expression evaluation via Form Node**, and **stored XSS across multiple nodes**, directing organizations to apply n8n’s upstream fixes.
Jul 4, 2026
German security advisories from dCERT reported **multiple vulnerabilities** affecting **n8n**, the workflow automation and orchestration platform. The notices identify separate advisories, `2026-0860` and `2026-1228`, indicating that more than one set of security issues has been documented for the product. The available advisory metadata does not include technical synopses, affected versions, or mitigation details, but the repeated disclosures signal an ongoing security concern for organizations using n8n. Security teams should review the referenced dCERT advisories, determine whether deployed n8n instances are affected, and prioritize vendor patches or other recommended mitigations as details become available.
Jun 29, 2026