Skip to main content
Vulnerability Database/CVE-2026-108856

CVE-2026-108856: UnicomAI Wanwu Auth Bypass Vulnerability

CVE-2026-108856 is an authorization bypass flaw in UnicomAI Wanwu that allows authenticated users to mint AppKeys for other users' MCP servers. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-108856 Overview

CVE-2026-108856 is an authorization bypass vulnerability in UnicomAI Wanwu through version 0.6.5. The flaw resides in the POST /v1/appspace/app/key endpoint, which fails to validate that the authenticated caller owns the Model Context Protocol (MCP) server referenced in the request. An authenticated user can mint an AppKey bound to another user's MCP server by supplying the victim's MCP server UUID with appType=mcpserver. The attacker can then open MCP sessions and invoke the victim's tools using the victim's upstream authentication context. The weakness is classified as Insecure Direct Object Reference [CWE-639].

Critical Impact

Authenticated attackers can issue valid AppKeys against other tenants' MCP servers and invoke tools under the victim's upstream credentials.

Affected Products

  • UnicomAI Wanwu through 0.6.5
  • app-service AppKey ORM layer (internal/app-service/client/orm/app_key.go)
  • bff-service OpenAPI authentication middleware (internal/bff-service/server/http/middleware/auth_openapi.go)

Discovery Timeline

  • 2026-10-11 - CVE-2026-108856 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-108856

Vulnerability Analysis

UnicomAI Wanwu exposes an AppKey minting endpoint intended to let a user generate credentials for applications and MCP servers they own. The endpoint accepts an appType discriminator and a resource UUID from the request body. When appType is set to mcpserver, the service persists an AppKey record that maps the caller's identity to the supplied MCP server UUID. The code path does not cross-check that the UUID belongs to a resource owned by the authenticated caller. As a result, the minted AppKey is treated as a legitimate credential for the targeted MCP server during subsequent OpenAPI calls. The downstream MCP session handler trusts the AppKey-to-server binding and routes tool invocations using the victim's stored upstream authentication.

Root Cause

The root cause is a missing ownership check in the AppKey creation flow. Authentication is enforced on the request, but authorization at the object level is absent, matching the pattern described in [CWE-639]. The persistence layer in app_key.go writes the attacker-supplied mcpserver UUID without validating it against the caller's resource scope.

Attack Vector

Exploitation requires network access and valid low-privilege credentials on a Wanwu instance. The attacker submits a crafted POST /v1/appspace/app/key request containing a victim-owned MCP server UUID and appType=mcpserver. The server returns an AppKey that the attacker uses to open an MCP session against the victim's server and call its exposed tools. See the VulnCheck Advisory: Wanwu Bypass and the HackMD CVE Analysis: Wanwu MCP Key for the full request/response walkthrough.

No verified public exploit code is referenced in the advisory. See the GitHub Code Snippet: App Key and the GitHub Code Snippet: Auth Middleware for the vulnerable code paths.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-108856

Indicators of Compromise

  • POST /v1/appspace/app/key requests where the appType field is mcpserver and the referenced UUID is not owned by the requesting user ID.
  • Newly created AppKey records whose caller user_id does not match the owner of the bound mcpserver resource.
  • MCP session opens or tool invocations authenticated by an AppKey whose creator differs from the MCP server owner.

Detection Strategies

  • Query the AppKey table and join against MCP server ownership to flag any key where appkey.user_id != mcpserver.owner_id.
  • Add application-layer logging on /v1/appspace/app/key to capture appType, resource UUID, caller identity, and source IP for review.
  • Correlate AppKey creation events with the first MCP session that uses the key to spot cross-tenant resource access.

Monitoring Recommendations

  • Forward Wanwu app-service and bff-service logs to a centralized analytics pipeline for ownership-mismatch alerting.
  • Alert on bursts of AppKey minting from a single account against multiple distinct MCP server UUIDs.
  • Track MCP tool invocation volumes per key and flag deviations from historical baselines for that tenant.

How to Mitigate CVE-2026-108856

Immediate Actions Required

  • Restrict access to /v1/appspace/app/key to trusted administrative users until a patched version is deployed.
  • Audit existing AppKey records for appType=mcpserver entries whose creator does not own the referenced MCP server and revoke mismatched keys.
  • Rotate upstream credentials configured on MCP servers that may have been accessed by attacker-minted AppKeys.

Patch Information

No fixed version is listed in the NVD entry at the time of publication. The vulnerability affects UnicomAI Wanwu through 0.6.5. Monitor the GitHub Repository for Wanwu and the VulnCheck Advisory: Wanwu Bypass for a vendor-released fix.

Workarounds

  • Deploy a reverse proxy or API gateway rule that rejects POST /v1/appspace/app/key requests when the body includes an mcpserver UUID not previously associated with the authenticated principal.
  • Patch the app-service AppKey creation handler locally to call an ownership check against the MCP server registry before writing to the database.
  • Disable the mcpserver AppKey minting path entirely if MCP tool exposure is not required in the environment.
bash
# Example gateway rule (nginx) to block cross-tenant minting attempts
# Reject POST /v1/appspace/app/key when request body claims appType=mcpserver
location = /v1/appspace/app/key {
    if ($request_method = POST) {
        access_by_lua_block {
            ngx.req.read_body()
            local body = ngx.req.get_body_data() or ""
            if body:find('"appType"%s*:%s*"mcpserver"') then
                ngx.log(ngx.WARN, "Blocked mcpserver AppKey mint attempt")
                return ngx.exit(403)
            end
        }
    }
    proxy_pass http://wanwu_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.