Kodareef5

**Name of the Vulnerable Software and Affected Versions** NATS Server versions prior to 2.14.3 NATS Server versions prior to 2.12.8 **Description** Message trace destination checks are not consistently applied to messages arriving through leafnode connections. This allows a leafnode operator to send trace events to subjects that are normally restricted and utilize trace-only behavior to block the standard delivery or storage of affected messages. **Recommendations** Update NATS Server to version 2.14.3 or later. Update NATS Server to version 2.12.8 or later.

**Name of the Vulnerable Software and Affected Versions** NATS Server versions prior to 2.12.8 NATS Server versions prior to 2.11.17 **Description** An unauthenticated peer with network access to a leafnode listener with compression enabled can cause the server to crash. This occurs during the pre-authentication leafnode handshake when repeated leafnode INFO protocol messages are sent before the authentication and account setup processes are completed. **Recommendations** Update NATS Server to version 2.12.8 or later. Update NATS Server to version 2.11.17 or later.

**Name of the Vulnerable Software and Affected Versions** NATS Server versions prior to 2.14.3 NATS Server versions prior to 2.12.12 **Description** An authenticated MQTT client can subscribe to the internal `$MQTT.deliver.pubrel` subject family. This action allows the client to bypass configured subscribe permissions and expose MQTT QoS2 protocol metadata for sessions within the account. QoS2 (Quality of Service level 2) is a protocol mechanism that ensures a message is delivered exactly once. **Recommendations** Update NATS Server to version 2.14.3 or later. Update NATS Server to version 2.12.12 or later.

**Name of the Vulnerable Software and Affected Versions** Coolify versions prior to 4.0.0-beta.471 **Description** Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. An authenticated user can execute commands on managed servers when a resource is deleted because the `LocalPersistentVolume.name` field is interpolated directly into docker volume shell commands without shell argument escaping. This allows the injection of shell metacharacters into the storage name. **Recommendations** Update to version 4.0.0-beta.471.

**Name of the Vulnerable Software and Affected Versions** authentik versions prior to 2025.12.5 authentik versions prior to 2026.2.3 **Description** The SAML source response processor `ResponseProcessor.parse()` fails to validate the Conditions element on assertions. Specifically, `NotBefore`, `NotOnOrAfter`, and `AudienceRestriction` are ignored, which enables the replay of expired assertions and the acceptance of assertions intended for different service providers. **Recommendations** Update to version 2025.12.5. Update to version 2026.2.3.

**Name of the Vulnerable Software and Affected Versions** Cilium versions prior to 1.17.15 Cilium versions 1.18.0 through 1.18.8 Cilium versions 1.19.0 through 1.19.2 **Description** When run against deployments with WireGuard encryption enabled, the output of the `cilium-bugtool` debugging tool can contain sensitive data. Specifically, the WireGuard private key `cilium wg0.key`, used for node-to-node encrypted communication, may be exposed. This tool is typically invoked manually or during the gathering of sysdumps via the `cilium sysdump` command. **Recommendations** Update to version 1.17.15 for versions prior to 1.17.15. Update to version 1.18.9 for versions 1.18.0 through 1.18.8. Update to version 1.19.3 for versions 1.19.0 through 1.19.2. Rotate WireGuard keys on affected nodes by deleting the key file and restarting the Cilium agent to generate a new key pair if bugtool or sysdump archives have been shared.

**Name of the Vulnerable Software and Affected Versions** Traefik versions prior to 2.11.43 Traefik versions prior to 3.6.14 Traefik versions prior to 3.7.0-rc.2 **Description** A timing side-channel issue exists in the BasicAuth middleware. A variable meant to provide a constant-time fallback secret consistently resolves to an empty string, which causes the constant-time comparison to short-circuit quickly instead of completing a full bcrypt evaluation. This creates a timing oracle, allowing an attacker to enumerate valid usernames by measuring differences in authentication response times. **Recommendations** Update to version 2.11.43 Update to version 3.6.14 Update to version 3.7.0-rc.2

**Name of the Vulnerable Software and Affected Versions** Contour versions 1.19.0 through 1.31.5 Contour versions 1.32.0 through 1.32.4 Contour versions 1.33.0 through 1.33.3 **Description** The Cookie Rewriting feature is susceptible to Lua code injection. An attacker with RBAC permissions to create or modify HTTPProxy resources can provide malicious values in the `spec.routes[].cookieRewritePolicies[].pathRewrite.value` or `spec.routes[].services[].cookieRewritePolicies[].pathRewrite.value` variables, leading to arbitrary code execution in the Envoy proxy. This occurs because user-controlled values are interpolated into Lua source code using Go text/template without sufficient sanitization. While the injected code executes only on the attacker's own route, it can be used to read Envoy xDS client credentials from the filesystem—potentially exposing TLS certificates and private keys of other tenants—or cause a denial of service for other tenants sharing the Envoy instance. **Recommendations** Update to version 1.31.6. Update to version 1.32.5. Update to version 1.33.4.

**Name of the Vulnerable Software and Affected Versions** Tekton Pipelines versions prior to 1.11.1 **Description** A validation bypass in the VolumeMount path restriction allows mounting volumes under restricted '/tekton/' internal paths by using '..' path traversal components. The restriction check uses the `strings.HasPrefix` function without applying `filepath.Clean`, meaning a path such as '/tekton/home/../results' passes validation but resolves to '/tekton/results' at runtime. This occurs because '/tekton/home' is an allowed prefix, allowing the traversal to bypass the check. This issue exists in the `container validation.go` and `task validation.go` files. An authenticated user with Task or TaskRun creation permissions could exploit this to write fake task results, read or modify step scripts before execution, or interfere with entrypoint coordination state. **Recommendations** Update to version 1.11.1. Use admission controllers such as OPA/Gatekeeper or Kyverno to validate that VolumeMount paths do not contain '..' components. Restrict permissions for creating Task and TaskRun resources via RBAC in multi-tenant environments.

**Name of the Vulnerable Software and Affected Versions** Tekton Pipelines versions 1.0.0 through 1.10.x **Description** The git resolver fails to validate the `revision` parameter, which is passed directly as a positional argument to the `git fetch` command. This allows an attacker to inject arbitrary flags, such as `--upload-pack=<binary>`. Additionally, the `validateRepoURL` function permits URLs starting with `/`, allowing local filesystem paths. A tenant capable of submitting `ResolutionRequest` objects can combine these behaviors to execute arbitrary binaries on the resolver pod. Because the `tekton-pipelines-resolvers` ServiceAccount possesses cluster-wide `get`, `list`, and `watch` permissions on all Secrets, this can lead to full cluster-wide secret exfiltration. **Recommendations** Update to version 1.11.1.

**Name of the Vulnerable Software and Affected Versions** Statamic versions prior to 5.73.20 Statamic versions prior to 6.13.0 **Description** Manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, can lead to the loss of content, assets, and user accounts. Exploitation via the Control Panel requires authentication with minimal permissions, such as the "view entries" permission to delete entries or the "view users" permission to delete users. Exploits targeting the REST and GraphQL APIs do not require permissions, but these APIs are not enabled by default; they must be explicitly enabled without authentication and with specific resources accessible to be exploited. **Recommendations** Update to version 5.73.20 Update to version 6.13.0

**Name of the Vulnerable Software and Affected Versions** OAuth2 Proxy versions prior to 7.15.2 **Description** An authorization bypass exists within the `email domain` enforcement option. An attacker can authenticate using a malformed email claim, such as `attacker@evil.com@company.com`, to satisfy an allowed domain check for `company.com`. This issue specifically affects deployments relying on `email domain` restrictions that accept email claim values from identity providers or claim mappings that do not strictly enforce standard email syntax. The risk is primarily present in self-hosted or custom OIDC environments and federated setups where unexpected claim values can reach the proxy. **Recommendations** Update to version 7.15.2 or later. Ensure the configured identity provider is unable to emit malformed or attacker-controlled email claim values.

**Name of the Vulnerable Software and Affected Versions** External Secrets Operator versions prior to 2.3.0 **Description** The v2 template engine in `runtime/template/v2/template.go` removes `env` and `expandenv` from `TxtFuncMap()` but leaves the `getHostByName()` function accessible to user-controlled templates. Since the controller executes templates within its own process, an attacker capable of creating or updating templated ExternalSecret resources can trigger controller-side DNS lookups using secret-derived values. This enables a DNS exfiltration primitive, allowing secret material to be leaked via DNS queries without requiring direct outbound network access from the attacker's workload. This results in a confidentiality issue in environments where lower-trust users can author these resources and the controller has DNS resolution capabilities. **Recommendations** Update to version 2.3.0. Restrict the ability of untrusted or lower-trust users to create or update templated ExternalSecret resources.

Name of the Vulnerable Software and Affected Versions File Browser versions prior to 2.63.1 Description File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. The `resourceGetHandler` in http/resource.go returns full text file content without checking the `Perm.Download` permission flag. The `/api/raw`, `/api/preview`, and `/api/subtitle` endpoints correctly verify this permission before serving content. A user with `download: false` can read any text file within their scope through bypass paths. Recommendations Update to version 2.63.1 or later.

Name of the Vulnerable Software and Affected Versions Cosign versions prior to 3.0.6 and prior to 2.6.3 Description Cosign, a tool for code signing and transparency for containers and binaries, had a flaw in `verify-blob-attestation` where it could incorrectly report a successful verification (“Verified OK”) for attestations containing malformed payloads or mismatched predicate types. This occurred due to a logic error in predicate type validation for older bundle formats and a complete bypass of predicate type validation for newer bundle formats. Recommendations Update to version 3.0.6 or later. Update to version 2.6.3 or later.

File Browser versions prior to 2.63.1 Description: File Browser is a file managing interface. Prior to version 2.63.1, a fix intended to restrict execute permissions for self-registered users was not applied to the proxy authentication handler. This allowed users automatically created on first successful proxy authentication login to inherit execution capabilities from global defaults, violating a security invariant. This issue is an incomplete fix for a previous problem where signup granted execution permissions when default permissions included execution. The vulnerability is related to the application of default settings in the `auth/proxy.go` `createUser()` function, where restrictions on `Execute` permission and `Commands` were missing compared to the signup handler. API Endpoint: /api/login. Vulnerable Parameters: `username`. Function Name: `createUser()`. Recommendations: Upgrade to File Browser version 2.63.1 or later.

Name of the Vulnerable Software and Affected Versions File Browser versions prior to 2.63.1 Description File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. The `Matches()` function in rules/rules.go uses `strings.HasPrefix()` without a trailing directory separator when matching paths against access rules. A rule for /uploads also matches /uploads backup/, potentially granting or denying access to unintended directories. Recommendations Update to version 2.63.1 or later.

Name of the Vulnerable Software and Affected Versions: File Browser versions prior to 2.63.1 Description: File Browser is a file managing interface. Prior to version 2.63.1, when an administrator revokes a user's Share and Download permissions, existing share links created by that user remain accessible to unauthenticated users. The public share download handler does not re-check the share owner's current permissions. This allows unauthenticated users to access files through existing share links even after the owner's permissions have been revoked. The vulnerability exists because the share access function does not validate the user's Share and Download permissions, unlike the share creation function. The API endpoint ''/api/public/dl/{hash}'' is affected, where `{hash}` represents the share link hash. The vulnerable parameter is the share link hash itself, as it allows access without proper permission checks. The function `withHashFile` is responsible for handling share access and lacks the necessary permission validation. Recommendations: Update File Browser to version 2.63.1 or later.

Name of the Vulnerable Software and Affected Versions: pyLoad versions 0.5.0b3.dev96 and earlier Description: pyLoad contains a server-side request forgery (SSRF) vulnerability. The initial fix for CVE-2026-33992 added IP validation to the initial download URL, but HTTP redirects are not validated. An authenticated user with ADD permission can bypass the SSRF fix by submitting a URL that redirects to an internal address. The vulnerability allows access to cloud metadata endpoints, internal network services, and localhost services. The `BaseDownloader.download()` function and `HTTPRequest` class are involved in the vulnerability. The `FOLLOWLOCATION` option in pycurl is set to 1, and `MAXREDIRS` is set to 10, enabling automatic redirect following. The `REDIR PROTOCOLS` option is not restricted, allowing redirects to any protocol. The SSRF check only validates the initial URL, and redirect targets bypass the filter entirely. Recommendations: Disable automatic redirect following in `HTTPRequest. init ()` by setting `self.c.setopt(pycurl.FOLLOWLOCATION, 0)`. Implement manual redirect following in the download logic with SSRF validation at each hop. Alternatively, restrict redirect protocols by setting `self.c.setopt(pycurl.REDIR PROTOCOLS, pycurl.PROTO HTTP | pycurl.PROTO HTTPS)` and add a pycurl callback to validate redirect destination IPs before following.

**Name of the Vulnerable Software and Affected Versions** BentoML versions prior to 1.4.38 **Description** BentoML contains a remote code execution (RCE) issue in the cloud deployment path within `src/bentoml/ internal/cloud/deployment.py`. Specifically, line 1648 interpolates `system packages` directly into a shell command using an f-string without proper quoting. This allows for command injection when the generated script, `setup.sh`, is uploaded to BentoCloud and executed during deployment. The vulnerability arises because the fix implemented in commit ce53491, which added `shlex.quote` to other areas of the code, was not applied to this specific path. The `system packages` values from `bentofile.yaml` are joined with spaces and directly interpolated into the `apt-get install` command, enabling an attacker to inject arbitrary commands. A proof of concept demonstrates that a malicious `bentofile.yaml` can be crafted to exfiltrate the hostname of the build infrastructure. This could lead to supply chain attacks, insider threats, or broader CI/CD compromise. **Recommendations** Update to BentoML version 1.4.38 or later.