deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-7wfc-4796-gmg5
Package: github.com/zitadel/zitadel/v2 (GO)
Severity: CRITICAL (CVSS 9.3)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: < 1.80.0-v2.20.0[PII_REDACTED]1519-4c879b47334e
Patched in: 1.80.0-v2.20.0[PII_REDACTED]1519-4c879b47334e

Summary: ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login

Details:
### Summary

Zitadel is vulnerable to an unauthenticated, full-read SSRF vulnerability. An unauthenticated remote attacker can force Zitadel into making HTTP requests to arbitrary domains, including internal addresses. The server then returns the upstream response to the attacker, enabling data exfiltration from internal services.

### Impact

ZITADEL Login UI (V2) was vulnerable to service URL manipulation through the x-zitadel-forward-host header. The service URL resolution logic treated the header as a trusted fallback for all deployments, including self-hosted instances. This allowed unauthenticated attacker to force the server to make outbound requests and read the responses, reaching internal services, exfiltrating data, and bypassing IP-based or network-segmentation controls. 
 
### Affected Versions

Systems using the login UI (v2) and running one of the following versions are affected:
- **v4.x**: `4.0.0-rc.1` through `4.7.0`

### Patches

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the x-zitadel-forward-host, resp. all forwarded headers against the instance domains and trusted domains. It's no longer used to route traffic to the Zitadel API.

Before you upgrade, ensure that:
- the `ZITADEL_API_URL` is set and is pointing to your instance, resp. system in multi-instance deployments.
- the HTTP `host` (or a `x-forwarded-host`) is passed in your reverse proxy to the login UI.
- a `x-zitadel-instance-host` (or `x-zitadel-forward-host`) is set in your reverse for multi-instance deployments. If you're running a single instance solution, you don't need to take any actions.

Fixed versions:
- 4.x: Upgrade to >=[4.7.1](https://github.com/zitadel/zitadel/releases/tag/v4.7.1)

### Workarounds

The recommended solution is to update ZITADEL to a patched version.

A ZITADEL fronting proxy can be configured to delete all `x-zitadel-forward-host` header values or set it to the requested host before sending requests to ZITADEL self-hosted environments.

### Questions

If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)

### Credits

Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
GitHub Security Advisory: GHSA-7wfc-4796-gmg5
Package: github.com/zitadel/zitadel (GO)
Severity: CRITICAL (CVSS 9.3)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: >= 4.0.0-rc.1, < 4.7.1
Patched in: 4.7.1

Summary: ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login

Details:
### Summary

Zitadel is vulnerable to an unauthenticated, full-read SSRF vulnerability. An unauthenticated remote attacker can force Zitadel into making HTTP requests to arbitrary domains, including internal addresses. The server then returns the upstream response to the attacker, enabling data exfiltration from internal services.

### Impact

ZITADEL Login UI (V2) was vulnerable to service URL manipulation through the x-zitadel-forward-host header. The service URL resolution logic treated the header as a trusted fallback for all deployments, including self-hosted instances. This allowed unauthenticated attacker to force the server to make outbound requests and read the responses, reaching internal services, exfiltrating data, and bypassing IP-based or network-segmentation controls. 
 
### Affected Versions

Systems using the login UI (v2) and running one of the following versions are affected:
- **v4.x**: `4.0.0-rc.1` through `4.7.0`

### Patches

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the x-zitadel-forward-host, resp. all forwarded headers against the instance domains and trusted domains. It's no longer used to route traffic to the Zitadel API.

Before you upgrade, ensure that:
- the `ZITADEL_API_URL` is set and is pointing to your instance, resp. system in multi-instance deployments.
- the HTTP `host` (or a `x-forwarded-host`) is passed in your reverse proxy to the login UI.
- a `x-zitadel-instance-host` (or `x-zitadel-forward-host`) is set in your reverse for multi-instance deployments. If you're running a single instance solution, you don't need to take any actions.

Fixed versions:
- 4.x: Upgrade to >=[4.7.1](https://github.com/zitadel/zitadel/releases/tag/v4.7.1)

### Workarounds

The recommended solution is to update ZITADEL to a patched version.

A ZITADEL fronting proxy can be configured to delete all `x-zitadel-forward-host` header values or set it to the requested host before sending requests to ZITADEL self-hosted environments.

### Questions

If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)

### Credits

Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
GitHub Security Advisory: GHSA-7wfc-4796-gmg5
Package: github.com/zitadel/zitadel (GO)
Severity: CRITICAL (CVSS 9.3)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: >= 1.83.4, <= 1.87.5
Patched in: unpatched

Summary: ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login

Details:
### Summary

Zitadel is vulnerable to an unauthenticated, full-read SSRF vulnerability. An unauthenticated remote attacker can force Zitadel into making HTTP requests to arbitrary domains, including internal addresses. The server then returns the upstream response to the attacker, enabling data exfiltration from internal services.

### Impact

ZITADEL Login UI (V2) was vulnerable to service URL manipulation through the x-zitadel-forward-host header. The service URL resolution logic treated the header as a trusted fallback for all deployments, including self-hosted instances. This allowed unauthenticated attacker to force the server to make outbound requests and read the responses, reaching internal services, exfiltrating data, and bypassing IP-based or network-segmentation controls. 
 
### Affected Versions

Systems using the login UI (v2) and running one of the following versions are affected:
- **v4.x**: `4.0.0-rc.1` through `4.7.0`

### Patches

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the x-zitadel-forward-host, resp. all forwarded headers against the instance domains and trusted domains. It's no longer used to route traffic to the Zitadel API.

Before you upgrade, ensure that:
- the `ZITADEL_API_URL` is set and is pointing to your instance, resp. system in multi-instance deployments.
- the HTTP `host` (or a `x-forwarded-host`) is passed in your reverse proxy to the login UI.
- a `x-zitadel-instance-host` (or `x-zitadel-forward-host`) is set in your reverse for multi-instance deployments. If you're running a single instance solution, you don't need to take any actions.

Fixed versions:
- 4.x: Upgrade to >=[4.7.1](https://github.com/zitadel/zitadel/releases/tag/v4.7.1)

### Workarounds

The recommended solution is to update ZITADEL to a patched version.

A ZITADEL fronting proxy can be configured to delete all `x-zitadel-forward-host` header values or set it to the requested host before sending requests to ZITADEL self-hosted environments.

### Questions

If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)

### Credits

Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
GitHub Security Advisory: GHSA-7wfc-4796-gmg5
Package: github.com/zitadel/zitadel (GO)
Severity: CRITICAL (CVSS 9.3)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: < 1.80.0-v2.20.0[PII_REDACTED]1519-4c879b47334e
Patched in: 1.80.0-v2.20.0[PII_REDACTED]1519-4c879b47334e

Summary: ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login

Details:
### Summary

Zitadel is vulnerable to an unauthenticated, full-read SSRF vulnerability. An unauthenticated remote attacker can force Zitadel into making HTTP requests to arbitrary domains, including internal addresses. The server then returns the upstream response to the attacker, enabling data exfiltration from internal services.

### Impact

ZITADEL Login UI (V2) was vulnerable to service URL manipulation through the x-zitadel-forward-host header. The service URL resolution logic treated the header as a trusted fallback for all deployments, including self-hosted instances. This allowed unauthenticated attacker to force the server to make outbound requests and read the responses, reaching internal services, exfiltrating data, and bypassing IP-based or network-segmentation controls. 
 
### Affected Versions

Systems using the login UI (v2) and running one of the following versions are affected:
- **v4.x**: `4.0.0-rc.1` through `4.7.0`

### Patches

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the x-zitadel-forward-host, resp. all forwarded headers against the instance domains and trusted domains. It's no longer used to route traffic to the Zitadel API.

Before you upgrade, ensure that:
- the `ZITADEL_API_URL` is set and is pointing to your instance, resp. system in multi-instance deployments.
- the HTTP `host` (or a `x-forwarded-host`) is passed in your reverse proxy to the login UI.
- a `x-zitadel-instance-host` (or `x-zitadel-forward-host`) is set in your reverse for multi-instance deployments. If you're running a single instance solution, you don't need to take any actions.

Fixed versions:
- 4.x: Upgrade to >=[4.7.1](https://github.com/zitadel/zitadel/releases/tag/v4.7.1)

### Workarounds

The recommended solution is to update ZITADEL to a patched version.

A ZITADEL fronting proxy can be configured to delete all `x-zitadel-forward-host` header values or set it to the requested host before sending requests to ZITADEL self-hosted environments.

### Questions

If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)

### Credits

Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
GitHub Security Advisory: GHSA-7cqv-qcq2-r765
Package: github.com/1Panel-dev/1Panel/agent (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: < 0.0.0[PII_REDACTED]3338-94f7d78cc976
Patched in: 0.0.0[PII_REDACTED]3338-94f7d78cc976

Summary: 1Panel IP Access Control Bypass via Untrusted X-Forwarded-For Headers

Details:
### Summary
The server trusts all reverse-proxy headers by default, so any remote client can spoof `X-Forwarded-For` to bypass IP-based protections (AllowIPs, API IP whitelist, “localhost-only” checks). All IP-based access control becomes ineffective.

### Details
- Gin is created with defaults (`gin.Default()`), which sets `TrustedProxies = 0.0.0.0/0` and uses `X-Forwarded-For`/`X-Real-IP` to compute `ClientIP()`.

- IP-based controls rely on `ClientIP()`:
    - AllowIPs / BindDomain (core/middleware/ip_limit.go, core/utils/security/security.go).
    - API IP whitelist (core/middleware/api_auth.go).
    - "localhost-only" checks that depend on `ClientIP()`.

- Because no trusted-proxy range is enforced, any client can send `X-Forwarded-For: 127.0.0.1` (or a whitelisted IP) and be treated as coming from that address.

### Impact
All IP-based access control is rendered ineffective: remote clients can masquerade as localhost or any whitelisted IP, defeating AllowIPs, API IP whitelists, and “localhost-only” protections.
GitHub Security Advisory: GHSA-7cqv-qcq2-r765
Package: github.com/1Panel-dev/1Panel (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: < 2.0.14
Patched in: 2.0.14

Summary: 1Panel IP Access Control Bypass via Untrusted X-Forwarded-For Headers

Details:
### Summary
The server trusts all reverse-proxy headers by default, so any remote client can spoof `X-Forwarded-For` to bypass IP-based protections (AllowIPs, API IP whitelist, “localhost-only” checks). All IP-based access control becomes ineffective.

### Details
- Gin is created with defaults (`gin.Default()`), which sets `TrustedProxies = 0.0.0.0/0` and uses `X-Forwarded-For`/`X-Real-IP` to compute `ClientIP()`.

- IP-based controls rely on `ClientIP()`:
    - AllowIPs / BindDomain (core/middleware/ip_limit.go, core/utils/security/security.go).
    - API IP whitelist (core/middleware/api_auth.go).
    - "localhost-only" checks that depend on `ClientIP()`.

- Because no trusted-proxy range is enforced, any client can send `X-Forwarded-For: 127.0.0.1` (or a whitelisted IP) and be treated as coming from that address.

### Impact
All IP-based access control is rendered ineffective: remote clients can masquerade as localhost or any whitelisted IP, defeating AllowIPs, API IP whitelists, and “localhost-only” protections.
GitHub Security Advisory: GHSA-qmg5-v42x-qqhq
Package: github.com/1Panel-dev/1Panel/core (GO)
Severity: HIGH (CVSS 7.5)
CWE: CWE-290: Authentication Bypass by Spoofing, CWE-602: Client-Side Enforcement of Server-Side Security, CWE-807: Reliance on Untrusted Inputs in a Security Decision
Vulnerable versions: < 0.0.0[PII_REDACTED]0527-ac43f00273be
Patched in: 0.0.0[PII_REDACTED]0527-ac43f00273be

Summary: 1Panel – CAPTCHA Bypass via Client-Controlled Flag 

Details:
### Summary

A CAPTCHA bypass vulnerability in the 1Panel authentication API allows an unauthenticated attacker to disable CAPTCHA verification by abusing a client-controlled parameter. Because the server previously trusted this value without proper validation, CAPTCHA protections could be bypassed, enabling automated login attempts and significantly increasing the risk of account takeover (ATO).

### Details

The /api/login endpoint accepts a boolean field named ignoreCaptcha directly from the client request body:

`"ignoreCaptcha": true`


The backend implementation uses this value to determine whether CAPTCHA validation should be performed:

```
if !req.IgnoreCaptcha {
    if errMsg := captcha.VerifyCode(req.CaptchaID, req.Captcha); errMsg != "" {
        helper.BadAuth(c, errMsg, nil)
        return
    }
}

```

Because req.IgnoreCaptcha is taken directly from user input—with no server-side validation, no session binding, and no privilege checks—any unauthenticated attacker can force CAPTCHA validation to be skipped.

There are no additional conditions, such as:

no requirement for MFA

no trusted device

no IP reputation checks

no prior valid session

no rate limiting

This results in CAPTCHA being entirely client-controlled, which violates fundamental authentication and anti-automation security assumptions.
GitHub Security Advisory: GHSA-qmg5-v42x-qqhq
Package: github.com/1Panel-dev/1Panel (GO)
Severity: HIGH (CVSS 7.5)
CWE: CWE-290: Authentication Bypass by Spoofing, CWE-602: Client-Side Enforcement of Server-Side Security, CWE-807: Reliance on Untrusted Inputs in a Security Decision
Vulnerable versions: < 2.0.14
Patched in: 2.0.14

Summary: 1Panel – CAPTCHA Bypass via Client-Controlled Flag 

Details:
### Summary

A CAPTCHA bypass vulnerability in the 1Panel authentication API allows an unauthenticated attacker to disable CAPTCHA verification by abusing a client-controlled parameter. Because the server previously trusted this value without proper validation, CAPTCHA protections could be bypassed, enabling automated login attempts and significantly increasing the risk of account takeover (ATO).

### Details

The /api/login endpoint accepts a boolean field named ignoreCaptcha directly from the client request body:

`"ignoreCaptcha": true`


The backend implementation uses this value to determine whether CAPTCHA validation should be performed:

```
if !req.IgnoreCaptcha {
    if errMsg := captcha.VerifyCode(req.CaptchaID, req.Captcha); errMsg != "" {
        helper.BadAuth(c, errMsg, nil)
        return
    }
}

```

Because req.IgnoreCaptcha is taken directly from user input—with no server-side validation, no session binding, and no privilege checks—any unauthenticated attacker can force CAPTCHA validation to be skipped.

There are no additional conditions, such as:

no requirement for MFA

no trusted device

no IP reputation checks

no prior valid session

no rate limiting

This results in CAPTCHA being entirely client-controlled, which violates fundamental authentication and anti-automation security assumptions.
GitHub Security Advisory: GHSA-gm3x-23wp-hc2c
Package: github.com/traefik/traefik (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-436: Interpretation Conflict
Vulnerable versions: <= 1.7.34
Patched in: unpatched

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-m497-hq5x-6jcv
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: >= 4.3.0-rc1, < 4.3.0
Patched in: 4.3.0

Summary: Mattermost Server allows attackers to create buttons that can launch API requests

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows an attacker to create a button that, when pressed by a user, launches an API request.
GitHub Security Advisory: GHSA-m497-hq5x-6jcv
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: >= 4.2.0-rc1, < 4.2.1
Patched in: 4.2.1

Summary: Mattermost Server allows attackers to create buttons that can launch API requests

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows an attacker to create a button that, when pressed by a user, launches an API request.
GitHub Security Advisory: GHSA-m497-hq5x-6jcv
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: < 4.1.2
Patched in: 4.1.2

Summary: Mattermost Server allows attackers to create buttons that can launch API requests

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows an attacker to create a button that, when pressed by a user, launches an API request.
GitHub Security Advisory: GHSA-jp57-4x34-5v94
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: >= 4.3.0-rc1, < 4.3.0
Patched in: 4.3.0

Summary: Mattermost Server is vulnerable to webhook and slash command manipulation

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. An attacker could create fictive system-message posts via webhooks and slash commands, in the v3 or v4 REST API.
GitHub Security Advisory: GHSA-jp57-4x34-5v94
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: >= 4.2.0-rc1, < 4.2.1
Patched in: 4.2.1

Summary: Mattermost Server is vulnerable to webhook and slash command manipulation

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. An attacker could create fictive system-message posts via webhooks and slash commands, in the v3 or v4 REST API.
GitHub Security Advisory: GHSA-jp57-4x34-5v94
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: < 4.1.2
Patched in: 4.1.2

Summary: Mattermost Server is vulnerable to webhook and slash command manipulation

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. An attacker could create fictive system-message posts via webhooks and slash commands, in the v3 or v4 REST API.
GitHub Security Advisory: GHSA-v2vm-hq26-5jv6
Package: github.com/mattermost/mattermost-server (GO)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: >= 4.3.0-rc1, < 4.3.0
Patched in: 4.3.0

Summary: Mattermost Server is vulnerable to SQL Injection when executing multiple POST requests

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows SQL injection during the fetching of multiple posts.
GitHub Security Advisory: GHSA-v2vm-hq26-5jv6
Package: github.com/mattermost/mattermost-server (GO)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: >= 4.2.0-rc1, < 4.2.1
Patched in: 4.2.1

Summary: Mattermost Server is vulnerable to SQL Injection when executing multiple POST requests

Details:
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows SQL injection during the fetching of multiple posts.