deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-2fcv-qww3-9v6h
Package: github.com/babylonlabs-io/babylon/v4 (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: < 4.1.0
Patched in: 4.1.0

Summary: Babylon's malformed vote extensions are not rejected

Details:
### Summary

Adversarial validators can send large vote extensions by using non-existing protobuf tags. This will result in the rejection of the subsequent block proposal. Eventually, all block proposals will be rejected by all validators.

### Impact

A small group of adversarial validators can cause a chain halt.
GitHub Security Advisory: GHSA-rj4j-2jph-gg43
Package: github.com/lf-edge/ekuiper/v2 (GO)
Severity: CRITICAL (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-23: Relative Path Traversal
Vulnerable versions: < 2.3.0
Patched in: 2.3.0

Summary: LF Edge eKuiper is vulnerable to Arbitrary File Read/Write via unsanitized names and zip extraction

Details:
### Summary
Multiple path traversal and unsafe path handling vulnerabilities were discovered in eKuiper prior to the fixes implemented in PR [lf-edge/ekuiper#3911](https://github.com/lf-edge/ekuiper/pull/3911). The issues allow attacker-controlled input (rule names, schema versions, plugin names, uploaded file names, and ZIP entries) to influence file system paths used by the application. In vulnerable deployments, this can permit files to be created, overwritten, or extracted outside the intended directories, potentially enabling disclosure of sensitive files, tampering with configuration or plugin binaries, denial of service, or other host compromise scenarios.

Several components used unvalidated user input when constructing filesystem paths or when extracting archives. In each case, input was accepted and used directly in path operations (join, create, delete, extract) without sufficient sanitization or canonicalization, allowing the input to include path separators, `..` segments, or absolute paths.

### Impact
**Arbitrary file overwrite / deletion:** attackers could overwrite or delete files outside the intended directory, which can corrupt application data, remove logs, or disable services.

### Resources
- https://github.com/lf-edge/ekuiper/commit/58362b089c76f08c400fe0dbb3667e6e871eaffd
- https://github.com/lf-edge/ekuiper/pull/3911
GitHub Security Advisory: GHSA-7ff4-jw48-3436
Package: github.com/openbao/openbao (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-266: Incorrect Privilege Assignment, CWE-269: Improper Privilege Management
Vulnerable versions: < 2.4.4
Patched in: 2.4.4

Summary: OpenBao is Vulnerable to Privileged Operator Identity Group Root Escalation

Details:
### Impact

Similar to HCSEC-2025-13 / CVE-2025-5999, a privileged operator could use the identity group subsystem to add a root policy to a group identity group, escalating their or another user's permissions in the system. Specifically this is an issue when:

1. An operator in the root namespace has access to `identity/groups` endpoints.
2. An operator does not have policy access.

Otherwise, an operator with policy access could create or modify an existing policy to grant root-equivalent permissions through the `sudo` capability.

### Patches

Patched in version 2.4.4. 

### Workarounds

Users should audit the use of identity subsystem and deny operators access if it is not in use.
GitHub Security Advisory: GHSA-9f46-w24h-69w4
Package: github.com/QuantumNous/new-api (GO)
Severity: HIGH (CVSS 8.5)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: < 0.9.6
Patched in: 0.9.6

Summary: new-api is vulnerable to SSRF Bypass

Details:
### Summary
A recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur.
Because the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet.

### Details
Use the following script to deploy on the attacker's server. Since ports 80, 443, and 8080 are default ports within the security range set by the administrator and will not be blocked, the service is deployed on port 8080.
```
from flask import Flask, redirect  
  
app = Flask(__name__)  
  
@app.route('/redirect')  
def ssrf_redirect():  
    return redirect('http://127.0.0.1:8003/uid.txt', code=302)  
  
if __name__ == '__main__':  
    app.run(host='0.0.0.0', port=8080)
```
Then, a request is made to the malicious service opened by the attacker, and it can be found that the resources on the intranet are successfully accessed.
<img width="663" height="60" alt="image" src="https://github.com/user-attachments/assets/2f296cff-510d-4cfe-8509-518e747bf8fe" />
At the same time, the locally opened service 127.0.0.1:8083/uid.txt also received related requests.
<img width="717" height="79" alt="image" src="https://github.com/user-attachments/assets/d6b6d2cc-280b-45b5-9946-10b7891bf017" />

### Impact
Using 302 redirects to bypass previous SSRF security fixes
GitHub Security Advisory: GHSA-w62r-7c53-fmc5
Package: github.com/grafana/grafana (GO)
Severity: CRITICAL (CVSS 10.0)
CWE: CWE-266: Incorrect Privilege Assignment
Vulnerable versions: >= 1.9.2-0[PII_REDACTED]0405-e6fdb746f235, < 1.9.2-0[PII_REDACTED]2618-ca5d89812015
Patched in: 1.9.2-0[PII_REDACTED]2618-ca5d89812015

Summary: Grafana Incorrect Privilege Assignment vulnerability

Details:
SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management.

In Grafana versions 12.x where SCIM provisioning is enabled and configured, a vulnerability in user identity handling allows a malicious or compromised SCIM client to provision a user with a numeric externalId, which in turn could allow to override internal user IDs and lead to impersonation or privilege escalation.

This vulnerability applies only if all of the following conditions are met:
- `enableSCIM` feature flag set to true
- `user_sync_enabled` config option in the `[auth.scim]` block set to true
GitHub Security Advisory: GHSA-w62r-7c53-fmc5
Package: github.com/grafana/grafana (GO)
Severity: CRITICAL (CVSS 10.0)
CWE: CWE-266: Incorrect Privilege Assignment
Vulnerable versions: >= 12.2.0, < 12.2.2
Patched in: 12.2.2

Summary: Grafana Incorrect Privilege Assignment vulnerability

Details:
SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management.

In Grafana versions 12.x where SCIM provisioning is enabled and configured, a vulnerability in user identity handling allows a malicious or compromised SCIM client to provision a user with a numeric externalId, which in turn could allow to override internal user IDs and lead to impersonation or privilege escalation.

This vulnerability applies only if all of the following conditions are met:
- `enableSCIM` feature flag set to true
- `user_sync_enabled` config option in the `[auth.scim]` block set to true
GitHub Security Advisory: GHSA-w62r-7c53-fmc5
Package: github.com/grafana/grafana (GO)
Severity: CRITICAL (CVSS 10.0)
CWE: CWE-266: Incorrect Privilege Assignment
Vulnerable versions: >= 12.1.0, < 12.1.4
Patched in: 12.1.4

Summary: Grafana Incorrect Privilege Assignment vulnerability

Details:
SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management.

In Grafana versions 12.x where SCIM provisioning is enabled and configured, a vulnerability in user identity handling allows a malicious or compromised SCIM client to provision a user with a numeric externalId, which in turn could allow to override internal user IDs and lead to impersonation or privilege escalation.

This vulnerability applies only if all of the following conditions are met:
- `enableSCIM` feature flag set to true
- `user_sync_enabled` config option in the `[auth.scim]` block set to true
GitHub Security Advisory: GHSA-w62r-7c53-fmc5
Package: github.com/grafana/grafana (GO)
Severity: CRITICAL (CVSS 10.0)
CWE: CWE-266: Incorrect Privilege Assignment
Vulnerable versions: >= 12.0.0, < 12.0.7
Patched in: 12.0.7

Summary: Grafana Incorrect Privilege Assignment vulnerability

Details:
SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management.

In Grafana versions 12.x where SCIM provisioning is enabled and configured, a vulnerability in user identity handling allows a malicious or compromised SCIM client to provision a user with a numeric externalId, which in turn could allow to override internal user IDs and lead to impersonation or privilege escalation.

This vulnerability applies only if all of the following conditions are met:
- `enableSCIM` feature flag set to true
- `user_sync_enabled` config option in the `[auth.scim]` block set to true
GitHub Security Advisory: GHSA-gmm6-j2g5-r52m
Package: github.com/hashicorp/terraform-provider-vault (GO)
Severity: HIGH (CVSS 7.4)
CWE: CWE-1188: Initialization of a Resource with an Insecure Default
Vulnerable versions: < 5.5.0
Patched in: 5.5.0

Summary: Vault’s Terraform Provider incorrectly set default deny_null_bind parameter for LDAP auth method to false by default

Details:
Vault’s Terraform Provider incorrectly set the default deny_null_bind parameter for the LDAP auth method to false by default, potentially resulting in an insecure configuration. If the underlying LDAP server allowed anonymous or unauthenticated binds, this could result in authentication bypass. This vulnerability, CVE-2025-13357, is fixed in Vault Terraform Provider v5.5.0.
GitHub Security Advisory: GHSA-9m7r-g8hg-x3vr
Package: github.com/authzed/spicedb (GO)
Severity: LOW (CVSS 0.0)
CWE: CWE-277: Insecure Inherited Permissions
Vulnerable versions: < 1.47.1
Patched in: 1.47.1

Summary: SpiceDB: LookupResources with Multiple Entrypoints across Different Definitions Can Return Incomplete Results

Details:
### Impact

If a schema includes the following characteristics:

1. Permission defined in terms of a union (`+`)
1. That union references the same relation on both sides, but one side arrows to a different permission

Then you might have missing `LookupResources` results when checking the permission. This only affects `LookupResources`; other APIs calculate permissionship correctly.

A small concrete example:

```
relation doer_of_things: user | group#member
permission do_the_thing = doer_of_things + doer_of_things->admin
```

A CheckPermission on `do_the_thing` will return the correct permissionship, but a LookupResources on `do_the_thing` may miss resources.

#### A Comprehensive Example

If you have a schema with a structure like this:

```
definition special_user {}

definition user {
  relation special_user_mapping: special_user
  permission special_user = special_user_mapping
}
definition group {
   relation member: user
   permission membership = member + member->special_user
}

definition system {
  relation viewer: user | group#membership
  // This is the problematic permission
  permission view = viewer + viewer->special_user
}
```

And these relationships:
```
system:somesystem#viewer@group:somegroup#membership
group:somegroup#member@user:someuser1
user:someuser1#special_user_mapping@special_user:specialuser
```

And you call LookupResources with:
```
subject_type: user
subject_id: someuser1
permission: view
resource_type: system
```

You would expect to receive `system:somesystem` in the results, but you do not.

Note that this only applies to `LookupResources`; if you `CheckPermission` for that resource specifically, it will return `HasPermission`.

### Patches

The issue is fixed in v1.47.1. Upgrading to this version will remediate this issue.
GitHub Security Advisory: GHSA-f786-75f3-74xj
Package: github.com/google/osv-scalibr (GO)
Severity: LOW (CVSS 0.0)
CWE: CWE-476: NULL Pointer Dereference
Vulnerable versions: < 0.3.4
Patched in: 0.3.4

Summary: OSV-SCALIBR has NULL Pointer Dereference

Details:
A bug in the filesystem traversal fallback path causes fs/diriterate/diriterate.go:Next() to overindex an empty slice when ReadDir returns nil for an empty directory, resulting in a panic (index out of range) and an application crash (denial of service) in OSV-SCALIBR.
GitHub Security Advisory: GHSA-8qg8-c7mw-6fj7
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 4.3.0-rc1, < 4.3.0
Patched in: 4.3.0

Summary: Mattermost Server is vulnerable to Directory Traversal by System Admins

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 when local storage for files is used. A System Admin can achieve directory traversal.
GitHub Security Advisory: GHSA-8qg8-c7mw-6fj7
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 4.2.0-rc1, < 4.2.1-0[PII_REDACTED]4140-6d3cb2ce07fc
Patched in: 4.2.1-0[PII_REDACTED]4140-6d3cb2ce07fc

Summary: Mattermost Server is vulnerable to Directory Traversal by System Admins

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 when local storage for files is used. A System Admin can achieve directory traversal.
GitHub Security Advisory: GHSA-8qg8-c7mw-6fj7
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: < 4.1.2-0[PII_REDACTED]1910-6be8113eb60
Patched in: 4.1.2-0[PII_REDACTED]1910-6be8113eb60

Summary: Mattermost Server is vulnerable to Directory Traversal by System Admins

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 when local storage for files is used. A System Admin can achieve directory traversal.
GitHub Security Advisory: GHSA-5mh6-p63g-3mv5
Package: github.com/mattermost/mattermost-server (GO)
Severity: HIGH (CVSS 7.5)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: < 5.1.0
Patched in: 5.1.0

Summary: Mattermost Server is vulnerable to a Denial of Service attack through `invite_people` command

Details:
An issue was discovered in Mattermost Server before 5.1.0. It allows attackers to cause a denial of service via the invite_people slash command.
GitHub Security Advisory: GHSA-f6x5-jh6r-wrfv
Package: golang.org/x/crypto (GO)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-125: Out-of-bounds Read
Vulnerable versions: < 0.45.0
Patched in: 0.45.0

Summary: golang.org/x/crypto/ssh/agent vulnerable to panic if message is malformed due to out of bounds read

Details:
SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.
GitHub Security Advisory: GHSA-j5w8-q4qc-rx2x
Package: golang.org/x/crypto (GO)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: < 0.45.0
Patched in: 0.45.0

Summary: golang.org/x/crypto/ssh allows an attacker to cause unbounded memory consumption

Details:
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
GitHub Security Advisory: GHSA-ch7q-53v8-73pc
Package: goauthentik.io (GO)
Severity: MODERATE (CVSS 5.8)
CWE: CWE-613: Insufficient Session Expiration
Vulnerable versions: < 0.0.0[PII_REDACTED]5424-6672e6aaa41e
Patched in: 0.0.0[PII_REDACTED]5424-6672e6aaa41e

Summary: authentik's invitation expiry is delayed by at least 5 minutes

Details:
### Summary

In previous authentik versions, invitations were considered valid regardless if they are expired or not, thus relying on background tasks to clean up expired ones. In a normal scenario this can take up to 5 minutes because the cleanup of expired objects is scheduled to run every 5 minutes. However, with a large amount of tasks in the backlog, this might take longer.

### Patches

authentik 2025.8.5 and 2025.10.2 fix this issue; for other versions the workaround below can be used.

### Workarounds

Users can create a policy that explicitly checks whether the invitation is still valid, and then bind it to the invitation stage on your invitation flow, and deny access if the invitation is not valid.

```python
return not context['flow_plan'].context['invitation'].is_expired
```

### For more information

If users have any questions or comments about this advisory:

- Email the authentik team at [security@goauthentik.io](mailto:security@goauthentik.io).
GitHub Security Advisory: GHSA-xr73-jq5p-ch8r
Package: goauthentik.io (GO)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-286: Incorrect User Management, CWE-289: Authentication Bypass by Alternate Name
Vulnerable versions: < 0.0.0[PII_REDACTED]0106-9dbdfc3f1be0
Patched in: 0.0.0[PII_REDACTED]0106-9dbdfc3f1be0

Summary: authentik allows a deactivated Service account to authenticate to OAuth

Details:
### Summary

When authenticating with `client_id` and `client_secret` to an OAuth provider, authentik creates a service account for the provider. In previous authentik versions, authentication for this account was possible even when the account was deactivated. Other permissions are correctly applied and federation with other providers still take assigned policies correctly into account.

### Patches

authentik 2025.8.5 and 2025.10.2 fix this issue, for other versions the workaround below can be used.

### Workarounds

You can add a policy to your application that explicitly checks if the service account is still valid, and deny access if not.

```python
return request.user.is_active
```

### For more information

If you have any questions or comments about this advisory:

- Email us at [security@goauthentik.io](mailto:security@goauthentik.io).
GitHub Security Advisory: GHSA-9hh7-6558-qfp2
Package: github.com/mattermost/mattermost/server/v8 (GO)
Severity: LOW (CVSS 3.0)
CWE: CWE-276: Incorrect Default Permissions
Vulnerable versions: < 8.0.0[PII_REDACTED]0616-ba86dfc5876b6
Patched in: 8.0.0[PII_REDACTED]0616-ba86dfc5876b6

Summary: Mattermost allows other users to determine when users had read channels via channel member objects

Details:
Mattermost versions 10.11.x <= 10.11.3, and 10.5.x <= 10.5.11 fail to enforce access permissions on the Agents plugin which allows other users to determine when users had read channels via channel member objects.
GitHub Security Advisory: GHSA-9hh7-6558-qfp2
Package: github.com/mattermost/mattermost-server (GO)
Severity: LOW (CVSS 3.0)
CWE: CWE-276: Incorrect Default Permissions
Vulnerable versions: >= 10.5.0, < 10.5.12
Patched in: 10.5.12

Summary: Mattermost allows other users to determine when users had read channels via channel member objects

Details:
Mattermost versions 10.11.x <= 10.11.3, and 10.5.x <= 10.5.11 fail to enforce access permissions on the Agents plugin which allows other users to determine when users had read channels via channel member objects.
GitHub Security Advisory: GHSA-9hh7-6558-qfp2
Package: github.com/mattermost/mattermost-server (GO)
Severity: LOW (CVSS 3.0)
CWE: CWE-276: Incorrect Default Permissions
Vulnerable versions: >= 10.11.0, < 10.11.4
Patched in: 10.11.4

Summary: Mattermost allows other users to determine when users had read channels via channel member objects

Details:
Mattermost versions 10.11.x <= 10.11.3, and 10.5.x <= 10.5.11 fail to enforce access permissions on the Agents plugin which allows other users to determine when users had read channels via channel member objects.
GitHub Security Advisory: GHSA-3g2j-vm47-x4mj
Package: github.com/canonical/lxd (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-269: Improper Privilege Management
Vulnerable versions: < 0.0.0[PII_REDACTED]4034-698854d0164f
Patched in: 0.0.0[PII_REDACTED]4034-698854d0164f

Summary: LXD vulnerable to a local privilege escalation through custom storage volumes

Details:
**Impact**

This affects any LXD user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the `security.shifted` property set to `true` as well as access to the host as an unprivileged user.

The most common case for this would be systems using `lxd-user` with the less privileged lxd group to provide unprivileged users with an isolated restricted access to LXD. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unprivileged user on the host to gain root privileges.

**Patches**

Patches for this issue are available: 

- LXD 6 series: https://github.com/canonical/lxd/pull/16904
- LXD 5.21 LTS series: https://github.com/canonical/lxd/pull/16922
- LXD 5.0 LTS series: https://github.com/canonical/lxd/pull/16923
- LXD 4.0 LTS series: https://github.com/canonical/lxd/pull/16924 

The first commit changes the permissions for any new storage pool, the later commit adds a patch that applies it on startup to all existing storage pools.

These fixes are also available in the associated candidate snap channels for each LTS series:

- 5.21/candidate (5.21.4-8a3cf61)
- 5.0/candidate (5.0.5-5c60378)
- 4.0/candidate (4.0.10-35a8127)

We will be preparing intermediate releases to the associated stable snap channels shortly.

**Workarounds**

Permissions can be manually restricted until a patched version of LXD is deployed.

This is done with:

```
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0700 /var/snap/lxd/common/lxd/storage-pools/*/{custom*,virtual-machines*,images}
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0711 /var/snap/lxd/common/lxd/storage-pools/*/{containers*,buckets*}
```

Those are the same permissions which will be applied by the patched LXD for both new and existing storage pools.

**References**

This was reported to Incus publicly on Github here: 

- https://github.com/lxc/incus/security/advisories/GHSA-56mx-8g9f-5crf
- https://github.com/lxc/incus/issues/2641
GitHub Security Advisory: GHSA-mqp8-pgg5-7x7m
Package: github.com/mattermost/mattermost/server/v8 (GO)
Severity: MODERATE (CVSS 4.9)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: < 8.0.0[PII_REDACTED]2932-a41db04d2746
Patched in: 8.0.0[PII_REDACTED]2932-a41db04d2746

Summary: Mattermost allows system administrators to access password hashes and MFA secrets

Details:
Mattermost versions 10.11.x <= 10.11.3, 10.5.x <= 10.5.11, 10.12.x <= 10.12.0 fail to sanitize user data which allows system administrators to access password hashes and MFA secrets via the POST /api/v4/users/{user_id}/email/verify/member endpoint
GitHub Security Advisory: GHSA-mqp8-pgg5-7x7m
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.9)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: >= 10.12.0, < 10.12.1
Patched in: 10.12.1

Summary: Mattermost allows system administrators to access password hashes and MFA secrets

Details:
Mattermost versions 10.11.x <= 10.11.3, 10.5.x <= 10.5.11, 10.12.x <= 10.12.0 fail to sanitize user data which allows system administrators to access password hashes and MFA secrets via the POST /api/v4/users/{user_id}/email/verify/member endpoint