deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-5v3h-x4wf-5c35
Package: github.com/rancher/rancher (GO)
Severity: HIGH (CVSS 8.4)
CWE: CWE-35: Path Traversal: '.../...//'
Vulnerable versions: >= 2.12.0, < 2.12.9
Patched in: 2.12.9

Summary: Rancher Extensions have arbitrary file access via path traversal

Details:
### Impact

A vulnerability has been identified in [Rancher's Extensions](https://ranchermanager.docs.rancher.com/integrations-in-rancher/rancher-extensions) where malicious code can be injected in Rancher through a path traversal in the `compressedEndpoint` field inside a `UIPlugin` deployment. A malicious UI extension could abuse that to:

- Overwrite Rancher binaries or configuration to inject code.
- Write to `/var/lib/rancher/` to tamper with cluster state.
- If `hostPath` volumes are mounted, write to the host node filesystem.
- Use this issue to chain with other attack vectors.

By default only the administrator can deploy UI extensions, unless permissions are granted to other users. It's always recommended to only install extensions that come from sources trusted by the user.

Please consult the associated  [MITRE CAPEC-126 - Technique - Path Traversal](https://capec.mitre.org/data/definitions/126.html) for further information about this category of attack.

### Patches

This vulnerability is addressed by ensuring that:

- The file defined by the UI Plugin CR's `compressedEndpoint` has to be created inside the cache directory and cannot contain `../`. If that is not possible, the installation will fail and the file won't be created. 
- The icons referenced by Cluster Repos' `index.yaml` file always resolves to a file inside the repository directory.

Patched versions of Rancher include releases v2.14.1, v2.13.5, v2.12.9, v2.11.13.

### Workarounds

There is no workaround. The user must be careful about which UI Plugins they install.

### Resources

If there are any questions or comments about this advisory:

- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
- Verify with the [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
GitHub Security Advisory: GHSA-5v3h-x4wf-5c35
Package: github.com/rancher/rancher (GO)
Severity: HIGH (CVSS 8.4)
CWE: CWE-35: Path Traversal: '.../...//'
Vulnerable versions: >= 2.13.0, < 2.13.5
Patched in: 2.13.5

Summary: Rancher Extensions have arbitrary file access via path traversal

Details:
### Impact

A vulnerability has been identified in [Rancher's Extensions](https://ranchermanager.docs.rancher.com/integrations-in-rancher/rancher-extensions) where malicious code can be injected in Rancher through a path traversal in the `compressedEndpoint` field inside a `UIPlugin` deployment. A malicious UI extension could abuse that to:

- Overwrite Rancher binaries or configuration to inject code.
- Write to `/var/lib/rancher/` to tamper with cluster state.
- If `hostPath` volumes are mounted, write to the host node filesystem.
- Use this issue to chain with other attack vectors.

By default only the administrator can deploy UI extensions, unless permissions are granted to other users. It's always recommended to only install extensions that come from sources trusted by the user.

Please consult the associated  [MITRE CAPEC-126 - Technique - Path Traversal](https://capec.mitre.org/data/definitions/126.html) for further information about this category of attack.

### Patches

This vulnerability is addressed by ensuring that:

- The file defined by the UI Plugin CR's `compressedEndpoint` has to be created inside the cache directory and cannot contain `../`. If that is not possible, the installation will fail and the file won't be created. 
- The icons referenced by Cluster Repos' `index.yaml` file always resolves to a file inside the repository directory.

Patched versions of Rancher include releases v2.14.1, v2.13.5, v2.12.9, v2.11.13.

### Workarounds

There is no workaround. The user must be careful about which UI Plugins they install.

### Resources

If there are any questions or comments about this advisory:

- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
- Verify with the [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
GitHub Security Advisory: GHSA-5v3h-x4wf-5c35
Package: github.com/rancher/rancher (GO)
Severity: HIGH (CVSS 8.4)
CWE: CWE-35: Path Traversal: '.../...//'
Vulnerable versions: >= 2.14.0, < 2.14.1
Patched in: 2.14.1

Summary: Rancher Extensions have arbitrary file access via path traversal

Details:
### Impact

A vulnerability has been identified in [Rancher's Extensions](https://ranchermanager.docs.rancher.com/integrations-in-rancher/rancher-extensions) where malicious code can be injected in Rancher through a path traversal in the `compressedEndpoint` field inside a `UIPlugin` deployment. A malicious UI extension could abuse that to:

- Overwrite Rancher binaries or configuration to inject code.
- Write to `/var/lib/rancher/` to tamper with cluster state.
- If `hostPath` volumes are mounted, write to the host node filesystem.
- Use this issue to chain with other attack vectors.

By default only the administrator can deploy UI extensions, unless permissions are granted to other users. It's always recommended to only install extensions that come from sources trusted by the user.

Please consult the associated  [MITRE CAPEC-126 - Technique - Path Traversal](https://capec.mitre.org/data/definitions/126.html) for further information about this category of attack.

### Patches

This vulnerability is addressed by ensuring that:

- The file defined by the UI Plugin CR's `compressedEndpoint` has to be created inside the cache directory and cannot contain `../`. If that is not possible, the installation will fail and the file won't be created. 
- The icons referenced by Cluster Repos' `index.yaml` file always resolves to a file inside the repository directory.

Patched versions of Rancher include releases v2.14.1, v2.13.5, v2.12.9, v2.11.13.

### Workarounds

There is no workaround. The user must be careful about which UI Plugins they install.

### Resources

If there are any questions or comments about this advisory:

- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
- Verify with the [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
GitHub Security Advisory: GHSA-fc67-c4hg-q653
Package: github.com/aws/amazon-ecs-agent (GO)
Severity: HIGH (CVSS 7.2)
CWE: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Vulnerable versions: >= 1.47.0, <= 1.102.2
Patched in: 1.103.0

Summary: Amazon ECS Container Agent (Windows) is vulnerable to Information Disclosure

Details:
### Summary
[Amazon Elastic Container Service (Amazon ECS)](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html) is a fully managed container orchestration service that enables customers to deploy, manage, and scale containerized applications. An issue exists where, under certain circumstances, improper input validation in the FSx Windows File Server volume mounting process allows command injection through specially crafted credentials. 

### Impact
Improper neutralization of inputs used in an OS command in the FSx Windows File Server volume mounting component in Amazon ECS Agent on Windows before 1.103.0 might allow a remote authenticated threat actor to execute shell commands with SYSTEM privileges on the underlying host via a specially crafted username field in an ECS task definition. This issue requires permissions to register ECS task definitions or write to the Secrets Manager or SSM Parameter Store credentials used by the FSx volume configuration.


To remediate this issue, users should upgrade to version 1.103.0.

**Impacted versions**: Version 1.47.0 through 1.102.2 of the ECS Agent for Windows

### Patches
This issue only impacts ECS Windows worker instances. ECS on Fargate is not affected. This issue has been addressed in ECS agent version 1.103.0.  Amazon ECS recommends [upgrading](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_window-container_instance.html) to the [latest](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-windows-ami-versions.html) Amazon ECS-optimized Windows AMI with an updated ECS agent version.

### Workarounds
Customers who cannot update to the latest AMI can restrict ecs:RegisterTaskDefinition permissions to trusted IAM principals only and restrict write access to Secrets Manager secrets referenced in FSx volume configurations.

### References
If you have any questions or comments about this advisory, Amazon ECS asks that users contact [AWS/Amazon] Security via [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.

### Acknowledgement

Amazon ECS would like to thank Sachin Patil for collaborating on this issue through the coordinated vulnerability disclosure process.
GitHub Security Advisory: GHSA-7v3r-m9c8-r855
Package: github.com/gotenberg/gotenberg/v8 (GO)
Severity: HIGH (CVSS 8.2)
CWE: CWE-184: Incomplete List of Disallowed Inputs
Vulnerable versions: <= 8.29.1
Patched in: unpatched

Summary: Gotenberg's ExifTool group-prefix syntax bypasses dangerous-tag blocklist

Details:
**Summary**

The ExifTool metadata write blocklist in Gotenberg v8 can be bypassed using ExifTool's group-prefix syntax, enabling arbitrary file rename, move, hardlink, and symlink creation on the server. This is a bypass of the fix for GHSA-qmwh-9m9c-h36m.

**Details**

The blocklist in `pkg/modules/exiftool/exiftool.go` filters four dangerous pseudo-tags (`FileName`, `Directory`, `HardLink`, `SymLink`) using `strings.EqualFold(key, tag)`. However, ExifTool supports group-prefix syntax where `File:FileName` is processed identically to `FileName` -- the prefix is stripped by `SetNewValue` in `Writer.pl` before tag matching.

The `safeKeyPattern` regex (`^[a-zA-Z0-9\-_.:]+$`) allows colons, so prefixed tag names pass validation. Any prefix works: `File:FileName`, `System:Directory`, `a:HardLink`, etc.

Additionally, `FilePermissions`, `FileUserID`, and `FileGroupID` pseudo-tags are not blocked at all and can modify file attributes without any prefix.

**PoC**

```bash
# Rename the converted PDF (bypasses FileName blocklist)
curl -F "files=@test.pdf" \
  -F 'metadata={"File:FileName":"pwned.pdf"}' \
  http://localhost:3000/forms/pdfengines/metadata/write

# Move the file to /tmp (bypasses Directory blocklist)
curl -F "files=@test.pdf" \
  -F 'metadata={"File:Directory":"/tmp"}' \
  http://localhost:3000/forms/pdfengines/metadata/write

# Create a symlink (bypasses SymLink blocklist)
curl -F "files=@test.pdf" \
  -F 'metadata={"File:SymLink":"/tmp/symlink-poc"}' \
  http://localhost:3000/forms/pdfengines/metadata/write

# Change file permissions (not blocked at all)
curl -F "files=@test.pdf" \
  -F 'metadata={"FilePermissions":"rwxrwxrwx"}' \
  http://localhost:3000/forms/pdfengines/metadata/write
```

**Impact**

Pre-auth (no authentication by default). Attacker can rename, move, or create links to files within the Gotenberg container. In deployments with mounted volumes or non-containerized setups, this enables arbitrary file read via symlink chaining and file overwrite via directory manipulation.

This is a direct bypass of the fix for GHSA-qmwh-9m9c-h36m.
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/xray (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/pgx-driver (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/otlp (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/okta (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/mysql-driver (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/iam (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/federated-auth (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/aws-secrets-manager (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-7wq2-32h4-9hc9
Package: github.com/aws/aws-advanced-go-wrapper/auth-helpers (GO)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.0.2
Patched in: 1.0.2

Summary: AWS Advanced Go Wrapper: Privilege Escalation in Aurora PostgreSQL Instance

Details:
### Description of Vulnerability: 
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

We recommend customers upgrade to the following versions:  AWS Go Wrapper to 2025-10-17


### Source of Vulnerability Report: 
Allistair Ishmael Hakim [allistair.hakim@gmail.com](mailto:allistair.hakim@gmail.com)


### Affected products & versions: 
AWS Go Wrapper < 2025-10-17


### Platforms:
 MacOS/Windows/Linux
GitHub Security Advisory: GHSA-9w9c-9w8m-w89q
Package: github.com/shellhub-io/shellhub (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-639: Authorization Bypass Through User-Controlled Key
Vulnerable versions: <= 0.24.1
Patched in: 0.24.2

Summary: ShellHub has cross-tenant IDOR in `GET /api/sessions/:uid` that discloses SSH session data

Details:
## Summary
`GET /api/sessions/:uid` returns the full session object for any authenticated caller, without scoping by the caller's tenant. An authenticated user can read session records (SSH username, device UID, remote IP, terminal type, authenticated flag, timestamps) belonging to any other namespace.

## Severity
**CVSS 3.1: 7.5 (High)** 
CWE-639

## Affected versions
ShellHub Community v0.24.1 (by code inspection — same vulnerable pattern as `GetDevice`). Not plant-reproducible without an active SSH session, but the flaw is structurally identical and confirmed via static analysis.

## Root cause
`api/services/session.go:37-44` — `GetSession` resolves the session by UID without any tenant filter:

  ```go
  func (s *service) GetSession(ctx context.Context, uid models.UID) (*models.Session, error) {
      session, err := s.store.SessionResolve(ctx, store.SessionUIDResolver, string(uid))
      // ⚠️ missing: s.store.Options().InNamespace(tenant)
      ...
  }
  ```

The `Authorize` middleware only verifies presence of a tenant in the context, not ownership of the requested session.

## Proof of concept

Pre-requisite: attacker has any valid user account and has obtained a session UID from the victim tenant (UIDs may leak via logs, shared session recordings, UI URLs, or through the device IDOR in the companion advisory since sessions reference devices by UID).

  ```bash
  ATTACKER_TOKEN=$(curl -s -X POST http://target/api/login \
    -H 'Content-Type: application/json' \
    -d '{"username":"attacker","password":"..."}' | jq -r .token)

  # Attempt cross-tenant read
  curl -i "http://target/api/sessions/<victim-session-uid>" \
    -H "Authorization: Bearer $ATTACKER_TOKEN"
  # Expected (fixed):   HTTP 403/404
  # Observed (v0.24.1): HTTP 200 + full session JSON
  ```

## Impact
  - Cross-tenant disclosure of SSH session data: target username, device UID, remote IP, authenticated status, session type, terminal, position (geolocation), started_at / last_seen timestamps.
  - Enables reconnaissance of other tenants' active users and systems; combined with session recording features, can enable deeper recon.

## Suggested fix
`api/services/session.go` — apply `InNamespace` in `GetSession`:

  ```go
  func (s *service) GetSession(ctx context.Context, uid models.UID) (*models.Session, error) {
      tenant := gateway.TenantFromContext(ctx)
      opts := []store.QueryOption{}
      if tenant != nil {
          opts = append(opts, s.store.Options().InNamespace(tenant.ID))
      }
      session, err := s.store.SessionResolve(ctx, store.SessionUIDResolver, string(uid), opts...)
      ...
  }
  ```