CVE-2026-65835 is a medium severity vulnerability in projectcapsule's capsule framework affecting versions prior to 0.13.8. It involves improper privilege management where tenant owners could create cluster-scoped resources due to incomplete enforcement of resource scope restrictions. The issue was fixed in version 0.13.8.
Capsule is a multi-tenancy and policy-based framework for Kubernetes. Prior to 0.13.8, CapsuleConfiguration.Spec.NodeMetadata.ForbiddenLabels.Regex and CapsuleConfiguration.Spec.NodeMetadata.ForbiddenAnnotations.Regex were not validated by the configuration admission webhook, allowing a Cluster Admin to store a malformed regex that later reached regexp.MustCompile in pkg/api/forbidden_list.go through internal/webhook/node/user_metadata.go and crashed the node admission webhook on Node create, update, or patch requests. This issue is fixed in version 0.13.8.
Netfoil versions prior to 0.4.0 use 0.0.0.0 instead of NXDOMAIN for block responses. On Linux systems, this causes blocked DNS queries to be redirected to localhost rather than being dropped. The impact depends on the services running on localhost and firewall configurations, potentially causing unintended local traffic.
A vulnerability in Zitadel's user self-management API allowed users to mark their email and phone as verified without completing the actual verification process. This was due to improper permission checks that enabled users to retrieve verification codes for email and phone numbers they do not control. The issue affects Zitadel versions 4.0.0 through 4.15.0, 3.0.0 through 3.4.10, and 2.43.0 through 2.71.19. The vulnerability has been fixed in versions 4.15.1 and later, 3.4.11 and later, and 3.4.11 and later for the respective branches. Users are advised to upgrade to these patched versions to mitigate the risk. If upgrading is not possible, a workaround exists to prevent returning verification codes to the user.
Cosmos provides users the ability self-host a home server by acting as a secure gateway to your application, as well as a server manager. Prior to 0.22.19, tokenMiddleware in src/proxy/routerGen.go can return through the Constellation tunnel bypass before removing x-cosmos-user, x-cosmos-role, x-cosmos-user-role, and x-cosmos-mfa headers and before invoking AdminOnlyWithRedirect. An attacker with a valid x-cstln-auth API key for an enrolled device who reaches Cosmos through the Constellation Nebula tunnel can supply a chosen x-cosmos-user value to a route with AuthEnabled enabled when the upstream application trusts that forward-auth header. The request can bypass Cosmos JWT, password, MFA, and AdminOnly checks, allowing user impersonation and admin-tier reads or writes exposed by the proxied application. This issue is fixed in version 0.22.19.
A lexical path validation flaw in the SanitizeFilePath function of github.com/fission/fission allowed sibling-directory escape due to improper use of strings.HasPrefix without enforcing path-separator boundaries. This permitted tenants controlling sibling directories to read or write outside intended safe directories. The issue affected all versions through v1.24.0 and was fixed in v1.25.0 by replacing SanitizeFilePath with kernel-enforced directory confinement helpers.
A Zip Slip vulnerability exists in the Unarchive function of pkg/utils/zip.go in github.com/fission/fission up to version 1.24.0. The function improperly joins archive entry names with the destination directory without validating that the resolved path remains inside the destination. This allows crafted zip entries with directory traversal sequences (e.g., ../../tmp/evil) to write files outside the intended extraction directory. The vulnerability can be triggered when the fetcher downloads and extracts a zip archive, potentially allowing an attacker controlling the archive URL to write files arbitrarily within the file system accessible to the fetcher process.
A validation bypass vulnerability exists in the HTTPTrigger resource of the Fission project (github.com/fission/fission) through version 1.24.0. The fields RelativeURL and Prefix were only validated at the CLI level, not at the API server admission level, allowing creation of HTTPTriggers with unsafe or conflicting URL paths via kubectl apply or direct API calls. This could lead to triggers with empty URLs, paths not starting with '/', paths containing directory traversal segments, or collisions with reserved router paths. The issue was fixed in version 1.25.0 by enforcing consistent validation rules at both the API server and CLI layers.
Fission versions up to 1.24.0 implemented PodSpec validation with a fixed denylist of Linux capabilities but omitted CAP_SYS_TIME. This omission allows tenants to add CAP_SYS_TIME to their function or environment containers, enabling them to alter the node's real-time clock. Since the Linux real-time clock is shared across the node, this can corrupt time-dependent operations for all workloads on that node. The vulnerability is fixed in Fission 1.25.0 by replacing the denylist with a restrictive allowlist for capabilities. The issue does not apply if a restrictive Pod Security Admission profile is enforced on the function-pod namespace.
A vulnerability in etcd prior to versions 3.5.33, 3.6.14, and 3.7.1 allows a network attacker to cause unbounded growth of handshake goroutines by opening many TCP connections to the TLS listener and not completing the TLS handshake. This can exhaust memory and cause denial of service, impacting availability of the etcd cluster and dependent systems such as Kubernetes control planes.
A null-pointer dereference vulnerability exists in kin-openapi's openapi3filter.ValidateRequest function, allowing unauthenticated clients to cause a denial of service by sending a single HTTP request. The issue occurs when validating a request against a content parameter whose media type object lacks a schema, which is legal under the OpenAPI specification. This leads to a panic and potential process crash in versions up to 0.143.0. The vulnerability affects both OpenAPI 3.0.x and 3.1.x and is patched in version 0.144.0.
A vulnerability in etcd's Watch API allows a user with READ permission on a single exact key to bypass authorization and watch events for all keys lexicographically greater than or equal to that key. This affects versions prior to 3.5.33, 3.6.14, and 3.7.1 when authentication is enabled. The issue arises because the open-ended RangeEnd sentinel is rewritten before the RBAC permission check, causing improper permission validation. This flaw does not affect Range/Get or DeleteRange requests and only impacts clusters with authentication enabled. The vulnerability has been fixed in the specified versions.
Oh My Posh versions prior to 29.35.1 contain a vulnerability where the resolved path string is re-rendered as a Go template, evaluating any template expressions in folder names. This allows arbitrary command execution as the current user when the shell prompt renders inside or below a directory with a crafted name. The default configuration is affected, and the issue impacts multiple path styles.
Oh My Posh versions prior to 29.35.1 allow terminal escape sequence injection via unsanitized prompt segment data. This occurs because dynamic strings such as directory names and Git commit metadata are rendered into the prompt without neutralizing raw terminal control characters. An attacker controlling these values can inject ANSI/OSC escape sequences that the victim's terminal executes on every prompt render, enabling clipboard hijacking, prompt spoofing, window-title manipulation, and denial of service.
OpenList v4 contains an authorization bypass vulnerability in its file sharing API due to improper path prefix validation. An authenticated user with sharing privileges can create share links to files outside their assigned base directory by exploiting a flawed string prefix check that does not consider directory separators. This allows unauthorized read access to arbitrary files in sibling directories, breaking tenant/user isolation. The issue affects versions prior to 4.2.4. The vulnerability enables horizontal privilege escalation by exposing files from other users or internal paths. No known exploits in the wild have been reported.
OpenList v4 before 4.2.4 contains an authorization bypass and information disclosure vulnerability in its search API due to improper path prefix validation and unfiltered backend counting in the Bleve search engine. A low-privileged user can bypass BasePath restrictions to access metadata of files in unauthorized sibling directories and confirm the existence of sensitive files via the total count field. This defeats the intended namespace isolation and allows enumeration of hidden infrastructure and sensitive file metadata.
OpenList v4 contains a vulnerability in its batch rename API that allows authenticated users with rename permissions to rename files outside their authorized base directory by using path traversal in the source filename parameter. The API validates the destination name but fails to properly validate the source name, enabling directory traversal and unauthorized file renaming. This affects versions prior to 4.2.4 and has a high severity rating with a CVSS score of 7.6. A patch is available to address this issue.
Cloudreve v4 exposes two admin node test endpoints that require only the Admin.Read OAuth scope but allow triggering server-side network requests to attacker-controlled URLs. This enables an attacker with an Admin.Read-only OAuth token to perform blind SSRF and internal service probing, actions that should require Admin.Write scope. The issue was verified in version 4.16.1 and the latest master commit. The root cause is missing Admin.Write scope enforcement on these test endpoints, which perform outbound network requests using attacker-supplied configuration.
An integer overflow vulnerability in the frp server's SSH Tunnel Gateway allows an unauthenticated remote attacker to crash the entire frps process by sending a specially crafted five-byte message. This causes a slice bounds out-of-range panic in the Go runtime, terminating the server process and dropping all active tunnels. The vulnerability is reachable without authentication when the SSH Tunnel Gateway is enabled with no authorized-keys file, which is the default mode. There is no confidentiality or code execution impact. The issue affects frp versions from v0.53.0 through v0.70.0 with the SSH Tunnel Gateway enabled.
Kite versions 0.6.9 through 0.14.0 contain a path traversal vulnerability in the Kubernetes proxy feature that allows authenticated users with limited namespace permissions to bypass RBAC restrictions and read cluster-wide resources. The vulnerability arises because encoded path traversal segments are decoded after authorization checks, enabling access to Kubernetes API endpoints outside the authorized namespace. This can lead to disclosure of sensitive cluster-wide information, including Secrets. The issue is fixed in version 0.14.1.