In OpenStack Swift through 2.38.0, S3API middleware does not enforce that semantic x-amz-* headers are covered by the SigV4 signature on presigned URL requests. An attacker who obtains a presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, causing Swift to perform a server-side copy from an arbitrary source object using the signer's authorization context. The attacker can read any object the signer has access to, provided the target project_id, container name, and object name are known. This affects all deployments using the default s3_acl=false configuration.
In OpenStack Neutron before 28.0.2, the subnetpool onboarding API does not verify ownership of the target subnets. An authenticated user can onboard subnets from another project's shared network into their own subnetpool, mutating the victim's subnet state and altering L3 routing and address scope behavior for victim routers.
FlowiseAI Flowise versions prior to 3.1.3 contain an incorrect authorization vulnerability in their OAuth2 credential endpoints. The endpoints authorize, callback, and refresh query credentials by ID without filtering by workspace ID, and some handlers are accessible without authentication. This flaw allows authenticated users to initiate OAuth2 flows using credentials from other workspaces and unauthenticated attackers to forge OAuth2 callbacks or refresh tokens for any credential. The issue is resolved in version 3.1.3.
CVE-2026-70472 is an improper authorization vulnerability in FlowiseAI Flowise versions prior to 3.1.3. The issue allows an attacker to use a client-controlled credential parameter to access credentials belonging to other workspaces without proper authorization checks. This can lead to unauthorized use of OpenAI API keys, modification or deletion of victim vector stores and files, and potential billing impact on the victim's OpenAI account. The vulnerability violates multi-tenant boundaries and is fixed in version 3.1.3.
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise injects $vars into the code execution sandbox without requiring variables:view, bypassing the permission-protected Variables API. Variables for the active workspace are fetched at packages/components/src/utils.ts and runtime variables are resolved from server environment variables, while the official variables route enforces variables:view. A user or API key that is denied variables:view can call /api/v1/node-custom-function and receive $vars pre-populated with all variables for the workspace, including Variable.name to Variable.value static variables and Variable.name to process.env[Variable.name] runtime variables. This can expose secrets such as database passwords, JWT secrets, SMTP passwords, and cloud keys, depending on the workspace Variables configuration. This issue is fixed in version 3.1.3.
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, `DELETE /api/v1/chatflows/:id` authorized requests with checkAnyPermission('chatflows:delete,agentflows:delete'), so possession of either permission was sufficient to reach the delete path. The delete logic then resolved the target record only by id and workspaceId and did not validate the target resource type, allowing a caller with only agentflows:delete to delete a CHATFLOW and a caller with only chatflows:delete to delete an AGENTFLOW in the same workspace. This issue is fixed in version 3.1.3.
CVE-2026-64630 is a medium severity vulnerability in Veeam ONE that allows a low-privileged user to access report data beyond the intended scope of a shared report link. This is due to incorrect authorization controls (CWE-863). No specific affected versions or patches are currently identified.
CVE-2026-62927 is a high-severity authorization bypass vulnerability in Eclipse Milo versions 1.0.0 through 1.1.4. The Call service incorrectly dispatches mixed batches of method calls after authorization checks, allowing low-privileged or anonymous clients to execute methods that should be denied by batching them with allowed methods.
Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could exploit this vulnerability to gain elevated privileges. Exploitation of this issue does not require user interaction.
Chisel versions prior to 1.11.5 contain an authorization bypass vulnerability where authenticated clients can circumvent --authfile ACL restrictions. The ACL is only enforced during the initial handshake for declared remotes but not on subsequent SSH channels, allowing clients to tunnel traffic to arbitrary destinations reachable from the server. This issue has been fixed in version 1.11.5.
Apache NiFi 2.0.0 through 2.10.0 support creating, reading, and deleting Assets associated with Parameter Contexts through the REST API. The framework authorizes asset deletion against the owning Parameter Context using the supplied Parameter Context Identifier and Asset Identifier. The framework performed authorized based on the supplied Parameter Context Identifier without verifying the requested Identifier against the stored Identifier. Apache NiFi installations that do not implement different levels of authorization across Parameter Contexts are not subject to this vulnerability, because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.11.0 is the recommended mitigation, which verifies Parameter Context ownership of the requested Asset before deletion using the same strategy applied to Asset read operations.
Authorization handling for Parameter Context validation requests in Apache NiFi 1.10.0 through 2.10.0 allows clients with read access to submit proposed Parameter values. The proposed values override current configuration, enabling users with read access to invoke predefined component validation methods with alternative settings. Apache NiFi installations that do not implement different levels of authorization for viewing and modifying Parameter Context configuration are not subject to this vulnerability. Upgrading to Apache NiFi 2.11.0 is the recommended mitigation, requiring write access to submit Parameter Context validation requests.
Russh is a Rust SSH client & server library. Prior to 0.62.5, russh dispatches channel-scoped Handler callbacks for recipient channel IDs that were never opened or confirmed in russh/src/server/encrypted.rs, server_read_authenticated, and the exec_request callback. Version 0.62.5 fixes the issue.
Simply Schedule Appointments WordPress plugin versions before 1.6.12.11 contain an authorization flaw where users with Contributor role and above can access all customers' appointment data site-wide. This occurs because the plugin does not properly check capabilities on an administrative appointment-listing shortcode and fails to restrict results to authorized users only. The exposed data includes names, email addresses, phone numbers, and notes of customers.
CVE-2026-16540 is a high-severity vulnerability in the Simply Schedule Appointments WordPress plugin prior to version 1.6.12.6. It involves incorrect authorization that allows unauthenticated users to access personal data of all appointments on the site. Additionally, in premium editions, attackers can permanently delete appointment records. This vulnerability does not require user interaction or privileges to exploit.
Event Booking Manager for WooCommerce versions before 5.3.7 contain an authorization flaw that allows users with Contributor role and above to modify titles and publication status of posts and pages they do not own via quick-edit functionality.
The Simple Restrict WordPress plugin before 1.2.9 does not enforce its content-restriction permission check on the REST API the way it does on the front end, relying there on a generic capability check instead of the Simple Restrict WordPress plugin before 1.2.9's own permission system, allowing users with contributor-level access or above to read the content of restricted posts and pages they were never granted access to.
Incorrect authorization in the http_request tool in Strands Agents Tools before 0.8.2 might allow remote attackers to obtain credentials configured via HTTP_REQUEST_TOKEN_CONFIG by influencing the LLM to route requests through actor-controlled proxy infrastructure.
To remediate this issue, users should upgrade to version 0.8.2.
JS Help Desk WordPress plugin versions before 3.1.4 contain an authorization flaw where the plugin does not verify ownership of a targeted reply before allowing updates. This vulnerability permits any authenticated user with Subscriber role or higher to overwrite the content of any support-ticket reply on the site without proper authorization. The issue is classified as CWE-863 (Incorrect Authorization).
An improper authorization and security-boundary bypass vulnerability in the bigquery-execute-sql tool component of Google mcp-toolbox versions 0.16.1 through 1.4.0 allows an authenticated attacker to bypass allowedDatasets validation checks. The toolbox relies on the BigQuery dry-run API to enforce dataset restrictions, but due to a fail-open logic flaw, it bypasses validation when the API returns an empty array for specialized constructs. This allows the attacker to extract structural DDL schemas for explicitly excluded datasets via INFORMATION_SCHEMA, and access downstream federated row data via EXTERNAL_QUERY connections.