VulnerabilityPublished 4 Feb 2026

CVE-2025-61917: n8n · Resource Exposure

Affects n8nSource CVE Database V5

Not known to be exploited · CVSS 7.7 High : upgrade to 1.114.3 soon.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.114.3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade n8n to 1.114.3.

Affected software

Product	Affected	Fixed in
n8n-ion8n	Affected >=1.65.0 <1.114.3	Fixed in 1.114.3
GitHubn8n-io/n8n`pkg:github/n8n-io/n8n`Other threats	Affected =1.65.0 =1.114.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade all n8n instances to version 1.114.3 or later immediately to apply the patch that replaces unsafe buffer allocation with safe, zero-initialized buffers.
Conduct a thorough audit of workflows and tasks to identify any that handle sensitive data, ensuring that secrets and tokens are stored and transmitted securely using n8n's credential management features.
Restrict access to the n8n environment to trusted users and networks, minimizing the risk of low-privilege attackers exploiting the vulnerability.
Implement runtime monitoring and logging to detect unusual access patterns or data exfiltration attempts related to workflow executions.
If upgrading immediately is not possible, consider isolating n8n instances in segmented network zones and applying strict access controls to reduce exposure.
Review and update incident response plans to include scenarios involving potential data leakage from workflow automation platforms.
Educate developers and administrators about secure coding and configuration practices within n8n to prevent introduction of similar vulnerabilities.

Description

CVE-2025-61917 is a high-severity vulnerability in the n8n workflow automation platform versions 1.65.0 through before 1.114.3. It arises from the unsafe use of Buffer.allocUnsafe() and Buffer.allocUnsafeSlow() in the task runner, which can lead to allocation of uninitialized memory buffers. These buffers may contain residual sensitive data such as secrets, tokens, or data from prior tasks within the same Node.js process, resulting in potential information disclosure.

Impact

For European organizations, this vulnerability poses a significant risk of sensitive data leakage from automated workflows managed by n8n. Since n8n is used to orchestrate business-critical processes, exposure of secrets, tokens, or confidential data could lead to unauthorized access to internal systems, data breaches, or compliance violations under regulations such as GDPR. The confidentiality impact is high, as attackers with low privileges can access residual memory contents without needing user interaction. While integrity and availability are not directly affected, the leakage of sensitive information can facilitate further attacks or espionage. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, are particularly vulnerable. The risk is amplified if n8n is exposed to external networks or integrated with cloud services. Failure to patch promptly could result in exploitation by threat actors seeking to harvest credentials or sensitive workflow data.

CWE-668Exposure of Resource to Wrong Sphere (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Feb 2026, 07:38 UTC

WeaknessesCWE-668, CWE-200

Technical details

References

Community reviews

Related threats