Open OnDemand versions prior to 4.1.6 and between 4.2.0 and before 4.2.3 log noVNC passwords in query parameters within user access logs. These logs, if insufficiently protected, can be accessed by other local users who may recover and replay the launch URLs, gaining unauthorized access to remote desktops. This can lead to privilege escalation depending on the desktop owner's privileges. The vulnerability is fixed in versions 4.1.6 and 4.2.3.
CVE-2026-132140 is a high-severity vulnerability in DrayTek Vigor2960 firmware up to version 1.5.1.6. It involves a null pointer dereference in the mainfunction.cgi file's Apmcfg Upload component, which can be triggered remotely without authentication. Exploit code has been publicly disclosed. Upgrading to version 1.5.1.7 resolves the issue.
IBM Engineering AI Hub 1.0.0 through 1.4.0 could allow a remote attacker to obtain sensitive information and perform unauthorized actions due to improper validation of a redirect URL.
IBM Engineering AI Hub 1.0.0 through 1.4.0 could allow a remote attacker to obtain sensitive information due to a Cross Origin Resource Sharing (CORS) misconfiguration.
IBM Engineering AI Hub 1.0.0 through 1.4.0 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
IBM Engineering AI Hub 1.0.0 through 1.4.0 could allow a remote authenticated attacker to obtain sensitive information due to a server-side request forgery.
CVE-2026-75522 is an improper certificate validation vulnerability in the openid4vp library prior to version 0.8.1. The flaw allows an attacker to supply a self-signed certificate that reuses a trusted Subject Distinguished Name without proper cryptographic verification, causing the system to accept forged credentials as if issued by a trusted authority. This issue is fixed in version 0.8.1.
CVE-2026-76088 is a high-severity vulnerability in the pgpainless OpenPGP API where certain components manually process deeply nested compressed packet structures without enforcing the maximum allowed layer depth. This allows a remote unauthenticated attacker to supply crafted OpenPGP messages that bypass the 16-layer limit, causing excessive resource consumption, thread blocking, heap exhaustion, and potential application crashes. The issue affects versions prior to 1.7.8 and from 2.0.0 up to but not including 2.0.4. Fixed versions are 1.7.8 and 2.0.4.
CVE-2026-132139 is a critical stack-based buffer overflow vulnerability in DrayTek Vigor2960 devices up to version 1.5.1.6. The flaw exists in the setSWMProfile function within /cgi-bin/mainfunction.cgi and can be exploited remotely by manipulating the filename argument. Public exploit code is available. Upgrading to version 1.5.1.7 or later addresses this issue.
Outstatic versions prior to 2.2.1 contain a vulnerability in their authenticated GitHub REST proxy that allows a user with dashboard access to cause the server to send their GitHub OAuth token to arbitrary non-GitHub origins. This occurs because the endpoint parameter was not properly validated, enabling token leakage to external hosts. The vulnerability does not allow unauthenticated attackers to access private data or other users' tokens without additional exploits. The issue has been fixed in version 2.2.1 by enforcing strict origin validation and restricting forwarded headers.
Atomic Server versions 0.29.0 through 0.40.1 contain a critical vulnerability (CVE-2026-69157) where an unauthenticated attacker can redeem a well-known invite at the /setup endpoint to gain write access to the entire Drive. This invite is created with write permissions and usagesLeft=1 but does not verify the redeemer's identity, allowing full Drive takeover on fresh deployments without credentials. The vulnerability allows an attacker to create a new Agent with write access, modify or delete any resource, and reconfigure permissions. The invite redemption mechanism also suffers from a TOCTOU race condition and an inverted expiry check, enabling multiple concurrent redemptions and acceptance of expired invites. No patch information is provided, and remediation requires adding authentication or a one-time secret to redeem /setup and fixing the invite usage logic.
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.
Dell Alienware Command Center (AWCC) versions prior to 6.14.105.0 contain a vulnerability involving improper restriction of rendered UI layers or frames. This flaw could be exploited by a high privileged attacker with remote access to cause denial of service or facilitate phishing attacks. The vulnerability has a low CVSS score of 3.1 and has been fixed in version 6.14.105.0.
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.