🚨 CVE-2026-77071
n8n before 1.123.69, 2.33.4, and 2.34.1 contains a PostgREST filter injection vulnerability in the Supabase node's Row Get Many, Delete, and Update operations, which built filter queries by concatenating an expression-bindable value without escaping. An attacker could inject a condition that widened the filter to match every row, turning an intended single-row operation into full-table disclosure, deletion, or modification.
🎖@cveNotify
n8n before 1.123.69, 2.33.4, and 2.34.1 contains a PostgREST filter injection vulnerability in the Supabase node's Row Get Many, Delete, and Update operations, which built filter queries by concatenating an expression-bindable value without escaping. An attacker could inject a condition that widened the filter to match every row, turning an intended single-row operation into full-table disclosure, deletion, or modification.
🎖@cveNotify
GitHub
Supabase Node PostgREST Filter Injection in Row Get Many, Delete, and Update Operations
## Impact
The Supabase node's Row Get Many, Delete, and Update operations built PostgREST filter queries by concatenating an expression-bindable value with no escaping. An attacker could injec...
The Supabase node's Row Get Many, Delete, and Update operations built PostgREST filter queries by concatenating an expression-bindable value with no escaping. An attacker could injec...
🚨 CVE-2026-77072
n8n before 1.123.69, 2.33.4, and 2.34.1 contains a stored cross-site scripting vulnerability in the Form node's completion page. The completion page applied its sandboxing Content-Security-Policy only when respondWith was not set to 'redirect', but responseText was always rendered as raw HTML. An authenticated member could set respondWith to 'redirect' via an expression while keeping responseText populated, causing the completion page to serve unsanitized HTML and script from the n8n origin. Any visitor who submitted the resulting public form would have that script execute same-origin with their session.
🎖@cveNotify
n8n before 1.123.69, 2.33.4, and 2.34.1 contains a stored cross-site scripting vulnerability in the Form node's completion page. The completion page applied its sandboxing Content-Security-Policy only when respondWith was not set to 'redirect', but responseText was always rendered as raw HTML. An authenticated member could set respondWith to 'redirect' via an expression while keeping responseText populated, causing the completion page to serve unsanitized HTML and script from the n8n origin. Any visitor who submitted the resulting public form would have that script execute same-origin with their session.
🎖@cveNotify
GitHub
Form Node Completion Page Sandbox CSP Bypass Leads to Stored XSS
## Impact
The Form node's completion page applied its sandboxing Content-Security-Policy only when `respondWith` was not `'redirect'`, but `responseText` was still rendered as raw HTML...
The Form node's completion page applied its sandboxing Content-Security-Policy only when `respondWith` was not `'redirect'`, but `responseText` was still rendered as raw HTML...
🚨 CVE-2026-77073
n8n versions before 2.34.1 contain a credential validation bypass in the MCP create_workflow_from_code tool when authentication type is set to an expression. Attackers with a valid MCP Bearer API key and knowledge of a target credential ID can persist unauthorized cross-project credential references on workflows in different projects.
🎖@cveNotify
n8n versions before 2.34.1 contain a credential validation bypass in the MCP create_workflow_from_code tool when authentication type is set to an expression. Attackers with a valid MCP Bearer API key and knowledge of a target credential ID can persist unauthorized cross-project credential references on workflows in different projects.
🎖@cveNotify
GitHub
MCP create_workflow_from_code Accepts Cross-Project Credentials When Auth Type Is an Expression
## Impact
The MCP `create_workflow_from_code` tool did not apply the same expression-awareness guard to credential validation that the runtime execution path uses. When a node's authentication...
The MCP `create_workflow_from_code` tool did not apply the same expression-awareness guard to credential validation that the runtime execution path uses. When a node's authentication...
🚨 CVE-2026-77074
n8n versions before 1.123.69 contain a server-side request forgery vulnerability in the Edit Image node's Draw Text operation that allows authenticated users to inject MVG primitives. Attackers can craft malicious text values to issue blind outbound HTTP requests to arbitrary addresses or access local files.
🎖@cveNotify
n8n versions before 1.123.69 contain a server-side request forgery vulnerability in the Edit Image node's Draw Text operation that allows authenticated users to inject MVG primitives. Attackers can craft malicious text values to issue blind outbound HTTP requests to arbitrary addresses or access local files.
🎖@cveNotify
GitHub
Edit Image Node Injection Enables Blind SSRF
## Impact
A crafted text value in the Edit Image node's Draw Text operation could terminate the intended text primitive and inject a new MVG primitive. An authenticated user able to run workfl...
A crafted text value in the Edit Image node's Draw Text operation could terminate the intended text primitive and inject a new MVG primitive. An authenticated user able to run workfl...
🚨 CVE-2026-77075
n8n before 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 contain an expression injection vulnerability in resource-locator field link preview rendering. The editor spliced the field's stored value directly into the node type's URL template without checking for expression syntax. An authenticated member can store a malicious value so that when another user opens the affected node in the editor, the injected expression is evaluated as JavaScript in the victim's authenticated session (cross-user script execution).
🎖@cveNotify
n8n before 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 contain an expression injection vulnerability in resource-locator field link preview rendering. The editor spliced the field's stored value directly into the node type's URL template without checking for expression syntax. An authenticated member can store a malicious value so that when another user opens the affected node in the editor, the injected expression is evaluated as JavaScript in the victim's authenticated session (cross-user script execution).
🎖@cveNotify
GitHub
Resource Locator Link Preview Expression Injection Allows Cross-User Script Execution
## Impact
When rendering a resource-locator field's link preview, the editor spliced the field's stored value directly into the node type's URL template without checking whether the st...
When rendering a resource-locator field's link preview, the editor spliced the field's stored value directly into the node type's URL template without checking whether the st...
🚨 CVE-2026-77076
n8n versions before 1.123.69, 2.33.4, and 2.34.1 contain an information disclosure vulnerability in the GraphQL node. When a GraphQL request fails at the connection level, the node re-throws the underlying HTTP client error unchanged instead of wrapping it in n8n's standard error type. That error contains the live request's headers, including a decrypted credential secret, which the execution engine persists verbatim. Any authenticated user able to read the resulting execution can retrieve the decrypted credential secret from the stored run data.
🎖@cveNotify
n8n versions before 1.123.69, 2.33.4, and 2.34.1 contain an information disclosure vulnerability in the GraphQL node. When a GraphQL request fails at the connection level, the node re-throws the underlying HTTP client error unchanged instead of wrapping it in n8n's standard error type. That error contains the live request's headers, including a decrypted credential secret, which the execution engine persists verbatim. Any authenticated user able to read the resulting execution can retrieve the decrypted credential secret from the stored run data.
🎖@cveNotify
GitHub
GraphQL Node Raw Error Re-throw Leaks Decrypted Credential Headers into Persisted Execution Data
## Impact
When a GraphQL node's request failed at the connection level, the node re-threw the underlying HTTP client error unchanged instead of wrapping it in n8n's standard error type. Th...
When a GraphQL node's request failed at the connection level, the node re-threw the underlying HTTP client error unchanged instead of wrapping it in n8n's standard error type. Th...
🚨 CVE-2026-77077
n8n versions before 1.123.69, 2.33.4, and 2.34.1 contain a JavaScript task runner VM sandbox escape. The runner's prototype-freezing routine covers globalThis functions but not internal module constructors such as EventEmitter, allowing an authenticated user with Code node access to exploit prototype pollution to execute arbitrary commands within the runner container. Because the polluted prototype is a process-wide object, the corruption persists across other tenants' Code node executions on the same shared runner. On v1.x instances without task runners enabled, Code node JavaScript runs directly in the main n8n process, where the impact could be higher.
🎖@cveNotify
n8n versions before 1.123.69, 2.33.4, and 2.34.1 contain a JavaScript task runner VM sandbox escape. The runner's prototype-freezing routine covers globalThis functions but not internal module constructors such as EventEmitter, allowing an authenticated user with Code node access to exploit prototype pollution to execute arbitrary commands within the runner container. Because the polluted prototype is a process-wide object, the corruption persists across other tenants' Code node executions on the same shared runner. On v1.x instances without task runners enabled, Code node JavaScript runs directly in the main n8n process, where the impact could be higher.
🎖@cveNotify
GitHub
JavaScript Task Runner VM Sandbox Escape via EventEmitter Prototype Pollution Leads to Remote Code Execution
## Impact
The JS task runner's prototype-freezing routine covered `globalThis` functions but not internal module constructors such as `EventEmitter`. An authenticated user with Code node acces...
The JS task runner's prototype-freezing routine covered `globalThis` functions but not internal module constructors such as `EventEmitter`. An authenticated user with Code node acces...
🚨 CVE-2026-77079
n8n before 2.34.1 and 2.33.4 contains an authorization bypass in the custom project role deletion (reassignment) path. When deleting a custom project role with a reassignment target, the code validated only that the target role existed and was project-scoped, performing no project-level authorization check. A user holding only the narrow role:manageProject global scope could delete any custom project role in use on the instance and reassign its holders (including themselves) to the built-in project:admin role, gaining full administrative control of projects they had no legitimate access to.
🎖@cveNotify
n8n before 2.34.1 and 2.33.4 contains an authorization bypass in the custom project role deletion (reassignment) path. When deleting a custom project role with a reassignment target, the code validated only that the target role existed and was project-scoped, performing no project-level authorization check. A user holding only the narrow role:manageProject global scope could delete any custom project role in use on the instance and reassign its holders (including themselves) to the built-in project:admin role, gaining full administrative control of projects they had no legitimate access to.
🎖@cveNotify
GitHub
Custom-role deletion's reassignment path bypasses project-scoped authorization
## Impact
Deleting a custom project role with a reassignment target validated only that the target role existed and was also project-scoped, it performed no project-level authorization check. A us...
Deleting a custom project role with a reassignment target validated only that the target role existed and was also project-scoped, it performed no project-level authorization check. A us...
🚨 CVE-2026-77081
n8n before 1.123.69, 2.x before 2.33.4, and 2.x before 2.34.1 contain an allowed-domains bypass in the GraphQL node. When the node's Authentication parameter is set to expression mode, every authentication-gated credential selector is treated as active; if two credentials of different types are attached, the node enforces the allowed-domains policy of only the first credential while still attaching material from both. An authenticated user with workflow-authoring rights can thereby send a domain-restricted credential to an attacker-controlled endpoint, exfiltrating it with the leaked credential's permissions.
🎖@cveNotify
n8n before 1.123.69, 2.x before 2.33.4, and 2.x before 2.34.1 contain an allowed-domains bypass in the GraphQL node. When the node's Authentication parameter is set to expression mode, every authentication-gated credential selector is treated as active; if two credentials of different types are attached, the node enforces the allowed-domains policy of only the first credential while still attaching material from both. An authenticated user with workflow-authoring rights can thereby send a domain-restricted credential to an attacker-controlled endpoint, exfiltrating it with the leaked credential's permissions.
🎖@cveNotify
GitHub
GraphQL Node Allowed-Domains Bypass Permits Restricted Credential Exfiltration
## Impact
The GraphQL node's `Authentication` parameter accepted expression values, which caused every authentication-gated credential selector to be treated as active. When two credentials of...
The GraphQL node's `Authentication` parameter accepted expression values, which caused every authentication-gated credential selector to be treated as active. When two credentials of...
🚨 CVE-2026-77082
n8n before 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 contains a regular expression denial of service (ReDoS) vulnerability in the Filter and Switch nodes, which compile user-supplied regex patterns with new RegExp() and execute them synchronously on the worker thread without complexity validation or execution timeout. A crafted regex pattern can block the worker for an extended period per data item processed, delaying other workflow executions on the same worker.
🎖@cveNotify
n8n before 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 contains a regular expression denial of service (ReDoS) vulnerability in the Filter and Switch nodes, which compile user-supplied regex patterns with new RegExp() and execute them synchronously on the worker thread without complexity validation or execution timeout. A crafted regex pattern can block the worker for an extended period per data item processed, delaying other workflow executions on the same worker.
🎖@cveNotify
GitHub
ReDoS in Filter and Switch Node Regex Matching Allows Worker Denial of Service
## Impact
The Filter and Switch nodes compiled user-supplied regex patterns with `new RegExp()` and executed them synchronously on the worker thread without any complexity validation or execution ...
The Filter and Switch nodes compiled user-supplied regex patterns with `new RegExp()` and executed them synchronously on the worker thread without any complexity validation or execution ...
🚨 CVE-2026-77083
n8n is a workflow automation platform. In versions prior to 1.123.69, 2.33.4, and 2.34.1, the JavaScript Code node's VM sandbox did not freeze the sandbox's Function.prototype, allowing an authenticated user with the ability to create and execute workflows to pollute it from within a Code node execution and recover a reference to the host's globalThis, resulting in a sandbox escape. The full exploit chain additionally depends on specific modules being available as allowlisted imports in the deployment's configuration. The issue is fixed in versions 1.123.69, 2.33.4, and 2.34.1.
🎖@cveNotify
n8n is a workflow automation platform. In versions prior to 1.123.69, 2.33.4, and 2.34.1, the JavaScript Code node's VM sandbox did not freeze the sandbox's Function.prototype, allowing an authenticated user with the ability to create and execute workflows to pollute it from within a Code node execution and recover a reference to the host's globalThis, resulting in a sandbox escape. The full exploit chain additionally depends on specific modules being available as allowlisted imports in the deployment's configuration. The issue is fixed in versions 1.123.69, 2.33.4, and 2.34.1.
🎖@cveNotify
GitHub
Sandbox Escape in JavaScript Code Node via Prototype Pollution
## Impact
The JavaScript Code node's VM sandbox did not freeze the sandbox `Function.prototype`, allowing an authenticated user to pollute it from within a Code node execution to recover a ref...
The JavaScript Code node's VM sandbox did not freeze the sandbox `Function.prototype`, allowing an authenticated user to pollute it from within a Code node execution to recover a ref...
🚨 CVE-2026-77084
n8n before 1.123.69 (and 2.x before 2.33.4 / 2.34.1) contains a code execution vulnerability in the Git node. The Git node executed certain repository-local git configuration values without neutralizing them, so any subsequent Git node operation against a repository containing a malicious value would execute it as the n8n process user. This is not reachable through the Git node's own configuration controls and requires a separate file-write vulnerability elsewhere to plant the malicious value.
🎖@cveNotify
n8n before 1.123.69 (and 2.x before 2.33.4 / 2.34.1) contains a code execution vulnerability in the Git node. The Git node executed certain repository-local git configuration values without neutralizing them, so any subsequent Git node operation against a repository containing a malicious value would execute it as the n8n process user. This is not reachable through the Git node's own configuration controls and requires a separate file-write vulnerability elsewhere to plant the malicious value.
🎖@cveNotify
GitHub
Code execution in the n8n Git node via unchecked repository-local git configuration
## Impact
The n8n Git node executed certain git configuration values from a repository's local configuration without neutralizing them. If such a value were present in a repository's confi...
The n8n Git node executed certain git configuration values from a repository's local configuration without neutralizing them. If such a value were present in a repository's confi...
🚨 CVE-2026-77085
n8n before 2.34.1 and 2.33.x before 2.33.4 contains an SSRF protection bypass in the SearXNG Agent tool. The tool sent requests to the user-supplied API URL using a raw HTTP client that did not route through n8n's centralized SSRF protection. On instances with N8N_SSRF_PROTECTION_ENABLED=true, an authenticated user with permission to create SearXNG credentials and configure a personal agent could set the API URL to an internal host, causing the n8n server to connect to that host and return the response content through the Agent chat output.
🎖@cveNotify
n8n before 2.34.1 and 2.33.x before 2.33.4 contains an SSRF protection bypass in the SearXNG Agent tool. The tool sent requests to the user-supplied API URL using a raw HTTP client that did not route through n8n's centralized SSRF protection. On instances with N8N_SSRF_PROTECTION_ENABLED=true, an authenticated user with permission to create SearXNG credentials and configure a personal agent could set the API URL to an internal host, causing the n8n server to connect to that host and return the response content through the Agent chat output.
🎖@cveNotify
GitHub
SSRF Protection Bypass via SearXNG Tool Allows Member Users to Read Internal Service Responses
## Impact
The SearXNG Agent tool sent requests to the user-supplied API URL using a raw HTTP client that did not route through n8n's centralized SSRF protection. On instances with `N8N_SSRF_PR...
The SearXNG Agent tool sent requests to the user-supplied API URL using a raw HTTP client that did not route through n8n's centralized SSRF protection. On instances with `N8N_SSRF_PR...
🚨 CVE-2026-53804
OTRS Community Edition contains an authenticated OS command injection vulnerability in the PGP encryption module that allows administrators to execute arbitrary operating-system commands by supplying crafted values for the PGP binary path and command options. Administrator-supplied configuration values are concatenated without sanitization into a shell command, enabling arbitrary command execution as the web server process user during normal ticket operations after the malicious configuration is deployed.
🎖@cveNotify
OTRS Community Edition contains an authenticated OS command injection vulnerability in the PGP encryption module that allows administrators to execute arbitrary operating-system commands by supplying crafted values for the PGP binary path and command options. Administrator-supplied configuration values are concatenated without sanitization into a shell command, enabling arbitrary command execution as the web server process user during normal ticket operations after the malicious configuration is deployed.
🎖@cveNotify
h00die-gr3y
CVE-2026-53804 — OTRS PGP Configuration Command Injection — h00die-gr3y
Authenticated OS command injection in OTRS Community Edition, Znuny and OTOBO through PGP executable and option settings that are interpolated into a Perl backtick command.
🚨 CVE-2026-68921
DiceBear is an avatar library for designers and developers. Prior to 9.4.3, @dicebear/core interpolates the rotate option into an SVG transform attribute without XML escaping in addRotate in packages/@dicebear/core/src/utils/svg.ts, while @dicebear/initials similarly emits fontSize and fontWeight without escaping in packages/@dicebear/initials/src/index.ts. Runtime callers can pass strings despite the numeric TypeScript types, break out of the attributes, and inject arbitrary SVG markup. Script can execute in the page origin when the generated avatar is inserted inline or served as image/svg+xml and opened directly, although exploitation requires an application to pass untrusted values into these normally developer-controlled options. This issue is fixed in @dicebear/core and @dicebear/initials version 9.4.3.
🎖@cveNotify
DiceBear is an avatar library for designers and developers. Prior to 9.4.3, @dicebear/core interpolates the rotate option into an SVG transform attribute without XML escaping in addRotate in packages/@dicebear/core/src/utils/svg.ts, while @dicebear/initials similarly emits fontSize and fontWeight without escaping in packages/@dicebear/initials/src/index.ts. Runtime callers can pass strings despite the numeric TypeScript types, break out of the attributes, and inject arbitrary SVG markup. Script can execute in the page origin when the generated avatar is inserted inline or served as image/svg+xml and opened directly, although exploitation requires an application to pass untrusted values into these normally developer-controlled options. This issue is fixed in @dicebear/core and @dicebear/initials version 9.4.3.
🎖@cveNotify
GitHub
Fix: Escape rotate, fontSize and fontWeight in SVG output · dicebear/dicebear@922946d
These option values are interpolated into SVG attributes but were not
escaped like the other attribute values.
escaped like the other attribute values.
🚨 CVE-2026-70654
libvips is a fast image processing library with low memory needs. Prior to version 8.18.3, applications that define unusual custom libvips sources and use them to process untrusted uncompressed PPM images can trigger a max/min error in vips_source_read_to_memory in libvips/iofuncs/source.c. The function uses VIPS_MAX instead of VIPS_MIN when selecting the remaining read size, allowing up to 4032 bytes to be written beyond the allocated heap buffer and causing memory corruption or a process crash. This issue is fixed in version 8.18.3.
🎖@cveNotify
libvips is a fast image processing library with low memory needs. Prior to version 8.18.3, applications that define unusual custom libvips sources and use them to process untrusted uncompressed PPM images can trigger a max/min error in vips_source_read_to_memory in libvips/iofuncs/source.c. The function uses VIPS_MAX instead of VIPS_MIN when selecting the remaining read size, allowing up to 4032 bytes to be written beyond the allocated heap buffer and causing memory corruption or a process crash. This issue is fixed in version 8.18.3.
🎖@cveNotify
GitHub
source: fix max/min confusion (#5038) · libvips/libvips@80e021c
Fix a copy-paste typo in vipssource.
Thanks Himanshu Anand
Thanks Himanshu Anand
🚨 CVE-2026-16936
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to a buffer overflow.
🎖@cveNotify
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to a buffer overflow.
🎖@cveNotify
Ibm
Security Bulletin: Vulnerabilities in IBM AIX and PowerVM VIOS
Updated Aug 21, 2026: Updated the summary to highlight the additional installation instructions. IBM is providing security updates for supported AIX and VIOS releases that are under active fix support. Delivered through Service Packs (SPs) and Fix Packs (FPs)…
🚨 CVE-2026-16946
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to a heap buffer overflow.
🎖@cveNotify
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to gain elevated privileges due to a heap buffer overflow.
🎖@cveNotify
Ibm
Security Bulletin: Vulnerabilities in IBM AIX and PowerVM VIOS
Updated Aug 21, 2026: Updated the summary to highlight the additional installation instructions. IBM is providing security updates for supported AIX and VIOS releases that are under active fix support. Delivered through Service Packs (SPs) and Fix Packs (FPs)…
🚨 CVE-2026-16972
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to obtain sensitive information due to improper authentication.
🎖@cveNotify
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to obtain sensitive information due to improper authentication.
🎖@cveNotify
Ibm
Security Bulletin: Vulnerabilities in IBM AIX and PowerVM VIOS
Updated Aug 21, 2026: Updated the summary to highlight the additional installation instructions. IBM is providing security updates for supported AIX and VIOS releases that are under active fix support. Delivered through Service Packs (SPs) and Fix Packs (FPs)…
🚨 CVE-2026-16996
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to an integer underflow.
🎖@cveNotify
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to execute arbitrary code due to an integer underflow.
🎖@cveNotify
Ibm
Security Bulletin: Vulnerabilities in IBM AIX and PowerVM VIOS
Updated Aug 21, 2026: Updated the summary to highlight the additional installation instructions. IBM is providing security updates for supported AIX and VIOS releases that are under active fix support. Delivered through Service Packs (SPs) and Fix Packs (FPs)…
🚨 CVE-2026-17118
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a use-after-free vulnerability.
🎖@cveNotify
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to a use-after-free vulnerability.
🎖@cveNotify
Ibm
Security Bulletin: Vulnerabilities in IBM AIX and PowerVM VIOS
Updated Aug 21, 2026: Updated the summary to highlight the additional installation instructions. IBM is providing security updates for supported AIX and VIOS releases that are under active fix support. Delivered through Service Packs (SPs) and Fix Packs (FPs)…