n8n before 1.123.85, 2.43.5, and 2.44.1 Credential Guard Bypass via Execute Sub-workflow
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.123.85, 2.44.1, 2.43.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
n8n, an open-source workflow automation platform, is affected by a flaw that lets workflow editors bypass credential restrictions through the Execute Sub-workflow feature. A user with editor access to shared workflows could use this to gain access to restricted project credentials and see their decrypted secret values.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
n8n before 1.123.85, 2.43.5, and 2.44.1 contains a credential guard bypass vulnerability that allows editors of shared workflows to use restricted credentials by loading sub-workflows from URLs or local files. Attackers can configure the Execute Sub-workflow node with source url or localFile to serve content that resolves project credentials and returns their decrypted values.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- n8n-io n8n
fixed in 1.123.85
- n8n-io n8n
From 2.44.0 · fixed in 2.44.1
- n8n-io n8n
From 2.0.0 · fixed in 2.43.5