deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-4g87-9x45-cx2h
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: >= 10.5.0, < 10.5.13
Patched in: 10.5.13

Summary: Mattermost fails to sanitize team email addresses

Details:
Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint
GitHub Security Advisory: GHSA-4g87-9x45-cx2h
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: >= 10.11.0, < 10.11.5
Patched in: 10.11.5

Summary: Mattermost fails to sanitize team email addresses

Details:
Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint
GitHub Security Advisory: GHSA-4g87-9x45-cx2h
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: >= 10.12.0, < 10.12.2
Patched in: 10.12.2

Summary: Mattermost fails to sanitize team email addresses

Details:
Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint
GitHub Security Advisory: GHSA-4g87-9x45-cx2h
Package: github.com/mattermost/mattermost-server (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: >= 11.0.0, < 11.0.3
Patched in: 11.0.3

Summary: Mattermost fails to sanitize team email addresses

Details:
Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint
GitHub Security Advisory: GHSA-4g87-9x45-cx2h
Package: github.com/mattermost/mattermost/server/v8 (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: < 8.0.0[PII_REDACTED]1448-abbf01b9db45
Patched in: 8.0.0[PII_REDACTED]1448-abbf01b9db45

Summary: Mattermost fails to sanitize team email addresses

Details:
Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint
GitHub Security Advisory: GHSA-3x39-62h4-f8j6
Package: github.com/mattermost/mattermost-server (GO)
Severity: CRITICAL (CVSS 9.9)
CWE: CWE-287: Improper Authentication, CWE-303: Incorrect Implementation of Authentication Algorithm
Vulnerable versions: >= 11.0.0, < 11.0.4
Patched in: 11.0.4

Summary: Mattermost fails to properly validate OAuth state tokens during OpenID Connect authentication

Details:
Mattermost versions 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12, 11.0.x <= 11.0.3 fail to properly validate OAuth state tokens during OpenID Connect authentication which allows an authenticated attacker with team creation privileges to take over a user account via manipulation of authentication data during the OAuth completion flow. This requires email verification to be disabled (default: disabled), OAuth/OpenID Connect to be enabled, and the attacker to control two users in the SSO system with one of them never having logged into Mattermost.
GitHub Security Advisory: GHSA-3x39-62h4-f8j6
Package: github.com/mattermost/mattermost-server (GO)
Severity: CRITICAL (CVSS 9.9)
CWE: CWE-287: Improper Authentication, CWE-303: Incorrect Implementation of Authentication Algorithm
Vulnerable versions: >= 10.5.0, < 10.5.13
Patched in: 10.5.13

Summary: Mattermost fails to properly validate OAuth state tokens during OpenID Connect authentication

Details:
Mattermost versions 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12, 11.0.x <= 11.0.3 fail to properly validate OAuth state tokens during OpenID Connect authentication which allows an authenticated attacker with team creation privileges to take over a user account via manipulation of authentication data during the OAuth completion flow. This requires email verification to be disabled (default: disabled), OAuth/OpenID Connect to be enabled, and the attacker to control two users in the SSO system with one of them never having logged into Mattermost.
GitHub Security Advisory: GHSA-3x39-62h4-f8j6
Package: github.com/mattermost/mattermost-server (GO)
Severity: CRITICAL (CVSS 9.9)
CWE: CWE-287: Improper Authentication, CWE-303: Incorrect Implementation of Authentication Algorithm
Vulnerable versions: >= 10.11.0, < 10.11.5
Patched in: 10.11.5

Summary: Mattermost fails to properly validate OAuth state tokens during OpenID Connect authentication

Details:
Mattermost versions 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12, 11.0.x <= 11.0.3 fail to properly validate OAuth state tokens during OpenID Connect authentication which allows an authenticated attacker with team creation privileges to take over a user account via manipulation of authentication data during the OAuth completion flow. This requires email verification to be disabled (default: disabled), OAuth/OpenID Connect to be enabled, and the attacker to control two users in the SSO system with one of them never having logged into Mattermost.
GitHub Security Advisory: GHSA-3x39-62h4-f8j6
Package: github.com/mattermost/mattermost-server (GO)
Severity: CRITICAL (CVSS 9.9)
CWE: CWE-287: Improper Authentication, CWE-303: Incorrect Implementation of Authentication Algorithm
Vulnerable versions: >= 10.12.0, < 10.12.2
Patched in: 10.12.2

Summary: Mattermost fails to properly validate OAuth state tokens during OpenID Connect authentication

Details:
Mattermost versions 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12, 11.0.x <= 11.0.3 fail to properly validate OAuth state tokens during OpenID Connect authentication which allows an authenticated attacker with team creation privileges to take over a user account via manipulation of authentication data during the OAuth completion flow. This requires email verification to be disabled (default: disabled), OAuth/OpenID Connect to be enabled, and the attacker to control two users in the SSO system with one of them never having logged into Mattermost.
GitHub Security Advisory: GHSA-3x39-62h4-f8j6
Package: github.com/mattermost/mattermost/server/v8 (GO)
Severity: CRITICAL (CVSS 9.9)
CWE: CWE-287: Improper Authentication, CWE-303: Incorrect Implementation of Authentication Algorithm
Vulnerable versions: < 8.0.0[PII_REDACTED]0919-d3ed703dc833
Patched in: 8.0.0[PII_REDACTED]0919-d3ed703dc833

Summary: Mattermost fails to properly validate OAuth state tokens during OpenID Connect authentication

Details:
Mattermost versions 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12, 11.0.x <= 11.0.3 fail to properly validate OAuth state tokens during OpenID Connect authentication which allows an authenticated attacker with team creation privileges to take over a user account via manipulation of authentication data during the OAuth completion flow. This requires email verification to be disabled (default: disabled), OAuth/OpenID Connect to be enabled, and the attacker to control two users in the SSO system with one of them never having logged into Mattermost.
GitHub Security Advisory: GHSA-38pp-6gcp-rqvm
Package: github.com/cilium/cilium (GO)
Severity: MODERATE (CVSS 4.0)
CWE: CWE-284: Improper Access Control
Vulnerable versions: < 1.16.17
Patched in: 1.16.17

Summary: Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic

Details:
### Impact

`CiliumNetworkPolicy`s which use `egress.toGroups.aws.securityGroupsIds` to reference AWS security group IDs that do not exist or are not attached to any network interface may unintentionally allow broader outbound access than intended by the policy authors. In such cases, the toCIDRset section of the derived policy is not generated, which means outbound traffic may be permitted to more destinations than originally intended.

### Patches

This issue has been patched in:

* Cilium v1.18.4
* Cilium v1.17.10
* Cilium v1.16.17

### This issue affects:

- Cilium v1.18 between v1.18.0 and v1.18.3 inclusive
- Cilium v1.17 between v1.17.0 and v1.17.9 inclusive
- Cilium v1.16.16 and below

### Workarounds

There is no workaround to this issue.

### Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @SeanEmac   for reporting this issue and to @fristonio for the patch.

### For more information

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
GitHub Security Advisory: GHSA-38pp-6gcp-rqvm
Package: Ciliumgithub.com/cilium/cilium (GO)
Severity: MODERATE (CVSS 4.0)
CWE: CWE-284: Improper Access Control
Vulnerable versions: >= 1.17.0, < 1.17.10
Patched in: 1.17.10

Summary: Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic

Details:
### Impact

`CiliumNetworkPolicy`s which use `egress.toGroups.aws.securityGroupsIds` to reference AWS security group IDs that do not exist or are not attached to any network interface may unintentionally allow broader outbound access than intended by the policy authors. In such cases, the toCIDRset section of the derived policy is not generated, which means outbound traffic may be permitted to more destinations than originally intended.

### Patches

This issue has been patched in:

* Cilium v1.18.4
* Cilium v1.17.10
* Cilium v1.16.17

### This issue affects:

- Cilium v1.18 between v1.18.0 and v1.18.3 inclusive
- Cilium v1.17 between v1.17.0 and v1.17.9 inclusive
- Cilium v1.16.16 and below

### Workarounds

There is no workaround to this issue.

### Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @SeanEmac   for reporting this issue and to @fristonio for the patch.

### For more information

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
GitHub Security Advisory: GHSA-38pp-6gcp-rqvm
Package: github.com/cilium/cilium (GO)
Severity: MODERATE (CVSS 4.0)
CWE: CWE-284: Improper Access Control
Vulnerable versions: >= 1.18.0, < 1.18.4
Patched in: 1.18.4

Summary: Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic

Details:
### Impact

`CiliumNetworkPolicy`s which use `egress.toGroups.aws.securityGroupsIds` to reference AWS security group IDs that do not exist or are not attached to any network interface may unintentionally allow broader outbound access than intended by the policy authors. In such cases, the toCIDRset section of the derived policy is not generated, which means outbound traffic may be permitted to more destinations than originally intended.

### Patches

This issue has been patched in:

* Cilium v1.18.4
* Cilium v1.17.10
* Cilium v1.16.17

### This issue affects:

- Cilium v1.18 between v1.18.0 and v1.18.3 inclusive
- Cilium v1.17 between v1.17.0 and v1.17.9 inclusive
- Cilium v1.16.16 and below

### Workarounds

There is no workaround to this issue.

### Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @SeanEmac   for reporting this issue and to @fristonio for the patch.

### For more information

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
GitHub Security Advisory: GHSA-gv8h-7v7w-r22q
Package: github.com/docker/compose/v2 (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-20: Improper Input Validation, CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 2.34.0, < 2.40.2
Patched in: 2.40.2

Summary: Docker Compose Vulnerable to Path Traversal via OCI Artifact Layer Annotations

Details:
Docker Compose trusts the path information embedded in remote OCI compose artifacts. When a layer includes the annotations com.docker.compose.extends or com.docker.compose.envfile, Compose joins the attacker‑supplied value from com.docker.compose.file/com.docker.compose.envfile with its local cache directory and writes the file there. 

### Impact
This affects any platform or workflow that resolves remote OCI compose artifacts, Docker Desktop, standalone Compose binaries on Linux, CI/CD runners, cloud dev environments is affected.
An attacker can escape the cache directory and overwrite arbitrary files on the machine running docker compose, even if the user only runs read‑only commands such as docker compose config or docker compose ps.

### Patches
v2.40.2

### Workarounds
NA
GitHub Security Advisory: GHSA-2c64-vmv2-hgfc
Package: github.com/openfga/openfga (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-285: Improper Authorization
Vulnerable versions: >= 1.4.0, < 1.11.1
Patched in: 1.11.1

Summary: OpenFGA Improper Policy Enforcement

Details:
### Overview
OpenFGA v1.4.0 to v1.11.0  (openfga-0.1.34 <= Helm chart <= openfga-0.2.48, v.1.4.0 <= docker <= v.1.11.0) are vulnerable to improper policy enforcement when certain Check and ListObject calls are executed.

### Am I Affected?
You are affected by this vulnerability if you meet the following preconditions:
- You are using OpenFGA v1.4.0 to v1.11.0
- The model has a a relation directly assignable by a [type bound pubic access](https://openfga.dev/docs/concepts#what-is-type-bound-public-access) with [condition](https://openfga.dev/docs/modeling/conditions)
- The same relation is not assignable by a type bound public access without condition
- You have a type assigned for the same relation that is a type bound public access without condition


### Fix
Upgrade to v1.11.1. This upgrade is backwards compatible.

### Workaround
None
GitHub Security Advisory: GHSA-f2hj-vpp9-6vm2
Package: github.com/free5gc/nssf (GO)
Severity: HIGH (CVSS 7.5)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: < 1.4.0
Patched in: 1.4.0

Summary: NSSF panic due to nil pointer dereference when expiry field is omitted in NSSAIAvailability POST

Details:
An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via crafted POST request to the Nnssf_NSSAIAvailability API.
GitHub Security Advisory: GHSA-3j9f-7w24-pcqg
Package: github.com/free5gc/openapi (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-1287: Improper Validation of Specified Type of Input
Vulnerable versions: < 1.2.2
Patched in: 1.2.2

Summary: Free5GC is vulnerable to DoS via the Nudm_SubscriberDataManagement API

Details:
An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via the Nudm_SubscriberDataManagement API.
GitHub Security Advisory: GHSA-3j9f-7w24-pcqg
Package: github.com/free5gc/udm (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-1287: Improper Validation of Specified Type of Input
Vulnerable versions: <= 1.4.0
Patched in: unpatched

Summary: Free5GC is vulnerable to DoS via the Nudm_SubscriberDataManagement API

Details:
An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via the Nudm_SubscriberDataManagement API.
GitHub Security Advisory: GHSA-vgq7-9r5r-j9v3
Package: github.com/free5gc/pcf (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-617: Reachable Assertion
Vulnerable versions: < 1.4.0
Patched in: 1.4.0

Summary: Free5GC is vulnerable to DoS through its Npcf_BDTPolicyControl POST API

Details:
An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via crafted POST request to the Npcf_BDTPolicyControl API.
GitHub Security Advisory: GHSA-66jq-2c23-2xh5
Package: github.com/VictoriaMetrics/VictoriaMetrics (GO)
Severity: LOW (CVSS 2.7)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 1.0.0, < 1.110.23
Patched in: 1.110.23

Summary: VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOM

Details:
### Impact
Affected versions are vulnerable to DoS attacks because the snappy decoder ignored VictoriaMetrics request size limits allowing malformed blocks to trigger excessive memory use. This could lead to OOM errors and service instability. The fix enforces block-size checks based on MaxRequest limits.

### Patches
Versions 1.129.1, 1.122.8, 1.110.23

### Resources
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.129.1
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.8
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.110.23
 
### Note 
VictoriaMetrics' security model assumes its APIs are properly secured (e.g. via access control flags or a firewall); this advisory addresses malicious input that should not be possible under a [correctly secured](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#security) deployment.
GitHub Security Advisory: GHSA-66jq-2c23-2xh5
Package: github.com/VictoriaMetrics/VictoriaMetrics (GO)
Severity: LOW (CVSS 2.7)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 1.111.0, < 1.122.8
Patched in: 1.122.8

Summary: VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOM

Details:
### Impact
Affected versions are vulnerable to DoS attacks because the snappy decoder ignored VictoriaMetrics request size limits allowing malformed blocks to trigger excessive memory use. This could lead to OOM errors and service instability. The fix enforces block-size checks based on MaxRequest limits.

### Patches
Versions 1.129.1, 1.122.8, 1.110.23

### Resources
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.129.1
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.8
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.110.23
 
### Note 
VictoriaMetrics' security model assumes its APIs are properly secured (e.g. via access control flags or a firewall); this advisory addresses malicious input that should not be possible under a [correctly secured](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#security) deployment.
GitHub Security Advisory: GHSA-66jq-2c23-2xh5
Package: github.com/VictoriaMetrics/VictoriaMetrics (GO)
Severity: LOW (CVSS 2.7)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 1.123.0, < 1.129.1
Patched in: 1.129.1

Summary: VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOM

Details:
### Impact
Affected versions are vulnerable to DoS attacks because the snappy decoder ignored VictoriaMetrics request size limits allowing malformed blocks to trigger excessive memory use. This could lead to OOM errors and service instability. The fix enforces block-size checks based on MaxRequest limits.

### Patches
Versions 1.129.1, 1.122.8, 1.110.23

### Resources
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.129.1
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.8
 - https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.110.23
 
### Note 
VictoriaMetrics' security model assumes its APIs are properly secured (e.g. via access control flags or a firewall); this advisory addresses malicious input that should not be possible under a [correctly secured](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#security) deployment.
GitHub Security Advisory: GHSA-6gxw-85q2-q646
Package: github.com/anchore/grype (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer
Vulnerable versions: >= 0.68.0, < 0.104.1
Patched in: 0.104.1

Summary: Grype has a credential disclosure vulnerability in its JSON output

Details:
A credential disclosure vulnerability was found in Grype, affecting versions `v0.68.0` through `v0.104.0`. If registry credentials are defined and the output of grype is written using the `--file` or `--output json=<file>` option, the registry credentials will be included unsanitized in the output file.

## Impact

In Grype versions `v0.68.0` through `v0.104.0`, when registry authentication is configured, those credentials can be incorrectly included in the output of a Grype scan (regardless of whether those credentials are actively being used for the current scan). Users that do not have registry authentication configured are not affected by this issue.

Registry credentials can be set via the Grype configuration file (e.g. `registry.auth[].username`, `registry.auth[].password`, `registry.auth[].token`) or environment variables (e.g., `GRYPE_REGISTRY_AUTH_USERNAME`, `GRYPE_REGISTRY_AUTH_PASSWORD`, `GRYPE_REGISTRY_AUTH_TOKEN`).

In order for the authentication details to be improperly included, the Grype file output format must be set to `json` with output target set to a file. For example `--output json=file.json` or `--output json --file file.json`. When these conditions are met, the configured credentials are not sanitized as they should be in the resulting JSON output file.

The authentication details could also be leaked via a malformed Grype Template. A Grype Template that includes the `Descriptor.Registry.Auth` fields would also include the unsanitized registry credentials. There are no known templates that include these fields.

## Patches
The patch has been released in `v0.104.1`.

## Workaround
Users running affected versions of grype can work around this vulnerability by redirecting stdout to a file instead of using the `--file` or `--output` options.

For example, replacing the command:

```
# using `--output json=path` (or `--file`) leaks credentials
grype --output json=test.json alpine:latest
```

with

```
# no use of `--output json=path` or `--file`. Output is sanitized...
grype --output json alpine:latest > test.json
```

...results in the same `test.json` output, but the credentials will be properly sanitized.

## Resources
Patch pull request: https://github.com/anchore/grype/pull/3068
GitHub Security Advisory: GHSA-xq4h-wqm2-668w
Package: github.com/babylonlabs-io/babylon/v4 (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-347: Improper Verification of Cryptographic Signature
Vulnerable versions: < 4.1.0
Patched in: 4.1.0

Summary: Babylon's BIP322 signature implementation is not fully compliant to the spec

Details:
### Summary

The BIP-322 signature verification does not enforce the SIGHASH value to be SIGHASH_ALL, and therefore is not strictly following the [spec](https://bips.dev/322/).

### Impact

Non-compliant BIP-322 signatures in proof of possessions can be accepted by the chain.