MCUboot Injection attack of unprotected TLV values in github.com/mcu-tools/mcuboot

Gogs has a Denial of Service in repository/wiki file listing web pages in gogs.io/gogs.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: gogs.io/gogs before v0.14.3.

Pocket ID: OIDC authorization code validation uses AND instead of OR, allowing cross-client token exchange in github.com/pocket-id/pocket-id/backend

Romeo is vulnerable to Archive Slip due to missing checks in sanitization in github.com/ctfer-io/romeo/webserver

Kite Kubernetes proxy path traversal allows authenticated users to bypass RBAC and read cluster-wide resources in github.com/zxh326/kite

Session data is stored using permissive permissions, allowing local users with filesystem access to read arbitrary data.

Due to support of Gzip compression in request bodies, as well as a lack of limiting response body sizes, a malicious server can cause a client to consume a significant amount of system resources, which may be used as a denial of service vector.

Mailpit is Vulnerable to Server-Side Request Forgery (SSRF) via Link Check API in github.com/axllent/mailpit

Mattermost Server: Insufficient Password-Reset Link Invalidation in github.com/mattermost/mattermost-server

Authelia Missing Username Canonicalization in Basic Auth (LDAP) in github.com/authelia/authelia

An issue in the AST parser of Open Policy Agent makes it possible for attackers to cause a Denial of Service attack from a crafted input.

Apache ServiceComb Service-Center Server-Side Request Forgery vulnerability in github.com/apache/servicecomb-service-center.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/apache/servicecomb-service-center before v2.2.0.

Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption in github.com/fission/fission

mo has a XSS via inline SVG script tags in Markdown rendering in github.com/k1LoW/mo

QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth.

With fix, connections now consistently reject messages larger than 65KiB in size.

Dalfox Server Mode has an Unauthenticated Arbitrary File Create/Append via `output` Option in github.com/hahwul/dalfox

Gotenberg's ExifTool group-prefix syntax bypasses dangerous-tag blocklist in github.com/gotenberg/gotenberg

Ambiguous OCI manifest parsing in github.com/containerd/containerd

Amazon S3 Encryption Client has a Key Commitment Issue in github.com/aws/amazon-s3-encryption-client-go

Grafana: Users outside an organization can delete a snapshot with its key in github.com/grafana/grafana.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/grafana/grafana from v9.5.0 before v9.5.18, from v10.0.0 before v10.0.13, from v10.1.0 before v10.1.9, from v10.2.0 before v10.2.6, from v10.3.0 before v10.3.5.

AnyCable: Pusher REST API Does Not Verify Request Body MD5 Enabling Signed-Request Replay with Arbitrary Body in github.com/anycable/anycable-go.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/anycable/anycable-go before v1.6.15.

slsa-verifier vulnerable to mproper validation of npm's publish attestations in github.com/slsa-framework/slsa-verifier

Mattermost doesn't sanitize FileInfo.Name received from federated peers during shared channel file sync in github.com/mattermost/mattermost-server

Komari vulnerable to 2FA Authentication Bypass in github.com/komari-monitor/komari

Nezha has cross-site GET request that can trigger stored cron commands on a victim's agents in github.com/nezhahq/nezha.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/nezhahq/nezha before v2.0.14.

Hashicorp Nomad Incorrect Privilege Assignment vulnerability in github.com/hashicorp/nomad

Mattermost Confluence plugin doesn't properly escape user-controlled display names in HTML template rendering in github.com/mattermost/mattermost-plugin-confluence

Recursive repository cloning can leak authentication tokens to non-GitHub submodule hosts in github.com/cli/cli

Grype has a credential disclosure vulnerability in its JSON output in github.com/anchore/grype

SiYuan: getUniqueFilename passes an unvalidated client-supplied path to the filesystem, giving anonymous readers an existence oracle over the entire host filesystem in github.com/siyuan-note/siyuan/kernel

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

Credential disclosure in syft when SYFT_ATTEST_PASSWORD environment variable set in github.com/anchore/syft

Guest user can discover active public channels in github.com/mattermost/mattermost-server

Ory Kratos has a SQL injection via forged pagination tokens in github.com/ory/kratos

GoBGP has a panic in AdjRib.Update via malformed BGP Update message (Nil Pointer Dereference) in github.com/osrg/gobgp

Path traversal via crafted vulnerability database or other downloaded artifacts in github.com/aquasecurity/trivy

act: actions/cache server allows malicious cache injection in github.com/nektos/act

ZITADEL has 1-Click Account Takeover via XSS in /saml-post Endpoint in github.com/zitadel/zitadel.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/zitadel/zitadel from v4.0.0 before v4.12.0.

# Summary

In the threshold signature scheme, participants start by dividing secrets into shares using a secret sharing scheme. The Verifiable Secret Sharing scheme generates shares from the user’s IDs but does not properly validate them. Using a malicious ID will make other users reveal their secrets during the secret-sharing procedure. In addition, a second issue resulting from lack of validation could cause nodes to crash when sent maliciously formed user IDs.

# Details

The creation of Parties IDs does not properly validate for maliciously chosen IDs. Parties generate the secret shares in `binance-chain/tss-lib` codebase that `keep-network/keep-ecdsa` uses by evaluating the polynomial with the other parties’ IDs. It is critical that these party ids are non-zero because evaluating the polynomial at point 0 reveals the secret.

There is a check that these ids are not zero, but this is insufficient since it is not performed modulo the curve order. Therefore, one can set their ID equal to the order of the elliptic curve, which equals 0 during the polynomial evaluation modulo the curve order.
```
    shares := make(Shares, num)
    for i := 0; i < num; i++ {
        if indexes[i].Cmp(big.NewInt(0)) == 0 {
            return nil, nil, fmt.Errorf("party index should not be 0")
        }
        share := evaluatePolynomial(ec, threshold, poly, indexes[i])
        shares[i] = &Share{Threshold: threshold, ID: indexes[i], Share: share}
    }
```
(https://github.com/binance-chain/tss-lib/blob/73560daec7f83d7355107ea9b5e59d16de8765be/crypto/vss/feldman_vss.go#L64-L70)

Thus, a party with an ID equal to the order of the curve will receive the secret key as its share.

Another issue with the tss-lib implementation was the lack of verification for modularly equal user IDs that can cause nodes to crash during key generation or resharing.

# Timeline

### 6 December 2021, 20:28 CET
The team is informed by Trail of Bits about the issue in `binance-chain/tss-lib`. The vulnerability was already disclosed with Binance and they have implemented fixes in their recent commits. We are advised to update our dependency to the most recent `binance-chain/tss-lib` version.

### 7 December 2021, 9:10 CET
The team confirms with Trail of Bits we started the work on a fix.

### 7 December 2021, 20:03 CET
The team informs Trail of Bits that we found a potential problem in Binance's fix that may lead to the signing code failing with Go panic. We identified the problematic line and suggested its removal.

To address the vulnerability in the protocol, it is required to ensure that:
- all indexes are non-zero,
- all indexes are non-zero modulo the curve order,
- all indexes are unique modulo the curve order.

The first two are guarded in `CheckIndexes` function by:
```
vMod := new(big.Int).Mod(v, ec.Params().N)
if vMod.Cmp(zero) == 0 {
  return nil, errors.New("party index should not be 0")
}
```
The last one is guarded by:
```
if sortutil.Dedupe(sortutil.BigIntSlice(dup)) < len(indexes) {
  return nil, errors.New("duplicate in indexes")
}
```
However, `CheckIndexes` was additionally modified to update values of passed indexes by doing `indexes[i] = vMod`.

This line was not backward-compatible and caused signatures to fail with `panic: runtime error: invalid memory address or nil pointer dereference` in case the signing group was generated with at least one `PartyID.Key` higher than `ec.Params().N`. This would also be problematic for new code that constructs such `PartyID` - we tested that key generation completed successfully but signing failed with the mentioned panic.

### 8 December 2021, 12:49 CET
Trail of Bits confirmed the line we flagged is not critical to the security of the protocol.

### 8 December 2021, 15:29 CET
The team informed Trail of Bits we are planning to open a PR to `binance-chain/tss-lib` with a fix and we suggest extending the embargo for communicating this issue for one more week, until Friday, Dec 17h to give everyone more time update their code given the problem was found. We also ask Trail of Bits to get in touch with Binance to review our fix given that we are not going to provide a sufficient explanation in the commit and PR description to do not threaten the security of projects that have already upgraded their dependency.

### 8 December 2021, 18:17 CET

The team informs Trail of Bits about opening a PR https://github.com/binance-chain/tss-lib/pull/155 and explains all the details of the issue.

The problematic scenario is:

1. We start the keygen by creating `PartyID` for each member. The `PartyID` struct has `Id` and `Key` fields. We set `PartyID.Key` that is higher than the elliptic curve's `N`.
2. This goes to tss-lib which starts the round 1 code (`ecdsa/keygen/round_1.go`). It takes `PartyID.Key` of each member and assembles the `ids` slice. This slice is thrown into `CheckIndexes` which overwrites each element by doing the modulo `N`.
3. After returning from `CheckIndexes` the modified `ids` slice is used to set the `Ks` slice in the final `LocalPartySaveData` which is received by each group member as keygen final result.
4. Each member takes this `LocalPartySaveData` and saves it on disk.
5. Upon signing, we do the same as in point 1, so we construct `PartyID`s in the same way and start the protocol. At this point, `PartyID.Key` is higher than curve's `N`.
6. Before starting round 1 of signing, `LocalPartySaveData` obtained at keygen and our `PartyID`s built at point 5 are used in `BuildLocalSaveDataSubset` to build a new `LocalPartySaveData` instance.
7. `BuildLocalSaveDataSubset` is the place where things go wrong because `Key` field of each `PartyID` from point 5 doesn't correspond to encoded `Ks` elements of `LocalPartySaveData` obtained after keygen, the final `LocalPartySaveData` is corrupted, and cause panic upon validation before signing round 1.

### 8 December 2021, 21:50 CET

Trail of Bits confirms they are going to followup with Binance and they agree to extend the embargo by a week.

### 8 December 2021, 15:16 CET

Trail of Bits validates the problematic scenario we described and our fix. Trail of Bits reaches to Binance and recommends merging our fix and in addition to some other fixes that would secure the code to do not panic even if `LocalPartySaveData` has corrupted data.

### 10 December 2021, 8:16 CET

Binance merges our fix https://github.com/binance-chain/tss-lib/commit/cd95cee01ea2af6d4aa8316612803be944d5369a

### 13 December 2021, 8:35 CET

Binance applies more fixes so that even in case of `LocalPartySaveData` corrupted, the code is not going to panic.

### 15 December 2021

The team releases a new version of the client, v1.8.1, and announces the need for an upgrade.
https://github.com/keep-network/keep-ecdsa/releases/tag/v1.8.1

Traefik: ForwardAuth identity spoofing via dot-form header alias in github.com/traefik/traefik

The package does not validate the ACS Location URI according to the SAML binding being parsed. If abused, this flaw allows attackers to register malicious Service Providers at the IdP and inject Javascript in the ACS endpoint definition, achieving Cross-Site-Scripting (XSS) in the IdP context during the redirection at the end of a SAML SSO Flow. Consequently, an attacker may perform any authenticated action as the victim once the victim's browser loads the SAML IdP initiated SSO link for the malicious service provider.

Authenticate method auth bypass in github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension

listmonk's active sessions remain valid after password reset and password change in github.com/knadh/listmonk

Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs in github.com/fleetdm/fleet

The go-jose package is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service.

Mattermost Fails to Enforce MFA on Plugin Endpoints in github.com/mattermost/mattermost-server

goshs: File-based .goshs ACL authorization bypass via the ?bulk zip-download route (unauthenticated read; residual of GHSA-wvhv-qcqf-f3cx) in github.com/patrickhener/goshs

Buildkite Elastic CI for AWS time-of-check-time-of-use race condition vulnerability in github.com/buildkite/elastic-ci-stack-for-aws

### Impact
_What kind of vulnerability is it? Who is impacted?_

The Karmada components deployed with `karmadactl`, `karma-operator`, and `helm chart` take Golang default cipher suites as part of the TLS protocol, which includes the insecure algorithm. Referring to https://github.com/golang/go/issues/41476#issuecomment-694914728, the 3DES algorithm vulnerability is very unlikely to be attacked. However, to address the concerns and to avoid being disturbed by the security scanner, Karmada has decided to limit the cipher suites to exclude the insecure 3DES algorithm and accordingly release this security advisory.

The components affected are：
- karmada-apiserver
- karmada-aggregated-apiserver
- karmada-search
- karmada-metrics-adapter
- etcd

### Patches
_Has the problem been patched? What versions should users upgrade to?_

From Karmada v1.8.0, when deploying Karmada with `karmadactl`, `karma-operator`, and `helm chart`, the default minimum TLS version of components(include `karmada-apiserver`, `karmada-aggregated-apiserver`, `karmada-search`, and `karmada-metrics-adapter`) would be set to `TLS1.3` to get rid of the insecure algorithm, and set default cipher suites(`TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305`) for `etcd`.

### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_

By setting the `--tls-min-version` for the affected components to TLS 1.3, or explicitly setting the `--cipher-suites` to secure algorithms.

### References
_Are there any links users can visit to find out more?_

1. Enhancements made from the Karmada community: https://github.com/karmada-io/karmada/issues/4191
2. Impact discussions from the Golang community: https://github.com/golang/go/issues/41476

Kratos has a Confused Deputy issue in github.com/go-kratos/kratos

Focalboard doesn't validate file ownership when serving uploaded files in github.com/mattermost/focalboard

WebSocket endpoint `/api/v2/ws/logs` reachable without authentication even when --auth is enabled in github.com/SpectoLabs/hoverfly

HTTP/3 QPACK Header Expansion DoS in github.com/quic-go/quic-go

Terraform WinDNS Provider improperly sanitizes input variables in `windns_record` in github.com/nrkno/terraform-provider-windns

Kubernetes allows bypassing mountable secrets policy imposed by the ServiceAccount admission plugin in k8s.io/kubernetes

A malicious peer can cause a syncing node to panic during blocksync. The syncing node may enter into a catastrophic invalid syncing state or get stuck in blocksync mode, never switching to consensus. Nodes that are vulnerable to this state may experience a Denial of Service condition in which syncing will not work as expected when joining a network as a client.

HashiCorp Vault improper configuration of multi factor authentication in github.com/hashicorp/vault

Answer Insufficient Session Expiration vulnerability in github.com/answerdev/answer

NATS has mTLS verify_and_map authentication bypass via incorrect Subject DN matching in github.com/nats-io/nats-server

### Impact

Authorized clients, having an `inject_processor` secret, could brute-force the secret token value by abusing the `fmt` parameter to the `Proxy-Tokenizer` header.

### Patches

This was fixed in https://github.com/superfly/tokenizer/pull/8 and further mitigated in https://github.com/superfly/tokenizer/pull/9.

usememos/memos has Insufficient Granularity of Access Control in github.com/usememos/memos

frp: Unauthenticated Remote Denial of Service in the frp SSH Tunnel Gateway via Integer Overflow in github.com/fatedier/frp

CVE-2024-46455 in github.com/Unstructured-IO/unstructured

Argo Workflows Controller: Denial of Service via malicious daemon Workflows in github.com/argoproj/argo-workflows

Sealed Secrets for Kubernetes: Rotate API Allows Scope Widening from Strict/Namespace-Wide to Cluster-Wide via Untrusted Template Annotations in github.com/bitnami-labs/sealed-secrets

Out of memory crash from malicious Helm registry in github.com/argoproj/argo-cd/v2

HashiCorpVault does not correctly validate OCSP responses in github.com/hashicorp/vault

Gitea does not properly validate repository ownership when linking attachments to releases in code.gitea.io/gitea

Klever-Go KVM read-only execution can commit contract delete and upgrade side effects in github.com/klever-io/klever-go

Answer vulnerable to Insertion of Sensitive Information Into Sent Data in github.com/answerdev/answer

Secret values can be printed to the --debug log when using a a custom publisher.

Go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation in github.com/go-git/go-git

The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com.

In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.

Cache driver GetBlob() allows read access to any blob without access control check in zotregistry.dev/zot.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: zotregistry.dev/zot before v2.1.0; zotregistry.io/zot before v2.1.0.

Gryph Agents Payload Filter Fails to Strip Tool Payload for Sensitive Content in github.com/safedep/gryph

Privilege escalation in rbac in github.com/google/exposure-notifications-verification-server

### Summary

If a user has restricted access to a project that is configured with `restricted=true`, they can gain root access on the system by creating a disk device with `shift=true` and creating a setuid root executable. This is possible because the `shift` property is not restricted unless `restricted.devices.disk.paths` is set.

### Details

The following patch shows the offending code with a possible fix:
```patch
--- a/lxd/device/disk.go
+++ b/lxd/device/disk.go
@@ -429,17 +429,19 @@ func (d *disk) validateEnvironmentSourcePath() error {
        if instProject.Name != api.ProjectDefaultName {
                // If restricted disk paths are in force, then check the disk's source is allowed, and record the
                // allowed parent path for later user during device start up sequence.
-               if shared.IsTrue(instProject.Config["restricted"]) && instProject.Config["restricted.devices.disk.paths"] != "" {
-                       allowed, restrictedParentSourcePath := project.CheckRestrictedDevicesDiskPaths(instProject.Config, d.config["source"])
-                       if !allowed {
-                               return fmt.Errorf("Disk source path %q not allowed by project for disk %q", d.config["source"], d.name)
+               if shared.IsTrue(instProject.Config["restricted"]) {
+                       if instProject.Config["restricted.devices.disk.paths"] != "" {
+                               allowed, restrictedParentSourcePath := project.CheckRestrictedDevicesDiskPaths(instProject.Config, d.config["source"])
+                               if !allowed {
+                                       return fmt.Errorf("Disk source path %q not allowed by project for disk %q", d.config["source"], d.name)
+                               }
+
+                               d.restrictedParentSourcePath = shared.HostPath(restrictedParentSourcePath)
                        }

                        if shared.IsTrue(d.config["shift"]) {
                                return fmt.Errorf(`The "shift" property cannot be used with a restricted source path`)
                        }
-
-                       d.restrictedParentSourcePath = shared.HostPath(restrictedParentSourcePath)
                }
        }
```

### PoC

```bash
$ lxc project create restricted -c restricted=true -c restricted.devices.disk=allow
$ lxc project switch restricted
$ lxc profile device add default root disk path=/ pool=default
$ lxc init ubuntu:22.04 c1
$ lxc config device add c1 d1 disk source=/ path=/mnt shift=true
$ lxc start c1  # no error

$ lxc project set restricted restricted.devices.disk.paths=/  # explicitly allow mounting /
$ lxc restart c1
Error: Failed to start device "d1": The "shift" property cannot be used with a restricted source path
```

Created https://github.com/canonical/lxd/issues/12606 to improve the documentation as per https://github.com/canonical/lxd/security/advisories/GHSA-x9qq-236j-gj97#advisory-comment-91918

Hashicorp Vault Privilege Escalation Vulnerability in github.com/hashicorp/vault

Gitea: Webhook Authorization Header Returned in Plaintext via API in gitea.dev

Gitea: Incomplete SSRF Protection in Webhook and Migration Allow-list Default Filter in code.gitea.io/gitea

Canonical LXD Project Existence Determination Through Error Handling in Image Get Function in github.com/canonical/lxd

A a third party may derive a valid proof from a valid initial tuple {proof, public_inputs}, corresponding to the same public inputs as the initial proof. This vulnerability is due to randomness being generated using a small part of the scratch memory describing the state, allowing for degrees of freedom in the transcript. Note that the impact is limited to the PlonK verifier smart contract.

OPKSSH Vulnerable to Authentication Bypass in github.com/openpubkey/opkssh

goshs --no-delete WebDAV MOVE bypass allows file deletion/overwrite in github.com/patrickhener/goshs

SiYuan has a Reflected Cross-Site Scripting (XSS) via /api/icon/getDynamicIcon in github.com/siyuan-note/siyuan/kernel

Fission Environment CRD PodSpec Injection Leading to Node Escape and Cluster Takeover in github.com/fission/fission

Gogs OS Command Injection vulnerability in gogs.io/gogs

SiYuan: SQL Query in Block Search Exposes Hidden Published Document Content in github.com/siyuan-note/siyuan/kernel

Pterodactyl Panel's SFTP sessions remain active after user account deletion or password change in github.com/pterodactyl/wings

Cilium East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers in github.com/cilium/cilium

HashiCorp Nomad’s exec2 task driver vulnerable to a symlink attack in github.com/hashicorp/nomad-driver-exec2

SiYuan: Unauthenticated Access to Password-Protected Bookmarks via /api/bookmark/getBookmark in github.com/siyuan-note/siyuan/kernel.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/siyuan-note/siyuan/kernel before v3.6.2.

Mattermost fails to properly validate User-Agent header tokens in github.com/mattermost/mattermost-server.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/mattermost/mattermost-server/v5 before v5.3.2-0.20260129181235-1346cf529aef.

ngress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation in k8s.io/ingress-nginx.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: k8s.io/ingress-nginx before v1.11.5, from v1.12.0-beta.0 before v1.12.1.

Arbitrary file write in nats-server in github.com/nats-io/nats-server

HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization in github.com/hashicorp/vault

Mattermost doesn't validate CSRF tokens on an authentication endpoint in github.com/mattermost/mattermost-server

High CPU usage leading to DoS via malicious p2p message in github.com/ethereum/go-ethereum

linx-server has an issue in the uploadPostHandler component that allows attackers to cause a Denial of Service (DoS) via a crafted POST request in github.com/andreimarcu/linx-server

Coder's unbounded memory allocation in provisioner file upload allows authenticated denial of service in github.com/coder/coder

CVE ID↕	Published↕	CVSS↓
GO-2024-2799	Jun 5, 2024	N/A
GO-2026-5098	Jun 25, 2026	N/A
GO-2026-4656	Mar 11, 2026	N/A
GO-2026-4719	Mar 26, 2026	N/A
GO-2026-6105	Aug 18, 2026	N/A
GO-2021-0084	Apr 14, 2021	N/A
GO-2020-0037	Apr 14, 2021	N/A
GO-2026-4558	Feb 27, 2026	N/A
GO-2025-4059	Oct 30, 2025	N/A
GO-2026-5430	Jun 25, 2026	N/A
GO-2022-0574	Jul 1, 2022	N/A
GO-2024-2495	Jun 28, 2024	N/A
GO-2026-6129	Aug 18, 2026	N/A
GO-2026-4765	Mar 23, 2026	N/A
GO-2023-2045	Sep 7, 2023	N/A
GO-2026-5257	Jun 25, 2026	N/A
GO-2026-5234	Jun 25, 2026	N/A
GO-2022-0360	Aug 21, 2024	N/A
GO-2025-4250	Dec 22, 2025	N/A
GO-2024-2697	Jun 5, 2024	N/A
GO-2026-6516	Sep 28, 2026	N/A
GO-2023-2188	Aug 21, 2024	N/A
GO-2026-6281	Aug 25, 2026	N/A
GO-2025-3873	Aug 18, 2025	N/A
GO-2026-5261	Jun 25, 2026	N/A
GO-2025-3758	Jul 28, 2025	N/A
GO-2026-4456	Feb 17, 2026	N/A
GO-2024-3296	Dec 2, 2024	N/A
GO-2025-4160	Nov 25, 2025	N/A
GO-2026-6626	Oct 7, 2026	N/A
GO-2025-4013	Oct 29, 2025	N/A
GO-2023-1533	Aug 20, 2024	N/A
GO-2025-4031	Oct 30, 2025	N/A
GO-2026-4801	Mar 23, 2026	N/A
GO-2026-5525	Jul 24, 2026	N/A
GO-2026-6294	Aug 26, 2026	N/A
GO-2026-4890	Apr 2, 2026	N/A
GO-2026-4607	Mar 10, 2026	N/A
GHSA-gp6j-vx54-5pmf	Jan 6, 2022	N/A
GO-2026-6455	Sep 16, 2026	N/A
GO-2023-2114	Oct 24, 2023	N/A
GO-2026-5544	Jun 25, 2026	N/A
GO-2026-5414	Jun 25, 2026	N/A
GO-2026-6268	Aug 25, 2026	N/A
GO-2023-2334	Nov 21, 2023	N/A
GO-2025-3551	Mar 25, 2025	N/A
GO-2026-6133	Aug 18, 2026	N/A
GO-2024-2440	Jun 28, 2024	N/A
GHSA-7xg2-83f8-39mr	Jan 3, 2024	N/A
GO-2026-5471	Jul 24, 2026	N/A
GO-2026-5670	Jun 25, 2026	N/A
GO-2025-3945	Sep 17, 2025	N/A
GO-2025-4233	Dec 15, 2025	N/A
GO-2025-3670	May 15, 2025	N/A
GO-2024-2746	Jun 4, 2024	N/A
GO-2024-2951	Jul 2, 2024	N/A
GO-2022-0590	Aug 21, 2024	N/A
GO-2023-1996	Aug 20, 2024	N/A
GO-2026-4828	Mar 26, 2026	N/A
GHSA-f28g-86hc-823q	Jul 13, 2023	N/A
GO-2022-1235	Aug 21, 2024	N/A
GO-2026-6103	Aug 18, 2026	N/A
GO-2024-3315	Dec 10, 2024	N/A
GO-2024-3226	Oct 30, 2024	N/A
GO-2026-4565	Mar 10, 2026	N/A
GO-2024-2667	Apr 16, 2024	N/A
GO-2024-2690	Jun 4, 2024	N/A
GO-2026-4364	Feb 2, 2026	N/A
GO-2026-5461	Jun 25, 2026	N/A
GO-2023-1716	Aug 20, 2024	N/A
GO-2024-2482	Feb 13, 2024	N/A
GO-2026-5074	Jul 24, 2026	N/A
GO-2025-3420	Jan 28, 2025	N/A
GO-2024-2979	Jul 10, 2024	N/A
GO-2026-5345	Jun 25, 2026	N/A
GO-2022-0798	Aug 21, 2024	N/A
GHSA-x9qq-236j-gj97	Dec 5, 2023	N/A
GO-2022-0618	Aug 21, 2024	N/A
GO-2026-6040	Jul 22, 2026	N/A
GO-2026-6030	Jul 22, 2026	N/A
GO-2025-4005	Nov 5, 2025	N/A
GO-2023-2119	Oct 24, 2023	N/A
GO-2025-3680	May 15, 2025	N/A
GO-2026-6136	Aug 18, 2026	N/A
GO-2026-4343	Feb 3, 2026	N/A
GO-2026-5860	Jul 7, 2026	N/A
GO-2023-1596	Aug 20, 2024	N/A
GO-2026-6353	Sep 10, 2026	N/A
GO-2026-4497	Feb 23, 2026	N/A
GO-2025-3560	Mar 25, 2025	N/A
GO-2026-5718	Jun 25, 2026	N/A
GO-2026-5318	Jun 25, 2026	N/A
GO-2026-4725	Mar 26, 2026	N/A
GO-2025-3565	Mar 25, 2025	N/A
GO-2022-0351	Aug 21, 2024	N/A
GO-2026-5199	Jun 25, 2026	N/A
GO-2026-5495	Jun 25, 2026	N/A
GO-2026-4314	Jan 23, 2026	N/A
GO-2026-6297	Aug 27, 2026	N/A
GO-2026-5911	Jul 7, 2026	N/A

Know every vulnerability
before it knows you.

go CVE Vulnerabilities — DevGuard Vulnerability Database

Know every vulnerabilitybefore it knows you.

go CVE Vulnerabilities — DevGuard Vulnerability Database

Know every vulnerability
before it knows you.