deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-2mj3-6grc-px38
Package: github.com/elastic/beats/v7 (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'), CWE-1284: Improper Validation of Specified Quantity in Input
Vulnerable versions: < 7.0.0-alpha2.0[PII_REDACTED]4633-dd3af18220bf
Patched in: 7.0.0-alpha2.0[PII_REDACTED]4633-dd3af18220bf

Summary: Filebeat Beats has Buffer Overflow via Malformed Syslog Message or Malicious Tokenizer Pattern in Dissect Configuration

Details:
Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) in Filebeat Syslog parser and the Libbeat Dissect processor can allow a user to trigger a Buffer Overflow (CAPEC-100) and cause a denial of service (panic/crash) of the Filebeat process via either a malformed Syslog message or a malicious tokenizer pattern in the Dissect configuration.
GitHub Security Advisory: GHSA-2mj3-6grc-px38
Package: github.com/elastic/beats/v7 (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'), CWE-1284: Improper Validation of Specified Quantity in Input
Vulnerable versions: >= 9.2.0, < 9.2.3
Patched in: 9.2.3

Summary: Filebeat Beats has Buffer Overflow via Malformed Syslog Message or Malicious Tokenizer Pattern in Dissect Configuration

Details:
Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) in Filebeat Syslog parser and the Libbeat Dissect processor can allow a user to trigger a Buffer Overflow (CAPEC-100) and cause a denial of service (panic/crash) of the Filebeat process via either a malformed Syslog message or a malicious tokenizer pattern in the Dissect configuration.
GitHub Security Advisory: GHSA-2mj3-6grc-px38
Package: github.com/elastic/beats/v7 (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'), CWE-1284: Improper Validation of Specified Quantity in Input
Vulnerable versions: >= 9.0.0, < 9.1.9
Patched in: 9.1.9

Summary: Filebeat Beats has Buffer Overflow via Malformed Syslog Message or Malicious Tokenizer Pattern in Dissect Configuration

Details:
Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) in Filebeat Syslog parser and the Libbeat Dissect processor can allow a user to trigger a Buffer Overflow (CAPEC-100) and cause a denial of service (panic/crash) of the Filebeat process via either a malformed Syslog message or a malicious tokenizer pattern in the Dissect configuration.
GitHub Security Advisory: GHSA-2mj3-6grc-px38
Package: github.com/elastic/beats/v7 (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'), CWE-1284: Improper Validation of Specified Quantity in Input
Vulnerable versions: >= 7.7.0, < 8.19.9
Patched in: 8.19.9

Summary: Filebeat Beats has Buffer Overflow via Malformed Syslog Message or Malicious Tokenizer Pattern in Dissect Configuration

Details:
Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) in Filebeat Syslog parser and the Libbeat Dissect processor can allow a user to trigger a Buffer Overflow (CAPEC-100) and cause a denial of service (panic/crash) of the Filebeat process via either a malformed Syslog message or a malicious tokenizer pattern in the Dissect configuration.
GitHub Security Advisory: GHSA-f6mr-38g8-39rg
Package: github.com/ollama/ollama (GO)
Severity: CRITICAL (CVSS 0.0)
CWE: CWE-284: Improper Access Control, CWE-306: Missing Authentication for Critical Function
Vulnerable versions: <= 0.13.5
Patched in: unpatched

Summary: Ollama Platform has missing authentication enabling attackers to perform model management operations

Details:
A critical authentication bypass vulnerability exists in Ollama platform's API endpoints in versions prior to and including v0.12.3. The platform exposes multiple API endpoints without requiring authentication, enabling remote attackers to perform unauthorized model management operations.
GitHub Security Advisory: GHSA-3g75-q268-r9r6
Package: github.com/aws/amazon-s3-encryption-client-go/v3 (GO)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Vulnerable versions: < 4.0.0
Patched in: 4.0.0

Summary: Amazon S3 Encryption Client has a Key Commitment Issue

Details:
## Summary

S3 Encryption Client for Go is an open-source client-side encryption library used to facilitate writing and reading encrypted records to S3.  

When the encrypted data key (EDK) is stored in an "Instruction File" instead of S3's metadata record, the EDK is exposed to an "Invisible Salamanders" attack  (https://eprint.iacr.org/2019/016), which could allow the EDK to be replaced with a new key. 



## Impact

### Background - Key Commitment

There is a cryptographic property whereby under certain conditions, a single ciphertext can be decrypted into 2 different plaintexts by using different encryption keys.  To address this issue, strong encryption schemes use what is known as "key commitment", a process by which an encrypted message can only be decrypted by one key; the key used to originally encrypt the message. 

In older versions of S3EC, when customers are also using a feature called "Instruction File" to store EDKs, key commitment is not implemented because multiple EDKs could be associated to an underlying encrypted message object.  For such customers an attack that leverages the lack of key commitment is possible.  A bad actor would need two things to leverage this issue: (i) the ability to create a separate, rogue, EDK that will also decrypt the underlying object to produce desired plaintext, and (ii) permission to upload a new instruction file to the S3 bucket to replace the existing instruction file placed there by the user using the S3C.  Any future attempt to decrypt the underlying encrypted message with the S3EC will unwittingly use the rogue EDK to produce a valid plaintext message.

Impacted versions: <= v3.1


### Patches

Amazon S3 Encryption Client is introducing the concept of "key commitment" to S3EC where the EDK is cryptographically bound to the ciphertext in order to address this issue.  In order to maintain compatibility for in-flight messages we are releasing the fix in two versions.  A code-compatible minor version that can read messages with key-commitment but not write them, and a new major version that can both read and write messages with key-commitment.  For maximum safety customers are asked to upgrade to the latest major version: v4.0.0 or later.

## Workarounds

There are no workarounds, please upgrade to the suggested version of S3EC.

## References

If customers have any questions or comments about this advisory, Amazon S3 Encryption Client asks that they contact AWS Security through the issue reporting page or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.
GitHub Security Advisory: GHSA-q66g-q98c-q454
Package: github.com/mattermost/mattermost (GO)
Severity: LOW (CVSS 3.1)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 11.0.0-alpha.1, < 11.1.0
Patched in: 11.1.0

Summary: Mattermost has missing redirect URL validation

Details:
Mattermost versions 10.11.x <= 10.11.4 fail to validate redirect URLs on the /error page, which allows an attacker to redirect a victim to a malicious site via a crafted link opened in a new tab.
GitHub Security Advisory: GHSA-q66g-q98c-q454
Package: github.com/mattermost/mattermost (GO)
Severity: LOW (CVSS 3.1)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 10.11.0-rc1, < 10.11.5-0[PII_REDACTED]1338-dad6bd7a1509
Patched in: 10.11.5-0[PII_REDACTED]1338-dad6bd7a1509

Summary: Mattermost has missing redirect URL validation

Details:
Mattermost versions 10.11.x <= 10.11.4 fail to validate redirect URLs on the /error page, which allows an attacker to redirect a victim to a malicious site via a crafted link opened in a new tab.
GitHub Security Advisory: GHSA-q66g-q98c-q454
Package: github.com/mattermost/mattermost/server/v8 (GO)
Severity: LOW (CVSS 3.1)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 8.0.0[PII_REDACTED]2209-4952acea88ce, < 8.0.0[PII_REDACTED]1338-dad6bd7a1509
Patched in: 8.0.0[PII_REDACTED]1338-dad6bd7a1509

Summary: Mattermost has missing redirect URL validation

Details:
Mattermost versions 10.11.x <= 10.11.4 fail to validate redirect URLs on the /error page, which allows an attacker to redirect a victim to a malicious site via a crafted link opened in a new tab.
GitHub Security Advisory: GHSA-jf5h-xfw4-p8gp
Package: github.com/mattermost/mattermost-plugin-github (GO)
Severity: LOW (CVSS 3.0)
CWE: CWE-1287: Improper Validation of Specified Type of Input
Vulnerable versions: < 1.0.1-0[PII_REDACTED]5715-0deffcfc6bee
Patched in: 1.0.1-0[PII_REDACTED]5715-0deffcfc6bee

Summary: Mattermost GitHub Plugin Bot Identity Validation Bypass Allows Arbitrary GitHub Reaction Injection

Details:
Mattermost versions 10.11.x <= 10.11.6 and Mattermost GitHub plugin versions <=2.4.0 fail to validate plugin bot identity in reaction forwarding which allows attackers to hijack the GitHub reaction feature to make users add reactions to arbitrary GitHub objects via crafted notification posts.
GitHub Security Advisory: GHSA-jf5h-xfw4-p8gp
Package: github.com/mattermost/mattermost (GO)
Severity: LOW (CVSS 3.0)
CWE: CWE-1287: Improper Validation of Specified Type of Input
Vulnerable versions: >= 11.0.0-alpha.1, < 11.1.0
Patched in: 11.1.0

Summary: Mattermost GitHub Plugin Bot Identity Validation Bypass Allows Arbitrary GitHub Reaction Injection

Details:
Mattermost versions 10.11.x <= 10.11.6 and Mattermost GitHub plugin versions <=2.4.0 fail to validate plugin bot identity in reaction forwarding which allows attackers to hijack the GitHub reaction feature to make users add reactions to arbitrary GitHub objects via crafted notification posts.
GitHub Security Advisory: GHSA-jf5h-xfw4-p8gp
Package: github.com/mattermost/mattermost (GO)
Severity: LOW (CVSS 3.0)
CWE: CWE-1287: Improper Validation of Specified Type of Input
Vulnerable versions: < 10.11.7-0[PII_REDACTED]3514-3b05384dd014
Patched in: 10.11.7-0[PII_REDACTED]3514-3b05384dd014

Summary: Mattermost GitHub Plugin Bot Identity Validation Bypass Allows Arbitrary GitHub Reaction Injection

Details:
Mattermost versions 10.11.x <= 10.11.6 and Mattermost GitHub plugin versions <=2.4.0 fail to validate plugin bot identity in reaction forwarding which allows attackers to hijack the GitHub reaction feature to make users add reactions to arbitrary GitHub objects via crafted notification posts.
GitHub Security Advisory: GHSA-jf5h-xfw4-p8gp
Package: github.com/mattermost/mattermost/server/v8 (GO)
Severity: LOW (CVSS 3.0)
CWE: CWE-1287: Improper Validation of Specified Type of Input
Vulnerable versions: >= 10.11.0-rc1, < 10.11.7-0[PII_REDACTED]3514-3b05384dd014
Patched in: 10.11.7-0[PII_REDACTED]3514-3b05384dd014

Summary: Mattermost GitHub Plugin Bot Identity Validation Bypass Allows Arbitrary GitHub Reaction Injection

Details:
Mattermost versions 10.11.x <= 10.11.6 and Mattermost GitHub plugin versions <=2.4.0 fail to validate plugin bot identity in reaction forwarding which allows attackers to hijack the GitHub reaction feature to make users add reactions to arbitrary GitHub objects via crafted notification posts.
GitHub Security Advisory: GHSA-gm3x-23wp-hc2c
Package: github.com/traefik/traefik/v3 (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-436: Interpretation Conflict
Vulnerable versions: < 3.6.3
Patched in: 3.6.3

Summary: Path Normalization Bypass in Traefik Router + Middleware Rules

Details:
## Impact

There is a potential vulnerability in Traefik managing the requests using a `PathPrefix`, `Path` or `PathRegex` matcher.

When Traefik is configured to route the requests to a backend using a matcher based on the path; if the request path contains an encoded restricted character from the following set **('/', '\', 'Null', ';', '?', '#')**, it’s possible to target a backend, exposed using another router, by-passing the middlewares chain.

## Example

```yaml
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
metadata:
  name: my-service
spec:
  routes:
    - match: PathPrefix(‘/admin/’)
      kind: Rule
      services:
        - name: service-a
          port: 8080
      middlewares:
        - name: my-security-middleware
    - match: PathPrefix(‘/’)
      kind: Rule
      services:
        - name: service-a
          port: 8080
```

In such a case, the request `http://mydomain.example.com/admin%2F` will reach the backend `service-a` without operating the middleware `my-security-middleware` and passing the security put in place for the `/admin/` path.

## Patches

- https://github.com/traefik/traefik/releases/tag/v2.11.32
- https://github.com/traefik/traefik/releases/tag/v3.6.4

## For more information

If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).

<details>
<summary>Original Description</summary>### Summary
A vulnerability exists in Traefik’s path matching logic that allows attackers to bypass access-control middleware (e.g., blocking rules) by using URL-encoded paths. I found this vulnerability while playing PwnSec CTF 2025 with my team @0xL4ugh

### Details
Traefik evaluates router rules before decoding or normalizing the request path, but forwards the request after decoding to the backend service. As a result, routes meant to block access to sensitive endpoints (such as internal, beta, or admin endpoints) can be trivially bypassed.

### PoC
Traefik configuration used in this issue :
```[http.routers.flask-router-report-deny]
  entryPoints = ["web"]
  rule = "PathPrefix(`/report_note`)"
  priority = 10
  middlewares = ["block-access"]
  service = "flask-service"

[http.middlewares.block-access.replacePathRegex]
  regex = ".*"
  replacement = "/blocked"
```
The intention is to block all access to /report_note.

However, the following request bypasses the block:
```
POST /%2freport_note HTTP/1.1
Host: localhost:62814


```
### Impact
Access Control Bypass:
Any endpoint intended to be blocked (e.g., admin/debug/beta APIs) can be accessed by URL-encoding slashes or other characters.

This could lead to:

- Unauthorized access to restricted endpoints
- Execution of protected internal functionality
- Potential privilege escalation
- Bypass of security policies enforced via Traefik routing rules
</details>
GitHub Security Advisory: GHSA-gm3x-23wp-hc2c
Package: github.com/traefik/traefik/v2 (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-436: Interpretation Conflict
Vulnerable versions: < 2.11.32
Patched in: 2.11.32

Summary: Path Normalization Bypass in Traefik Router + Middleware Rules

Details:
## Impact

There is a potential vulnerability in Traefik managing the requests using a `PathPrefix`, `Path` or `PathRegex` matcher.

When Traefik is configured to route the requests to a backend using a matcher based on the path; if the request path contains an encoded restricted character from the following set **('/', '\', 'Null', ';', '?', '#')**, it’s possible to target a backend, exposed using another router, by-passing the middlewares chain.

## Example

```yaml
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
metadata:
  name: my-service
spec:
  routes:
    - match: PathPrefix(‘/admin/’)
      kind: Rule
      services:
        - name: service-a
          port: 8080
      middlewares:
        - name: my-security-middleware
    - match: PathPrefix(‘/’)
      kind: Rule
      services:
        - name: service-a
          port: 8080
```

In such a case, the request `http://mydomain.example.com/admin%2F` will reach the backend `service-a` without operating the middleware `my-security-middleware` and passing the security put in place for the `/admin/` path.

## Patches

- https://github.com/traefik/traefik/releases/tag/v2.11.32
- https://github.com/traefik/traefik/releases/tag/v3.6.4

## For more information

If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).

<details>
<summary>Original Description</summary>### Summary
A vulnerability exists in Traefik’s path matching logic that allows attackers to bypass access-control middleware (e.g., blocking rules) by using URL-encoded paths. I found this vulnerability while playing PwnSec CTF 2025 with my team @0xL4ugh

### Details
Traefik evaluates router rules before decoding or normalizing the request path, but forwards the request after decoding to the backend service. As a result, routes meant to block access to sensitive endpoints (such as internal, beta, or admin endpoints) can be trivially bypassed.

### PoC
Traefik configuration used in this issue :
```[http.routers.flask-router-report-deny]
  entryPoints = ["web"]
  rule = "PathPrefix(`/report_note`)"
  priority = 10
  middlewares = ["block-access"]
  service = "flask-service"

[http.middlewares.block-access.replacePathRegex]
  regex = ".*"
  replacement = "/blocked"
```
The intention is to block all access to /report_note.

However, the following request bypasses the block:
```
POST /%2freport_note HTTP/1.1
Host: localhost:62814


```
### Impact
Access Control Bypass:
Any endpoint intended to be blocked (e.g., admin/debug/beta APIs) can be accessed by URL-encoding slashes or other characters.

This could lead to:

- Unauthorized access to restricted endpoints
- Execution of protected internal functionality
- Potential privilege escalation
- Bypass of security policies enforced via Traefik routing rules
</details>
GitHub Security Advisory: GHSA-g754-hx8w-x2g6
Package: github.com/quic-go/quic-go (GO)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: < 0.57.0
Patched in: 0.57.0

Summary: quic-go HTTP/3 QPACK Header Expansion DoS

Details:
## Summary

An attacker can cause excessive memory allocation in quic-go's HTTP/3 client and server implementations by sending a QPACK-encoded HEADERS frame that decodes into a large header field section (many unique header names and/or large values). The implementation builds an `http.Header` (used on the `http.Request` and `http.Response`, respectively), while only enforcing limits on the size of the (QPACK-compressed) HEADERS frame, but not on the decoded header, leading to memory exhaustion.

## Impact

A misbehaving or malicious peer can cause a denial-of-service (DoS) attack on quic-go's HTTP/3 servers or clients by triggering excessive memory allocation, potentially leading to crashes or exhaustion. It affects both servers and clients due to symmetric header construction.

## Details

In HTTP/3, headers are compressed using QPACK (RFC 9204). quic-go's HTTP/3 server (and client) decodes the QPACK-encoded HEADERS frame into header fields, then constructs an http.Request (or response).

`http3.Server.MaxHeaderBytes` and `http3.Transport.MaxResponseHeaderBytes`, respectively, limit encoded HEADERS frame size (default: 1 MB server, 10 MB client), but not decoded size. A maliciously crafted HEADERS frame can expand to ~50x the encoded size using QPACK static table entries with long names / values.

RFC 9114 requires enforcing decoded field section size limits via SETTINGS, which quic-go did not do.

## The Fix

quic-go now enforces RFC 9114 decoded field section size limits, sending SETTINGS_MAX_FIELD_SECTION_SIZE and using incremental QPACK decoding to check the header size after each entry, aborting early on violations with HTTP 431 (on the server side) and stream reset (on the client side).
GitHub Security Advisory: GHSA-cfpf-hrx2-8rv6
Package: github.com/expr-lang/expr (GO)
Severity: HIGH (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: < 1.17.7
Patched in: 1.17.7

Summary: Expr has Denial of Service via Unbounded Recursion in Builtin Functions

Details:
Several builtin functions in Expr, including `flatten`, `min`, `max`, `mean`, and `median`, perform
recursive traversal over user-provided data structures without enforcing a maximum recursion depth.

If the evaluation environment contains **deeply nested** or **cyclic** data structures, these functions may recurse
indefinitely until exceed the Go runtime stack limit. This results in a **stack overflow panic**, causing the host
application to crash.

While exploitability depends on whether an attacker can influence or inject cyclic or pathologically deep data into the
evaluation environment, this behavior represents a denial-of-service (DoS) risk and affects overall library robustness.
Instead of returning a recoverable evaluation error, the process may terminate unexpectedly.

### Impact

In affected versions, evaluation of expressions that invoke certain builtin functions on untrusted or insufficiently
validated data structures can lead to a **process-level crash** due to stack exhaustion.

This issue is most relevant in scenarios where:

* Expr is used to evaluate expressions against externally supplied or dynamically constructed environments.
* Cyclic references (directly or indirectly) can be introduced into arrays, maps, or structs.
* There are no application-level safeguards preventing deeply nested input data.

In typical use cases with controlled, acyclic data, the issue may not manifest. However, when present, the resulting
panic can be used to reliably crash the application, constituting a denial of service.

### Patches

The issue has been fixed in the v1.17.7 versions of Expr.

The patch introduces a **maximum recursion depth limit** for affected builtin functions. When this limit is exceeded,
evaluation aborts gracefully and returns a descriptive error instead of panicking.

Additionally, the maximum depth can be customized by users via `builtin.MaxDepth`, allowing applications with legitimate
deep structures to raise the limit in a controlled manner.

Users are strongly encouraged to upgrade to the patched release, which includes both the recursion guard and
comprehensive test coverage to prevent regressions.

### Workarounds

For users who cannot immediately upgrade, the following mitigations are recommended:

* Ensure that evaluation environments cannot contain cyclic references.
* Validate or sanitize externally supplied data structures before passing them to Expr.
* Wrap expression evaluation with panic recovery to prevent a full process crash (as a last-resort defensive measure).

These workarounds reduce risk but do not fully eliminate the issue without the patch.
GitHub Security Advisory: GHSA-cc8c-28gj-px38
Package: github.com/RedHatInsights/runtimes-inventory-operator (GO)
Severity: HIGH (CVSS 8.7)
CWE: CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')
Vulnerable versions: <= 0.0.0[PII_REDACTED]4[PII_REDACTED]abee1
Patched in: unpatched

Summary: Misconfigured Internal Proxy in runtimes-inventory-rhel8-operator Grants Standard Users Full Cluster Administrator Access

Details:
A flaw was found in runtimes-inventory-rhel8-operator. An internal proxy component is incorrectly configured. Because of this flaw, the proxy attaches the cluster's main administrative credentials to any command it receives, instead of only the specific reports it is supposed to handle.

This allows a standard user within the cluster to send unauthorized commands to the management platform, effectively acting with the full permissions of the cluster administrator. This could lead to unauthorized changes to the cluster's configuration or status on the Red Hat platform.
GitHub Security Advisory: GHSA-58fx-7v9q-3g56
Package: github.com/redhat-developer/gitops-operator (GO)
Severity: HIGH (CVSS 8.2)
CWE: CWE-668: Exposure of Resource to Wrong Sphere
Vulnerable versions: < 1.16.2
Patched in: 1.16.2

Summary: OpenShift GitOps Operator Namespace Isolation Break

Details:
A flaw was found in openshift-gitops-operator-container. The openshift.io/cluster-monitoring label is applied to all namespaces that deploy an ArgoCD CR instance, allowing the namespace to create a rogue PrometheusRule. This issue can have adverse effects on the platform monitoring stack, as the rule is rolled out cluster-wide when the label is applied.