deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-38c7-23hj-2wgq
Package: n8n (NPM)
Severity: MODERATE (CVSS 4.0)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: >= 2.0.0, < 2.6.2
Patched in: 2.6.2

Summary: n8n has Webhook Forgery on Zendesk Trigger Node

Details:
## Impact
An attacker who knows the webhook URL of a workflow using the ZendeskTrigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node does not verify the HMAC-SHA256 signature that Zendesk attaches to every outbound webhook, allowing any party to inject crafted payloads into the connected workflow.

## Patches
The issue has been fixed in n8n versions 2.6.2 and 1.123.18. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Restrict network access to the n8n webhook endpoint to known Zendesk IP ranges.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-38c7-23hj-2wgq
Package: n8n (NPM)
Severity: MODERATE (CVSS 4.0)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: < 1.123.18
Patched in: 1.123.18

Summary: n8n has Webhook Forgery on Zendesk Trigger Node

Details:
## Impact
An attacker who knows the webhook URL of a workflow using the ZendeskTrigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node does not verify the HMAC-SHA256 signature that Zendesk attaches to every outbound webhook, allowing any party to inject crafted payloads into the connected workflow.

## Patches
The issue has been fixed in n8n versions 2.6.2 and 1.123.18. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Restrict network access to the n8n webhook endpoint to known Zendesk IP ranges.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-fvfv-ppw4-7h2w
Package: n8n (NPM)
Severity: MODERATE (CVSS 3.7)
CWE: CWE-20: Improper Input Validation, CWE-693: Protection Mechanism Failure
Vulnerable versions: < 2.10.0
Patched in: 2.10.0

Summary: n8n has a Guardrail Node Bypass

Details:
## Impact
An end user interacting with a workflow that uses the Guardrail node could craft an input that bypasses the default guardrail instructions.

## Patches
The issue has been fixed in n8n version 2.10.0. Users should upgrade to this version or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit access to trusted users.
- Review asses the practical impact of guardrail bypasses in your usecase and adjust your workflow accordingly.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-jh8h-6c9q-7gmw
Package: n8n (NPM)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 2.10.0, < 2.10.1
Patched in: 2.10.1

Summary: n8n has an Authentication Bypass in its Chat Trigger Node

Details:
## Impact
When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented. 
- This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default).

## Patches
The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Use a different authentication method for the Chat Trigger node, or restrict network access to the webhook endpoint to trusted origins.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-jh8h-6c9q-7gmw
Package: n8n (NPM)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 2.0.0, < 2.9.3
Patched in: 2.9.3

Summary: n8n has an Authentication Bypass in its Chat Trigger Node

Details:
## Impact
When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented. 
- This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default).

## Patches
The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Use a different authentication method for the Chat Trigger node, or restrict network access to the webhook endpoint to trusted origins.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-jh8h-6c9q-7gmw
Package: n8n (NPM)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-287: Improper Authentication
Vulnerable versions: < 1.123.22
Patched in: 1.123.22

Summary: n8n has an Authentication Bypass in its Chat Trigger Node

Details:
## Impact
When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented. 
- This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default).

## Patches
The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Use a different authentication method for the Chat Trigger node, or restrict network access to the webhook endpoint to trusted origins.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-vjf3-2gpj-233v
Package: n8n (NPM)
Severity: MODERATE (CVSS 6.3)
CWE: CWE-269: Improper Privilege Management, CWE-284: Improper Access Control, CWE-287: Improper Authentication
Vulnerable versions: < 2.8.0
Patched in: 2.8.0

Summary: n8n has an SSO Enforcement Bypass in its Self-Service Settings API

Details:
## Impact
An authenticated user signed in through Single Sign-On (SSO) could disable SSO enforcement for their own account through the n8n API. This allowed the user to create a local password and authenticate directly with email and password, completely bypassing the organization's SSO policy, centralized identity management, and any identity-provider-enforced multi-factor authentication.

## Patches
The issue has been fixed in n8n version 2.8.0. Users should upgrade to this version or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Monitor audit logs for users who create local credentials after authenticating via SSO.
- Restrict the n8n instance to fully trusted users only.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-qgvg-pr8v-6rr3
Package: svelte (NPM)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 5.53.0, < 5.53.5
Patched in: 5.53.5

Summary: Svelte: XSS via HTML Comment Injection in SSR Error Boundary Hydration Markers

Details:
Errors from `transformError` were not correctly escaped prior to being embedded in the HTML output, causing potential HTML injection and XSS if attacker-controlled content is returned from `transformError`.
GitHub Security Advisory: GHSA-phwv-c562-gvmh
Package: svelte (NPM)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: <= 5.53.4
Patched in: 5.53.5

Summary: Svelte vulnerable to XSS during SSR with contenteditable `bind:innerText` and `bind:textContent`

Details:
The contents of `bind:innerText` and `bind:textContent` on `contenteditable` elements were not properly escaped. This could enable HTML injection and Cross-site Scripting (XSS) if rendering untrusted data as the binding's initial value on the server.
GitHub Security Advisory: GHSA-gv5r-9gxr-v74w
Package: bootstrap-multiselect (NPM)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), CWE-352: Cross-Site Request Forgery (CSRF)
Vulnerable versions: < 2.0.0
Patched in: 2.0.0

Summary: Bootstrap Multiselect Vulnerable to CSRF and Reflective XSS via Arbitrary POST Data

Details:
An issue was discovered in post.php in bootstrap-multiselect (aka Bootstrap Multiselect) 1.1.2. A PHP script in the source code echoes arbitrary POST data. If a developer adopts this structure wholesale in a live application, it could create a Reflective Cross-Site Scripting (XSS) vulnerability exploitable through Cross-Site Request Forgery (CSRF).
GitHub Security Advisory: GHSA-r5mx-6wc6-7h9w
Package: dottie (NPM)
Severity: MODERATE (CVSS 6.3)
CWE: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Vulnerable versions: >= 2.0.4, <= 2.0.6
Patched in: 2.0.7

Summary: dottie is vulnerable to Prototype Pollution bypass via non-first path segments in set() and transform()

Details:
### Summary

dottie versions 2.0.4 through 2.0.6 contain an incomplete fix for CVE-2023-26132. The prototype pollution guard introduced in commit `7d3aee1` only validates the first segment of a dot-separated path, allowing an attacker to bypass the protection by placing `__proto__` at any position other than the first.

Both `dottie.set()` and `dottie.transform()` are affected.

### Details

The existing guard checks only `pieces[0] === '__proto__'`. When a path like `'a.__proto__.polluted'` is used, `pieces[0]` evaluates to `'a'`, not `'__proto__'`, so the guard is bypassed.

Inside the traversal loop, `current['__proto__'] = {}` triggers the `__proto__` setter, replacing the intermediate object's prototype. The final value is then written onto this new prototype.

**Important distinction:** This vulnerability does NOT pollute the global `Object.prototype`. It injects properties into a specific object's prototype chain. However, injected properties are invisible to `hasOwnProperty()` and `Object.keys()`, which makes them difficult to detect and can lead to authorization bypass in common coding patterns.

### PoC
```javascript
const dottie = require('dottie');

// set() bypass
const obj = {};
dottie.set(obj, 'session.__proto__.isAdmin', true);
console.log(obj.session.isAdmin);                    // true
console.log(({}).isAdmin);                           // undefined
console.log(obj.session.hasOwnProperty('isAdmin'));  // false

// transform() bypass
const flat = { 'user.__proto__.role': 'admin', 'user.name': 'guest' };
const result = dottie.transform(flat);
console.log(result.user.role);                       // 'admin'
console.log(({}).role);                              // undefined
```

Tested on Node.js v20 and v22, dottie 2.0.6, Windows 11.

### Impact

The primary risk is authorization bypass. In a typical server-side scenario where dottie is used to process user input (e.g., via Sequelize, which depends on dottie with ~1.3M weekly npm downloads), an attacker can inject properties like `isAdmin: true` into objects used for access control decisions. Since the injected property is not an own property, standard checks using `hasOwnProperty()` or `Object.keys()` will not reveal it, while property access like `if (session.isAdmin)` will return `true`.

Additionally, replacing an object's prototype via `current['__proto__'] = {}` strips all inherited methods, potentially causing TypeError exceptions and denial of service.
GitHub Security Advisory: GHSA-mqpr-49jj-32rc
Package: n8n (NPM)
Severity: MODERATE (CVSS 4.0)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: >= 2.0.0, < 2.5.0
Patched in: 2.5.0

Summary: n8n: Webhook Forgery on Github Webhook Trigger

Details:
## Impact
An attacker who knows the webhook URL of a workflow using the GitHub Webhook Trigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node did not implement the HMAC-SHA256 signature verification that GitHub provides to authenticate webhook deliveries, allowing any party to spoof GitHub webhook events.

## Patches
The issue has been fixed in n8n versions 2.5.0 and 1.123.15. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Restrict network access to the n8n webhook endpoint to known GitHub webhook IP ranges.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-mqpr-49jj-32rc
Package: n8n (NPM)
Severity: MODERATE (CVSS 4.0)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: < 1.123.15
Patched in: 1.123.15

Summary: n8n: Webhook Forgery on Github Webhook Trigger

Details:
## Impact
An attacker who knows the webhook URL of a workflow using the GitHub Webhook Trigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node did not implement the HMAC-SHA256 signature verification that GitHub provides to authenticate webhook deliveries, allowing any party to spoof GitHub webhook events.

## Patches
The issue has been fixed in n8n versions 2.5.0 and 1.123.15. Users should upgrade to one of these versions or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Restrict network access to the n8n webhook endpoint to known GitHub webhook IP ranges.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
GitHub Security Advisory: GHSA-f3f2-mcxc-pwjx
Package: n8n (NPM)
Severity: MODERATE (CVSS 8.2)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: < 2.4.0
Patched in: 2.4.0

Summary: n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes

Details:
## Impact
An authenticated user with permission to create or modify workflows and access to a database credential could unknowingly create a workflow that was vulnerable to SQL injection, even while expecting inputs to be handled safely through escaped parameters. By supplying specially crafted table or column names, an attacker could inject arbitrary SQL because the MySQL, PostgreSQL, and Microsoft SQL nodes did not escape identifier values when constructing queries, enabling injection through node configuration parameters.

## Patches
The issue has been fixed in n8n version 2.4.0. Users should upgrade to this version or later to remediate the vulnerability.

## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Disable the MySQL, PostgreSQL, and Microsoft SQL nodes by adding `n8n-nodes-base.mySql`, `n8n-nodes-base.postgres`, and `n8n-nodes-base.microsoftSql` to the `NODES_EXCLUDE` environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

## Credit

Reporter: Pawel Bednarz from the NATO Cyber Security Centre (NCSC)
GitHub Security Advisory: GHSA-4r4r-4jp4-wwf9
Package: @frangoteam/fuxa (NPM)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-288: Authentication Bypass Using an Alternate Path or Channel
Vulnerable versions: <= 1.2.8
Patched in: unpatched

Summary: FUXA has JWT Authentication Bypass via HTTP Referer header spoofing

Details:
FUXA 1.2.8 and prior contains an Authentication Bypass vulnerability leading to Remote Code Execution (RCE). The vulnerability exists in the server/api/jwt-helper.js middleware, which improperly trusts the HTTP "Referer" header to validate internal requests. A remote unauthenticated attacker can bypass JWT authentication by spoofing the Referer header to match the server's host. Successful exploitation allows the attacker to access the protected /api/runscript endpoint and execute arbitrary Node.js code on the server.
GitHub Security Advisory: GHSA-w789-49fc-v8hr
Package: terriajs-server (NPM)
Severity: HIGH (CVSS 0.0)
CWE: CWE-20: Improper Input Validation, CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: < 4.0.3
Patched in: 4.0.3

Summary: TerriaJS-Server has a domain validation bypass vulnerability in its proxy allowlist

Details:
### Impact
A validation bug allows an attacker to proxy domains not explicitly allowed in the `proxyableDomains` configuration.

The validation only checks if a hostname _ended_ with an allowed domain. This meant:

If `example.com` is allowed in `proxyableDomains`:

- ✅ example.com is allowed (correct)
- ✅ api.example.com is allowed (correct)
- ⚠️ maliciousexample.com is allowed (incorrect)

An attacker could register maliciousexample.com and proxy content through `terriajs-server`, bypassing proxy restrictions.

### Patches
All versions up to 4.0.2 are affected. Upgrade to 4.0.3 to address the vulnerability.
GitHub Security Advisory: GHSA-mjf5-7g4m-gx5w
Package: storybook (NPM)
Severity: HIGH (CVSS 0.0)
CWE: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), CWE-1385: Missing Origin Validation in WebSockets
Vulnerable versions: >= 10.0.0-beta.0, < 10.2.10
Patched in: 10.2.10

Summary: Storybook Dev Server is Vulnerable to WebSocket Hijacking

Details:
### Summary

The WebSocket functionality in Storybook's dev server, used to create and update stories, is vulnerable to WebSocket hijacking. This vulnerability **only affects the Storybook dev server; production builds are not impacted**.

### Details

Exploitation requires a developer to visit a malicious website while their local Storybook dev server is running. Because the WebSocket connection does not validate the origin of incoming connections, a malicious site can silently send WebSocket messages to the local instance without any further user interaction.

If a Storybook dev server is intentionally exposed publicly (e.g. for design reviews or stakeholder demos) the risk is higher, as no malicious site visit is required. Any unauthenticated attacker can send WebSocket messages to it directly.

The vulnerability affects the WebSocket message handlers for creating and saving stories, which can be exploited via unauthorized WebSocket connections to achieve persistent XSS or Remote Code Execution (RCE).

_Note: recent versions of Chrome have some protections against this, but Firefox does not._

### Impact
This vulnerability can lead to supply chain compromise. Key risks include:

- **Remote Code Execution**: The vulnerability can allow attackers to execute malicious code, with the extent of impact depending on the configuration. Server-side RCE is possible in non-default configurations, such as when stories are executed via portable stories in JSDOM, potentially allowing attackers to exfiltrate credentials and environment variables, access source code and the filesystem, establish backdoors, or pivot to internal network resources.
- **Persistent XSS**: Malicious payloads are written directly into story source files. If the malicious payload is committed to version control, it becomes part of the codebase and can propagate to deployed Storybook documentation sites, affecting developers and stakeholders who view them.
- **Supply Chain Propagation**: If the modified source files are committed, injected code can spread to other team members via git, execute in CI/CD pipelines, and affect shared component libraries used across multiple projects.

### Affected versions

8.1 and above. While the exploitable functionality was introduced in 8.1, the patch has been applied to 7.x as a precautionary measure given the underlying WebSocket behaviour.

### Recommended actions
Update to one of the patched versions: `7.6.23`, `8.6.17`, `9.1.19`, `10.2.10`.
GitHub Security Advisory: GHSA-mjf5-7g4m-gx5w
Package: storybook (NPM)
Severity: HIGH (CVSS 0.0)
CWE: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), CWE-1385: Missing Origin Validation in WebSockets
Vulnerable versions: >= 8.7.0-alpha.0, < 9.1.19
Patched in: 9.1.19

Summary: Storybook Dev Server is Vulnerable to WebSocket Hijacking

Details:
### Summary

The WebSocket functionality in Storybook's dev server, used to create and update stories, is vulnerable to WebSocket hijacking. This vulnerability **only affects the Storybook dev server; production builds are not impacted**.

### Details

Exploitation requires a developer to visit a malicious website while their local Storybook dev server is running. Because the WebSocket connection does not validate the origin of incoming connections, a malicious site can silently send WebSocket messages to the local instance without any further user interaction.

If a Storybook dev server is intentionally exposed publicly (e.g. for design reviews or stakeholder demos) the risk is higher, as no malicious site visit is required. Any unauthenticated attacker can send WebSocket messages to it directly.

The vulnerability affects the WebSocket message handlers for creating and saving stories, which can be exploited via unauthorized WebSocket connections to achieve persistent XSS or Remote Code Execution (RCE).

_Note: recent versions of Chrome have some protections against this, but Firefox does not._

### Impact
This vulnerability can lead to supply chain compromise. Key risks include:

- **Remote Code Execution**: The vulnerability can allow attackers to execute malicious code, with the extent of impact depending on the configuration. Server-side RCE is possible in non-default configurations, such as when stories are executed via portable stories in JSDOM, potentially allowing attackers to exfiltrate credentials and environment variables, access source code and the filesystem, establish backdoors, or pivot to internal network resources.
- **Persistent XSS**: Malicious payloads are written directly into story source files. If the malicious payload is committed to version control, it becomes part of the codebase and can propagate to deployed Storybook documentation sites, affecting developers and stakeholders who view them.
- **Supply Chain Propagation**: If the modified source files are committed, injected code can spread to other team members via git, execute in CI/CD pipelines, and affect shared component libraries used across multiple projects.

### Affected versions

8.1 and above. While the exploitable functionality was introduced in 8.1, the patch has been applied to 7.x as a precautionary measure given the underlying WebSocket behaviour.

### Recommended actions
Update to one of the patched versions: `7.6.23`, `8.6.17`, `9.1.19`, `10.2.10`.