A vulnerability in atomic-server allows any authenticated agent to set the internalId property on a resource it owns without validation. The /download handler uses this internalId directly as a filesystem path without sanitization or containment checks, enabling arbitrary file read on the host. This includes sensitive files such as /etc/passwd and critically the server's root agent private key, which can lead to full server compromise. The flaw exists because the commit apply path does not restrict writable properties and the download handler trusts the stored internalId value. The vulnerability affects versions from 0.30.0 through 0.40.1. No official patch link is provided, but remediation involves sanitizing and confining the path and restricting client-settable properties.
Atomic Server versions 0.30.0 through 0.40.1 have a stored cross-site scripting (XSS) vulnerability via uploaded files served inline on the /download endpoint. Uploaded HTML or SVG files are served with Content-Disposition: inline and without Content-Security-Policy or X-Content-Type-Options headers, allowing execution of attacker-supplied scripts in the app origin. This enables theft of the session cookie (which is not HttpOnly) and the Ed25519 private key stored in IndexedDB, leading to permanent account takeover. If the victim is an admin/root Agent, this can lead to server takeover.
A vulnerability in djangocms-versioning prior to version 2.6.1 allows staff users to bypass intended object-level authorization checks when CMS_PERMISSION is enabled or disabled. This flaw permits staff users with certain permissions to discard draft versions or create editable drafts from published versions of content they should not be authorized to change. The issue is resolved in version 2.6.1.
When payload encryption is enabled, failure messages and stack traces that temporal-proxy is configured to keep from the upstream Temporal service can reach it in plaintext, where anyone who can read the Workflow's history at the upstream can read them. When the proxy returns a failure to a Worker, it decrypts the failure's encoded attributes and copies the message and stack trace back onto the failure, keeping the attributes. A Worker that sends that failure back through the proxy, as SDKs do when an Activity failure becomes the cause of a Workflow failure, sends the restored text with it, and the proxy forwards the text unchanged because the failure already has encoded attributes. The upstream then stores the text in plaintext beside its encrypted copy. This affects deployments that enable failure encryption in the proxy, and deployments that leave it off while the SDK encodes failure attributes itself. Payloads are not affected. temporal-proxy versions 0.9.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.
When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.
SharpIppNext is a .NET Standard library for building Internet Printing Protocol clients and servers. Prior to 4.1.0, server-side SharpIppNext implementations using SharpIppServer.ReceiveRequestAsync or SharpIppServer.ReceiveRawRequestAsync pass incoming data to IppProtocol.ReadIppRequestAsync in SharpIpp/Protocol/IppProtocol.cs, where ReadDocumentStream is enabled by default and the remaining document body is copied with CopyToAsync into a MemoryStream without a size limit. An unauthenticated remote client can send an arbitrarily large IPP document body, exhausting process memory and causing an out-of-memory failure or service termination. Client-only implementations using SharpIppClient are not affected. This issue is fixed in version 4.1.0.
A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.
A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach.
A caller who can reach the temporal-proxy gRPC listener, with or without a valid credential, can grow the proxy's memory until the process is terminated by sending requests with many distinct gRPC method names. temporal-proxy labels its request metrics with the method name exactly as the caller sent it, and records every request, including those that authentication or routing reject. Each distinct method name adds metric series that are never removed. The series grow whether or not the metrics endpoint is scraped, and metric labels configured from request metadata multiply the growth. temporal-proxy versions 0.1.0-alpha.20260716 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.
AnsibleForms versions prior to 6.2.1 contain a persistent cross-site scripting (XSS) vulnerability. Authenticated users can submit job input that is stored and later rendered without proper HTML escaping, enabling script execution in other users' browsers. The lack of Content Security Policy and storage of JWT tokens in localStorage increases the risk of token theft and account takeover, including administrator accounts. This vulnerability is fixed in version 6.2.1.
AnsibleForms versions prior to 6.2.1 contain an OS command injection vulnerability that allows users with repository management privileges to execute arbitrary commands on the server. This occurs because user-controlled inputs in repository management are interpolated into shell commands without proper sanitization. The issue is fixed in version 6.2.1.
AnsibleForms versions prior to 6.2.1 contain an authentication bypass vulnerability due to a hard-coded fallback JWT signing secret. This allows an unauthenticated attacker to forge tokens with administrative privileges, gaining full privileged API access. The issue is resolved in version 6.2.1.
NotrinosERP versions from 1.0.0 up to but not including 1.1.0 contain a path traversal vulnerability in the employee document handler. Authenticated users with SA_EMPLOYEE permission can upload files with executable extensions without validation, leading to server-side code execution when the uploaded file is accessed. This vulnerability is fixed in version 1.1.0.
CVE-2026-76090 is a code injection vulnerability in the softwaremill tapir Scala library prior to version 1.13.27. The vulnerability arises from tapir-openapi-codegen-core generating Scala source code from untrusted OpenAPI documents without proper validation or escaping of object property names, query, header, path parameter names, and operation tags. This allows crafted input to inject arbitrary Scala code during code generation and compilation. This is a build-time issue and does not directly affect running tapir servers. The issue is fixed in version 1.13.27.
CVE-2026-71425 is a server-side request forgery (SSRF) vulnerability in avitorio outstatic versions prior to 2.2.1. The issue arises because the authenticated GitHub REST proxy accepts an unvalidated endpoint parameter and concatenates it to form an upstream URL, attaching the user's GitHub OAuth token without verifying the destination host. This allows an authenticated user to cause the server to send their token to a non-GitHub host, potentially exposing private repositories and resources accessible by the token. The vulnerability does not allow unauthenticated attackers to access private data or other users' tokens without additional exploitation. The issue is fixed in version 2.2.1.
Finsys Dockhand versions prior to 1.0.55 contain a path traversal vulnerability that allows users with stacks:edit permission to move arbitrary server directories by providing a crafted oldDir parameter. This can be exploited via POST requests to the /api/stacks/[name]/relocate endpoint, enabling attackers to relocate directories into stack paths, potentially disrupting services and exposing sensitive contents. The vulnerability is fixed in version 1.0.55.
CVE-2026-130751 is a privilege management vulnerability in OpenWrt LuCI's luci-app-travelmate component. Versions before 3.0.0-1 on master and before 2.4.9-6 on openwrt-25.12 allow authenticated read-only users to execute state-mutating commands as root via the rpcd ACL. This enables attackers to run commands such as /etc/init.d/travelmate setup, start, stop, restart, or /sbin/ifup, potentially modifying network and firewall configurations or disrupting the travelmate daemon.
The uhop package 'install-artifact-from-github' prior to version 1.7.0 downloads prebuilt native artifacts from GitHub without verifying their cryptographic integrity. This allows an attacker who can control the download source or intercept the download to supply malicious native code that executes when loaded. Version 1.7.0 introduces SHA-256 verification for default GitHub sources if the consuming package provides artifact hashes, but configured mirrors and packages without these hashes remain unverified.
cf-manager is an all-in-one dashboard for managing multiple Cloudflare accounts and services. Prior to 1.1.2, worker/src/routes/workers.ts uses bare fetch(url) calls to retrieve user-supplied URLs and deploys the returned content as a Worker script using stored Cloudflare credentials. The multipart and JSON branches of POST /api/:accountId/workers and POST /api/batch-deploy accept URLs without protocol, destination, redirect, content-type, or response-size validation. An attacker with deployment API access, or unauthenticated access when API_SECRET is not configured, can make cf-manager access internal resources or fetch attacker-controlled JavaScript and execute it in the victim Cloudflare Workers account. This issue is fixed in version 1.1.2.
Miren Runtime versions prior to 0.11.1 contain an improper certificate validation vulnerability in the QUIC/HTTP3 RPC server. The server accepts client certificates without verifying that they chain to the configured cluster certificate authority, allowing an attacker to present a self-signed certificate with a matching issuer distinguished name. This flaw enables the attacker to bypass RBAC checks and gain cluster superuser access, risking disclosure, modification, or disruption of managed resources. The issue is fixed in version 0.11.1.