Gitea versions prior to 1.27.0 have a denial of service vulnerability in the SSH key ingestion endpoint. The flaw is due to an O(N²) string concatenation loop in the SSH2 key normalization function that lacks input size limits. An authenticated user can submit a maliciously large SSH2 formatted key, causing excessive CPU and memory usage that may take the server offline. This vulnerability is identified as CVE-2026-56657 and is classified as a moderate severity issue. A patch is available to address this vulnerability.
Gitea versions prior to 1.26.4 contain a vulnerability in the CODEOWNERS feature where user-supplied regex patterns are compiled without sanitization or timeout, enabling a Regular Expression Denial of Service (ReDoS) attack. An attacker with a repository can craft malicious CODEOWNERS patterns and file names in pull requests that cause exponential regex backtracking, hanging the server during pull request processing. This results in database connections being held open, potentially exhausting the connection pool and making the Gitea instance unresponsive.
In Eclipse hawkBit versions 1.0.3 and prior, a privilege escalation vulnerability (CWE-284 / CWE-862) has been identified in the Direct Device Integration (DDI) Controller.
This vulnerability allows an authenticated device to escalate its permissions and bypass the strict boundaries of its assigned updates. Under normal operation, a device should be restricted strictly to the specific firmware artifacts explicitly assigned to it. However, this flaw enables any authenticated device to bypass this restriction and download any firmware artifact within the same tenant.
This is not an authentication bypass; the requesting device must possess valid credentials for its respective tenant. Instead, the issue stems from a flaw in object-level authorization validation.
A related, lower-severity helper issue exists in the listing software modules artifacts metadata endpoint. This endpoint does not enforce assignment checks, enabling an authenticated device to list and enumerate available firmware artifacts, which can facilitate targeted exfiltration using the main download authorization bypass.
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have a broken workspace authorization check that allows any authenticated low-privilege workspace member to escalate their own role to `owner`. The issue is caused by privileged workspace-management routes using the shared dependency `require_workspace_member(...)` without requiring `admin` or `owner`. The dependency defaults to `min_role="member"`, so routes that should be administrative are accessible to ordinary workspace members. As a result, a normal workspace member can promote their own account from `member` to `owner`; add arbitrary users as `owner` or `admin`; change other members' roles; remove legitimate owners or members; take over workspace membership completely; and/or perform destructive workspace operations after escalation. This is a broken access control / vertical privilege escalation vulnerability. PraisonAI Platform version 0.1.4 patches the issue.
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Prior to version 0.1.4, the workspace-scoped REST routes contain a systemic object-level authorization flaw that allows an authenticated user from one workspace to access, modify, and delete objects belonging to another workspace by supplying the victim object's global UUID. The affected pattern appears in workspace-scoped routes such as agents, projects, issues, and comments. The route layer verifies that the caller is a member of the `workspace_id` provided in the URL, but the service layer later resolves the target object by global object ID only. It does not verify that the resolved object actually belongs to the workspace in the URL. As a result, a valid member of `workspace_attacker` can call a route under `/api/v1/workspaces/{workspace_attacker}/...` while supplying an object UUID from `workspace_victim`. The server authorizes the request based on membership in `workspace_attacker`, then fetches or mutates the victim object by global UUID. This breaks the platform's workspace isolation boundary. PraisonAI Platform version 0.1.4 patches the issue.
PraisonAI versions prior to 4.6.40 have an improper access control vulnerability in the call server's agent control API. When the environment variable CALL_SERVER_TOKEN is not set, the authentication mechanism fails open, allowing unauthenticated remote clients to control agents. This includes listing, inspecting, invoking, and unregistering agents. The call server binds to all network interfaces (0.0.0.0), increasing exposure risk. Version 4.6.40 addresses this issue.
SolarWinds Serv-U is affected by a broken access control vulnerability that could allow arbitrary file read and write, which can then be used to escalate privileges and execute code as root. A domain administrator access is required, and the impact is lower in Windows installations.
SolarWinds Serv-U is affected by a privilege escalation vulnerability that allows a domain user group to be elevated into an administrator group. The impact is lower in Windows deployments.
SolarWinds Serv-U is affected by a privilege escalation vulnerability that allows a domain administrator to elevate their privileges to a system administrator. The impact is lower in Windows deployments.
SolarWinds Serv-U is affected by a remote code execution vulnerability that, when exploited, can allow the arbitrary execution of code remotely as root. The impact is lower in Windows deployments.
CVE-2026-16365 is a high-severity vulnerability affecting the DOM: Workers component in Thunderbird and Firefox packages on Red Hat Enterprise Linux and SUSE Linux Enterprise distributions. It involves multiple authorization and memory safety weaknesses. The vulnerability is addressed by updates equivalent to Mozilla's Firefox 153 release. No CVSS score is provided, but the impact is considered high.
CVE-2026-47255 is a high-severity vulnerability affecting the @agenticmail/api and @agenticmail/core packages prior to versions 0.9.32 and 0.9.10 respectively. The issue involves improper input validation and weaknesses in several security controls including inactive-agent hour filtering, SQL identifier validation, metadata ownership checks, blocking unauthorized SQL metadata access, secure handling of outbound worker secrets, SMTP envelope/header validation, and TLS certificate verification. These flaws could lead to integrity violations and partial denial of service. The vulnerability has been patched in the stated versions.
NextCRM version 0.12.1 has an improper privilege management vulnerability in its MCP product tools API. Authenticated users with low privileges can perform product creation, modification, archiving, or soft-deletion via the /api/mcp/mcp endpoint without proper role checks. This allows unauthorized write access to the shared CRM product catalog. The issue is fixed in version 0.12.3.
NextCRM version 0.12.1 contains an improper access control vulnerability in its MCP campaign tools. Authenticated users with valid MCP API tokens can bypass authorization checks and access or modify campaigns they do not own. This includes reading, updating, deleting campaigns, modifying templates and steps, and controlling campaign delivery. The issue is fixed in version 0.12.2.
An improper access control vulnerability exists in the Page Builder CK extension for Joomla versions prior to 3.6.2. This flaw allows unauthorized access to frontend page list views, potentially exposing sensitive content or functionality. The vulnerability is identified as CWE-284 and carries a critical severity rating with a CVSS score of 9.1. No official patch or remediation guidance has been provided yet by the vendor.
The Quix Page Builder Pro extension for Joomla versions 1.0 through 6.2.0 suffers from an improper access control vulnerability. This flaw allows authenticated users to upload media files without having the necessary media management permissions. The vulnerability is identified as CWE-284 and has a high severity rating with a CVSS score of 8.7. No official patch or remediation guidance is currently available from the vendor.
CVE-2026-46415 is an improper access control vulnerability in the caddy-defender plugin for Caddy. Versions prior to 0.10.1 use the immediate peer IP address (RemoteAddr) instead of the resolved client IP when behind trusted proxies, allowing clients from blocked IP ranges to bypass IP-based blocking. This affects deployments using trusted proxies, CDNs, or load balancers. The issue is fixed in version 0.10.1 by using the resolved client IP when available. No complete workaround exists in affected versions except enforcing IP blocking at the proxy or edge layer. Deployments without intermediate proxies are not affected.
The PayPlus Payment Gateway WordPress plugin before 8.2.2 does not perform authorization or order-ownership validation in one of its AJAX actions available to unauthenticated users, allowing them to tamper with the payment-related metadata of arbitrary WooCommerce orders.
A flaw was found in the organization management component of Keycloak. A delegated administrator with permission to manage organizations can create an invitation for a non-existent email address and then retrieve the secret registration link directly through the application programming interface. By using this link, the administrator can create new user accounts and add them to the organization without having the required user management permissions or access to the invited email account. This allows an administrator to bypass security boundaries and add unauthorized members to an organization.
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 3.7.15 and 4.0.6, the allow-list fix for CVE-2026-31892 is incomplete because workflow/util/merge.go ValidateUserOverrides and SanitizeUserWorkflowSpec walk only the top-level fields of WorkflowSpec via reflection, and WorkflowSpec.ArtifactGC is allow-listed wholesale; the struct behind that field, WorkflowLevelArtifactGC, has a PodSpecPatch sub-field whose contents flow unmodified into util.ApplyPodSpecPatch on the artifact-GC pod, the same sink the original fix closed for WorkflowSpec.PodSpecPatch, so a user submitting a Workflow under templateReferencing: Strict or Secure (against a referenced WorkflowTemplate that declares an output artifact and setting spec.artifactGC.strategy: OnWorkflowCompletion) can still inject an arbitrary strategic merge patch into the artifact-GC pod, including hostPath volumes, privileged: true, arbitrary image and command, and hostNetwork: true, defeating the stated purpose of Strict/Secure reference mode. This issue is fixed in versions 3.7.15 and 4.0.6.