n8n versions before 1.123.85, 2.43.5, and 2.44.1 have an authorization bypass vulnerability. This flaw allows authenticated users to access credentials they should not have permission to use by exploiting inline sub-workflow nodes with non-boolean disabled values. Attackers who know a credential ID can execute workflows in inline JSON mode, bypassing permission checks and potentially exfiltrating decrypted credentials to attacker-controlled servers.
A vulnerability in n8n versions before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 causes the SeaTable Trigger node's API token to be saved in error execution data. This occurs because failed poll requests store raw request headers, exposing the API token to users who can view workflow executions but do not have credential read access.
n8n versions before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 improperly store credential secrets in execution error data for certain nodes. This exposure occurs when operations fail in the Git, MongoDB Atlas Vector Store, and Google Cloud Storage nodes. Users with permission to view workflow executions but without credential read access can extract sensitive secrets such as Git passwords or tokens, MongoDB passwords, and Google access tokens from the error data.
n8n versions prior to 1.123.85, 2.43.5, and 2.44.1 contain an authorization bypass vulnerability. This flaw allows member users to access credentials they should not have permission to use by omitting default node parameters in workflows. Exploitation enables attackers to save and execute workflows that bypass pre-execution credential checks, resulting in decrypted credential values being sent to destinations controlled by the attacker.
A filter injection vulnerability exists in the Quick Base node of n8n versions before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1. This flaw allows attackers to supply untrusted input, such as webhook data, that is sent as raw query text to the Quick Base API. Exploitation can cause the 'Get Many' operation to return all records or the 'Delete' operation to remove all records accessible by the workflow credentials.
A regular expression denial of service (ReDoS) vulnerability exists in n8n versions before 1.123.85, 2.43.5, and 2.44.1. Authenticated users who can create and run workflows may exploit this by submitting specially crafted wildcard-heavy File(s) Selector patterns. This causes exponential backtracking in the regex engine, blocking the event loop and rendering the UI, API, webhooks, and health checks unresponsive until the service is restarted.
A vulnerability in n8n versions before 2.43.5 and 2.44.x before 2.44.1 allows authenticated members with workflow creation and execution permissions to exploit a client-supplied workflow ID. By using a crafted ID such as __proto__, the application improperly caches workflow owner projects, causing project checks to match all projects. This flaw enables unauthorized listing, reading, modification, and deletion of Data Table rows across all projects within the instance.
A credential guard bypass vulnerability exists in n8n versions before 1.123.85, 2.43.5, and 2.44.1. This flaw allows editors of shared workflows to exploit the Execute Sub-workflow node by loading sub-workflows from URLs or local files, thereby accessing restricted credentials and obtaining their decrypted values.
A denial of service vulnerability exists in github.com/go-jose/go-jose/v4 where parsing deeply nested JSON structures can cause the Go runtime to hit its stack limit and crash the application. This affects versions prior to 4.1.5 and up to 3.0.5. The issue is fixed in version 4.1.5. Applications parsing untrusted JSON with affected versions are exposed to crashes.
The systeminformation library version prior to 5.33.13 contains a prototype pollution vulnerability in the networkStats() function. This occurs when the interface name '__proto__' is passed, causing writes to Object.prototype and polluting all objects in the Node.js process. The vulnerability affects applications running on FreeBSD, OpenBSD, or NetBSD that pass untrusted input to networkStats(). The impact includes unexpected properties appearing on all objects, which can alter application logic and enumeration behavior. No remote code execution or attacker-controlled values are known. A fix is available in version 5.33.13.
Vue I18n versions before 11.4.14 and certain 12.0.0-alpha versions have a vulnerability where the escapeParameter feature does not properly escape named interpolation values when a translation call passes both a list and named values. This can lead to unescaped HTML markup being inserted, potentially enabling DOM-based XSS if untrusted named values are rendered as HTML. The issue is fixed in versions 11.4.14 and 12.0.0-alpha.5.
Vue I18n versions prior to 11.4.14 and certain alpha versions of 12.0.0 contain a vulnerability where the escapeParameter feature does not properly sanitize the srcdoc attribute in iframe elements within translation messages. This allows an attacker to inject HTML content that the browser decodes and executes in the same origin, leading to DOM-based cross-site scripting (XSS). The issue arises because the sanitizer escapes characters using character references that are decoded inside srcdoc, bypassing the sanitization. The vulnerability is fixed in versions 11.4.14 and 12.0.0-alpha.5.
LangGraph Python SDK v3 streaming client versions 0.4.0 through 0.4.5 improperly handle unencoded thread_id and assistant_id values in request paths, allowing relative path segments to redirect authenticated GET requests to other paths on the same server. This affects also langgraph versions 1.2.3 through 1.2.13 when used with vulnerable SDK versions. The vulnerability allows an attacker controlling these identifiers to cause the SDK to fetch and return data from arbitrary readable paths on the server, but does not allow modification of data. The issue is fixed in langgraph-sdk 0.4.6 and langgraph 1.2.14.
Echo versions prior to 5.4.0 and 4.16.0 contain an open redirect vulnerability due to improper sanitization of redirect URIs. The sanitizeURI function only inspects the first two bytes of the URI for separator characters, allowing a control character such as a tab to prefix the URI and bypass the check. Browsers strip such control characters and normalize backslashes to forward slashes, causing the Location header to redirect to an attacker-controlled domain. This vulnerability has been confirmed with a proof of concept and affects the RemoveTrailingSlash middleware when configured to redirect.
The decode-uri-component package prior to version 0.5.1 contains an uncontrolled resource consumption vulnerability. Its fallback decoding function can cause quadratic CPU usage when processing malformed inputs with many distinct percent-encoded sequences, leading to blocking of the Node.js event loop. This issue is resolved in version 0.5.1.
Echo, a Go web framework, had a vulnerability in versions prior to 4.16.0 and 5.4.0 where it trusted forwarded scheme headers from any client. This allowed an attacker to bypass HTTPSRedirect by claiming an HTTPS scheme over plaintext HTTP, or suppress the Strict-Transport-Security header when behind a TLS-terminating proxy. The issue is fixed in versions 4.16.0 and 5.4.0.
A vulnerability in the labstack echo Go web framework allows double decoding of the same URL path data in middleware.Static prior to versions 4.15.3 and 5.2.0. This double decoding can reconstruct double-encoded separators before filesystem resolution, potentially allowing access to files under guarded routes when the static middleware is registered globally. The issue is fixed in versions 4.15.3 and 5.2.0.
CVE-2026-118654 is a path traversal vulnerability in the Echo Go web framework's static file handlers prior to versions 4.16.0 and 5.4.0. The flaw allows an unauthenticated attacker to bypass route-level middleware protections by exploiting how dot segments are normalized after route matching, enabling unauthorized reading of protected files accessible via static filesystem mounts. This issue is a regression from an incomplete fix of a previous vulnerability (CVE-2026-55677) and is resolved in Echo versions 4.16.0 and 5.4.0.
### Impact
A `credits.href` value beginning with `javascript:` is assigned to the window location when the credits label is clicked, without being checked against an allowed-scheme list. An attacker who controls the chart configuration can therefore run script in the origin of the page hosting the chart. Exploitation requires that untrusted data reach the chart configuration and that a user click the credits label. Charts built with Highcharts Stock, Maps and Gantt are included, since those ship from the same package as Core.
### Workarounds
Drop-in fix - for any versions affected (5.0.0-13.0.2).
Add the below IIFE to run after Highcharts is loaded, but before a chart is created.
```js
!function(t){if(t&&t.Chart&&!t.Chart.prototype.creditsHrefPatched){var r=t.Chart.prototype,e=r.addCredits;r.addCredits=function(n){var o=t.merge(!0,this.options.credits,n);return o&&o.href&&!c(o.href)&&delete o.href,e.call(this,o)},r.creditsHrefPatched=!0}function c(r){var e=t.AST&&t.AST.allowedReferences||["https://","http://","mailto:","/","../","./","#"];return"string"==typeof r&&e.some(function(t){return 0===r.indexOf(t)})}}(Highcharts);
```
[Live demo & testing](https://jsfiddle.net/BlackLabel/6a09ws1f/)
### Obtaining the patched version
The patched releases are available from all the usual distribution channels. With npm, upgrade the affected package to the patched version listed above, for example `npm install highcharts@ 13.1.0`. If you load Highcharts from the CDN, use the versioned URLs on code.highcharts.com, for example `https://code.highcharts.com/13.1.0/highcharts.js`. For more on each installation method, see the [installation guide](https://www.highcharts.com/docs/getting-started/installation).