deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-3846-mfvc-xwpf
Package: openclaw (NPM)
Severity: HIGH (CVSS 7.1)
CWE: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Vulnerable versions: < 2026.2.22
Patched in: unpatched

Summary: Duplicate Advisory: Exec allowlist wrapper analysis did not unwrap env/shell dispatch chains

Details:
## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-jj82-76v6-933r. This link is maintained to preserve external references.

## Original Description
OpenClaw versions prior to 2026.2.22 contain an allowlist bypass vulnerability in system.run exec analysis that fails to unwrap env and shell-dispatch wrapper chains. Attackers can route execution through wrapper binaries like env bash to smuggle payloads that satisfy allowlist entries while executing non-allowlisted commands.
GitHub Security Advisory: GHSA-82gw-wqw6-r2cf
Package: openclaw (NPM)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Vulnerable versions: <= 2026.2.17
Patched in: unpatched

Summary: Duplicate Advisory: Command Injection via unescaped environment assignments in Windows Scheduled Task script generation

Details:
## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-pj5x-38rw-6fph. This link is maintained to preserve external references.

## Original Description
OpenClaw versions prior to 2026.2.19 contain a command injection vulnerability in Windows Scheduled Task script generation where environment variables are written to gateway.cmd using unquoted set KEY=VALUE assignments, allowing shell metacharacters to break out of assignment context. Attackers can inject arbitrary commands through environment variable values containing metacharacters like &, |, ^, %, or ! to achieve command execution when the scheduled task script is generated and executed.
GitHub Security Advisory: GHSA-pfj7-wv7c-22pr
Package: parse-server (NPM)
Severity: HIGH (CVSS 9.1)
CWE: CWE-287: Improper Authentication
Vulnerable versions: < 8.6.52
Patched in: 8.6.52

Summary: Parse Server has an auth provider validation bypass on login via partial authData

Details:
### Impact

An authentication bypass vulnerability allows an attacker to log in as any user who has linked a third-party authentication provider, without knowing the user's credentials. The attacker only needs to know the user's provider ID to gain full access to their account, including a valid session token.

This affects Parse Server deployments where the server option `allowExpiredAuthDataToken` is set to `true`. The default value is `false`.

### Patches

Auth providers are now always validated on login, regardless of the `allowExpiredAuthDataToken` setting. The option `allowExpiredAuthDataToken` has been deprecated and will be removed in a future major version.

### Workarounds

Set `allowExpiredAuthDataToken` to `false` (the default) or remove the option from the server configuration.
GitHub Security Advisory: GHSA-pfj7-wv7c-22pr
Package: parse-server (NPM)
Severity: HIGH (CVSS 9.1)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 9.0.0, < 9.6.0-alpha.41
Patched in: 9.6.0-alpha.41

Summary: Parse Server has an auth provider validation bypass on login via partial authData

Details:
### Impact

An authentication bypass vulnerability allows an attacker to log in as any user who has linked a third-party authentication provider, without knowing the user's credentials. The attacker only needs to know the user's provider ID to gain full access to their account, including a valid session token.

This affects Parse Server deployments where the server option `allowExpiredAuthDataToken` is set to `true`. The default value is `false`.

### Patches

Auth providers are now always validated on login, regardless of the `allowExpiredAuthDataToken` setting. The option `allowExpiredAuthDataToken` has been deprecated and will be removed in a future major version.

### Workarounds

Set `allowExpiredAuthDataToken` to `false` (the default) or remove the option from the server configuration.
GitHub Security Advisory: GHSA-vfx2-hv2g-xj5f
Package: @angular/ssr (NPM)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 20.0.0-next.0, < 20.3.21
Patched in: 20.3.21

Summary: Protocol-Relative URL Injection via Single Backslash Bypass in Angular SSR

Details:
An Open Redirect vulnerability exists in `@angular/ssr` due to an incomplete fix for CVE-2026-27738. While the original fix successfully blocked multiple leading slashes (e.g., `///`), the internal validation logic fails to account for a single backslash (`\`) bypass.

When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header:

- An attacker provides a value starting with a single backslash (e.g., `\evil.com`).
- The internal validation failed to flag the single backslash as invalid.
- The application prepends a leading forward slash, resulting in a `Location` header containing `/\evil.com`.
- Modern browsers interpret the `/\` sequence as `//`, treating it as a protocol-relative URL and redirecting the user to the attacker-controlled domain.

Furthermore, the response lacks the `Vary: X-Forwarded-Prefix` header, allowing the malicious redirect to be stored in intermediate caches (Web Cache Poisoning).

### Impact
This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking:

- **Scale**: A single request can poison a high-traffic route, impacting all users until the cache expires.
- **SEO Poisoning**: Search engine crawlers may follow and index these malicious redirects, causing the legitimate site to be delisted or associated with malicious domains.
- **Trust**: Because the initial URL belongs to the trusted domain, users and security tools are less likely to flag the redirect as malicious.

### Patches

- 22.0.0-next.2
- 21.2.3
- 20.3.21

### Workarounds
Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their `server.ts` before the Angular engine processes the request:

```ts
app.use((req, res, next) => {
  const prefix = req.headers['x-forwarded-prefix'];
  if (typeof prefix === 'string') {
    // Sanitize by removing all leading forward and backward slashes
    req.headers['x-forwarded-prefix'] = prefix.trim().replace(/^[/\\]+/, '/');
  }
  next();
});
```


### References

- Fix: https://github.com/angular/angular-cli/pull/32771
- Original CVE: CVE-2026-27738
GitHub Security Advisory: GHSA-vfx2-hv2g-xj5f
Package: @angular/ssr (NPM)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 21.0.0-next.0, < 21.2.3
Patched in: 21.2.3

Summary: Protocol-Relative URL Injection via Single Backslash Bypass in Angular SSR

Details:
An Open Redirect vulnerability exists in `@angular/ssr` due to an incomplete fix for CVE-2026-27738. While the original fix successfully blocked multiple leading slashes (e.g., `///`), the internal validation logic fails to account for a single backslash (`\`) bypass.

When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header:

- An attacker provides a value starting with a single backslash (e.g., `\evil.com`).
- The internal validation failed to flag the single backslash as invalid.
- The application prepends a leading forward slash, resulting in a `Location` header containing `/\evil.com`.
- Modern browsers interpret the `/\` sequence as `//`, treating it as a protocol-relative URL and redirecting the user to the attacker-controlled domain.

Furthermore, the response lacks the `Vary: X-Forwarded-Prefix` header, allowing the malicious redirect to be stored in intermediate caches (Web Cache Poisoning).

### Impact
This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking:

- **Scale**: A single request can poison a high-traffic route, impacting all users until the cache expires.
- **SEO Poisoning**: Search engine crawlers may follow and index these malicious redirects, causing the legitimate site to be delisted or associated with malicious domains.
- **Trust**: Because the initial URL belongs to the trusted domain, users and security tools are less likely to flag the redirect as malicious.

### Patches

- 22.0.0-next.2
- 21.2.3
- 20.3.21

### Workarounds
Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their `server.ts` before the Angular engine processes the request:

```ts
app.use((req, res, next) => {
  const prefix = req.headers['x-forwarded-prefix'];
  if (typeof prefix === 'string') {
    // Sanitize by removing all leading forward and backward slashes
    req.headers['x-forwarded-prefix'] = prefix.trim().replace(/^[/\\]+/, '/');
  }
  next();
});
```


### References

- Fix: https://github.com/angular/angular-cli/pull/32771
- Original CVE: CVE-2026-27738
GitHub Security Advisory: GHSA-vfx2-hv2g-xj5f
Package: @angular/ssr (NPM)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 22.0.0-next.0, < 22.0.0-next.2
Patched in: 22.0.0-next.2

Summary: Protocol-Relative URL Injection via Single Backslash Bypass in Angular SSR

Details:
An Open Redirect vulnerability exists in `@angular/ssr` due to an incomplete fix for CVE-2026-27738. While the original fix successfully blocked multiple leading slashes (e.g., `///`), the internal validation logic fails to account for a single backslash (`\`) bypass.

When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header:

- An attacker provides a value starting with a single backslash (e.g., `\evil.com`).
- The internal validation failed to flag the single backslash as invalid.
- The application prepends a leading forward slash, resulting in a `Location` header containing `/\evil.com`.
- Modern browsers interpret the `/\` sequence as `//`, treating it as a protocol-relative URL and redirecting the user to the attacker-controlled domain.

Furthermore, the response lacks the `Vary: X-Forwarded-Prefix` header, allowing the malicious redirect to be stored in intermediate caches (Web Cache Poisoning).

### Impact
This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking:

- **Scale**: A single request can poison a high-traffic route, impacting all users until the cache expires.
- **SEO Poisoning**: Search engine crawlers may follow and index these malicious redirects, causing the legitimate site to be delisted or associated with malicious domains.
- **Trust**: Because the initial URL belongs to the trusted domain, users and security tools are less likely to flag the redirect as malicious.

### Patches

- 22.0.0-next.2
- 21.2.3
- 20.3.21

### Workarounds
Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their `server.ts` before the Angular engine processes the request:

```ts
app.use((req, res, next) => {
  const prefix = req.headers['x-forwarded-prefix'];
  if (typeof prefix === 'string') {
    // Sanitize by removing all leading forward and backward slashes
    req.headers['x-forwarded-prefix'] = prefix.trim().replace(/^[/\\]+/, '/');
  }
  next();
});
```


### References

- Fix: https://github.com/angular/angular-cli/pull/32771
- Original CVE: CVE-2026-27738
GitHub Security Advisory: GHSA-ggm6-h3mx-cmmp
Package: openclaw (NPM)
Severity: LOW (CVSS 3.6)
CWE: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Vulnerable versions: <= 2026.2.17
Patched in: unpatched

Summary: Duplicate Advisory: safeBins stdin-only bypass via sort output and recursive grep flags

Details:
## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-4685-c5cp-vp95. This link is maintained to preserve external references.

## Original Description
OpenClaw versions prior to 2026.2.19 tools.exec.safeBins contains an input validation bypass vulnerability that allows attackers to execute unintended filesystem operations through sort output flags or recursive grep flags. Attackers with command execution access can leverage sort -o flag for arbitrary file writes or grep -R flag for recursive file reads, circumventing intended stdin-only restrictions.
GitHub Security Advisory: GHSA-8px5-2gfr-7ph6
Package: openclaw (NPM)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Vulnerable versions: >= 2026.1.21, <= 2026.2.17
Patched in: unpatched

Summary: Duplicate Advisory: OpenClaw has Windows Lobster shell fallback command injection in constrained fallback path

Details:
## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-fg3m-vhrr-8gj6. This link is maintained to preserve external references.

## Original Description
OpenClaw versions 2026.1.21 prior to 2026.2.19 contain a command injection vulnerability in the Lobster extension's Windows shell fallback mechanism that allows attackers to inject arbitrary commands through tool-provided arguments. When spawn failures trigger shell fallback with shell: true, attackers can exploit cmd.exe command interpretation to execute malicious commands by controlling workflow arguments.
GitHub Security Advisory: GHSA-5gqg-mqh5-2v39
Package: openclaw (NPM)
Severity: MODERATE (CVSS 7.1)
CWE: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Vulnerable versions: < 2026.2.19
Patched in: 2026.2.19

Summary: Duplicate Advisory: OpenClaw Windows Scheduled Task script generation allowed local command injection via unsafe cmd argument handling

Details:
## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-mqr9-vqhq-3jxw. This link is maintained to preserve external references.

## Original Description
OpenClaw versions prior to 2026.2.19 contain a local command injection vulnerability in Windows scheduled task script generation due to unsafe handling of cmd metacharacters and expansion-sensitive characters in gateway.cmd files. Local attackers with control over service script generation arguments can inject arbitrary commands by providing metacharacter-only values or CR/LF sequences that execute unintended code in the scheduled task context.
GitHub Security Advisory: GHSA-jrqm-vmqc-gm93
Package: ckeditor5 (NPM)
Severity: MODERATE (CVSS 6.4)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 29.0.0, < 47.6.0
Patched in: 47.6.0

Summary: CKEditor 5 has Cross-site Scripting (XSS) in the HTML Support package

Details:
### Impact
A Cross-Site Scripting (XSS) vulnerability has been discovered in the General HTML Support feature. This vulnerability could be triggered by inserting specially crafted markup, leading to unauthorized JavaScript code execution, if the editor instance used an unsafe General HTML Support configuration.

This vulnerability affects only installations where the editor configuration meets the following criteria:

* [General HTML Support](https://ckeditor.com/docs/ckeditor5/latest/features/html/general-html-support.html) is enabled,
* General HTML Support configuration allows inserting unsafe markup (see [Security](https://ckeditor.com/docs/ckeditor5/latest/features/html/general-html-support.html#security) section to learn more).

### Patches
The problem has been recognized and patched. The fix will be available in version 47.6.0 (and above).

### Workarounds
CKEditor 5 recommends configuring General HTML Support securely to ensure that unsafe content is not accepted. Please refer to the [Security](https://ckeditor.com/docs/ckeditor5/latest/features/html/general-html-support.html#security) section for detailed guidance.

### Credits
CKEditor 5 would like to thank: 
- Emilio Kevin
- Jeongwoo Lee, Younsoung Kim, Minseok Kim and Jinyeong Kim from ENKI Whitehat

for responsibly reporting this vulnerability.

### For more information
Email us at [security@cksource.com](mailto:security@cksource.com) if you have any questions or comments about this advisory.
GitHub Security Advisory: GHSA-jrqm-vmqc-gm93
Package: @ckeditor/ckeditor5-html-support (NPM)
Severity: MODERATE (CVSS 6.4)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 29.0.0, < 47.6.0
Patched in: 47.6.0

Summary: CKEditor 5 has Cross-site Scripting (XSS) in the HTML Support package

Details:
### Impact
A Cross-Site Scripting (XSS) vulnerability has been discovered in the General HTML Support feature. This vulnerability could be triggered by inserting specially crafted markup, leading to unauthorized JavaScript code execution, if the editor instance used an unsafe General HTML Support configuration.

This vulnerability affects only installations where the editor configuration meets the following criteria:

* [General HTML Support](https://ckeditor.com/docs/ckeditor5/latest/features/html/general-html-support.html) is enabled,
* General HTML Support configuration allows inserting unsafe markup (see [Security](https://ckeditor.com/docs/ckeditor5/latest/features/html/general-html-support.html#security) section to learn more).

### Patches
The problem has been recognized and patched. The fix will be available in version 47.6.0 (and above).

### Workarounds
CKEditor 5 recommends configuring General HTML Support securely to ensure that unsafe content is not accepted. Please refer to the [Security](https://ckeditor.com/docs/ckeditor5/latest/features/html/general-html-support.html#security) section for detailed guidance.

### Credits
CKEditor 5 would like to thank: 
- Emilio Kevin
- Jeongwoo Lee, Younsoung Kim, Minseok Kim and Jinyeong Kim from ENKI Whitehat

for responsibly reporting this vulnerability.

### For more information
Email us at [security@cksource.com](mailto:security@cksource.com) if you have any questions or comments about this advisory.
GitHub Security Advisory: GHSA-cgcg-q9jh-5pr2
Package: @keystone-6/core (NPM)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-863: Incorrect Authorization
Vulnerable versions: <= 6.5.1
Patched in: 6.5.2

Summary: @keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany (CVE-2025-46720 incomplete fix)

Details:
# Summary  
`{field}.isFilterable` access control can be bypassed in `findMany` queries by passing a `cursor`.  This can be used to confirm the existence of records by protected field values.

The fix for [CVE-2025-46720](https://github.com/keystonejs/keystone/security/advisories/GHSA-hg9m-67mm-7pg3) (field-level `isFilterable` bypass for update and delete mutations) added checks to the `where` parameter in `update` and `delete` mutations however the `cursor` parameter in `findMany` was not patched and accepts the same `UniqueWhere` input type.

# Impact  
This affects any project relying on `isFilterable` behaviour (at the list or field level) to prevent external users from using the filtering of fields as a discovery mechanism. `isFilterable` access control using a function can be bypassed by using the `cursor` input.

This has no impact on projects using `isFilterable: false` or `defaultIsFilterable: false` for sensitive fields, or if you have otherwise omitted filtering by these fields from your GraphQL schema. (See workarounds)

# Patches  
This issue has been patched in `@keystone-6/core` version 6.5.2.

# Workarounds  
To mitigate this issue in older versions where patching is not a viable pathway.

- Set `{field}.isFilterable: false` statically for relevant fields to prevent filtering by them earlier in the access control pipeline (that is, don't use functions)
- Set `{field}.graphql.omit.read: true` for relevant fields, which implicitly removes filtering by these fields your GraphQL schema
GitHub Security Advisory: GHSA-3x4c-7xq6-9pq8
Package: next (NPM)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 10.0.0, < 15.5.14
Patched in: 15.5.14

Summary: Next.js: Unbounded next/image disk cache growth can exhaust storage

Details:
## Summary
The default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth.

## Impact
An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. Note that this does not impact platforms that have their own image optimization capabilities, such as Vercel.

## Patches
Fixed by adding an LRU-backed disk cache with `images.maximumDiskCacheSize`, including eviction of least-recently-used entries when the limit is exceeded. Setting `maximumDiskCacheSize: 0` disables disk caching. 

## Workarounds
If upgrade is not immediately possible:
- Periodically clean `.next/cache/images`.
- Reduce variant cardinality (e.g., tighten values for `images.localPatterns`, `images.remotePatterns`, and `images.qualities`)
GitHub Security Advisory: GHSA-3x4c-7xq6-9pq8
Package: next (NPM)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 16.0.0-beta.0, < 16.1.7
Patched in: 16.1.7

Summary: Next.js: Unbounded next/image disk cache growth can exhaust storage

Details:
## Summary
The default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth.

## Impact
An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. Note that this does not impact platforms that have their own image optimization capabilities, such as Vercel.

## Patches
Fixed by adding an LRU-backed disk cache with `images.maximumDiskCacheSize`, including eviction of least-recently-used entries when the limit is exceeded. Setting `maximumDiskCacheSize: 0` disables disk caching. 

## Workarounds
If upgrade is not immediately possible:
- Periodically clean `.next/cache/images`.
- Reduce variant cardinality (e.g., tighten values for `images.localPatterns`, `images.remotePatterns`, and `images.qualities`)
GitHub Security Advisory: GHSA-866c-wwm5-4rj7
Package: openclaw (NPM)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-294: Authentication Bypass by Capture-replay
Vulnerable versions: <= 2026.2.24
Patched in: unpatched

Summary: Duplicate Advisory: OpenClaw's Nextcloud Talk webhook replay could trigger duplicate inbound processing

Details:
## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-r9q5-c7qc-p26w. This link is maintained to preserve external references.

## Original Description
OpenClaw versions prior to 2026.2.25 lack durable replay state for Nextcloud Talk webhook events, allowing valid signed webhook requests to be replayed without suppression. Attackers can capture and replay previously valid signed webhook requests to trigger duplicate inbound message processing and cause integrity or availability issues.
GitHub Security Advisory: GHSA-5326-6f73-m96w
Package: openclaw (NPM)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-184: Incomplete List of Disallowed Inputs
Vulnerable versions: < 2026.2.22
Patched in: unpatched

Summary: Duplicate Advisory: OpenClaw macOS companion app (beta): allowlist parsing mismatch for system.run shell chains

Details:
## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-5f9p-f3w2-fwch. This link is maintained to preserve external references.

## Original Description
OpenClaw versions prior to 2026.2.22 contain an allowlist parsing mismatch vulnerability in the macOS companion app that allows authenticated operators to bypass exec approval checks. Attackers with operator.write privileges and a paired macOS beta node can craft shell-chain payloads that pass incomplete allowlist validation and execute arbitrary commands on the paired host.