Skip to content

AAK-MCP-UNLA-CVE-2026-108865-001: Unla gateway image through v0.10.0: the built-in OAuth2 server issues tokens without authenticating anyone (no fixed release)

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
UnlaOAuthServerIssuesUnauthenticatedTokens

What it detects

Unla (AmoyLab/Unla, formerly mcp-gateway) is a Go MCP gateway that ships as container images: ghcr.io/amoylab/unla/allinone, ghcr.io/amoylab/unla/mcp-gateway, and the Aliyun mirror registry.ap-southeast-1.aliyuncs.com/amoylab/unla-allinone its Chinese README names. Its built-in OAuth2 server never authenticates a resource owner: /authorize issues a code to any registered client without asking who the user is, and /token exchanges it. So an unauthenticated attacker can register a client, get a code and exchange it for a valid access token, which opens the OAuth2-protected MCP prefixes, the upstream APIs Unla proxies and the credentials it injects into them (CVE-2026-108865, CVSS 3.1 8.2, CWE-287). The OAuth2 server arrived in v0.6.0, the amoylab/unla images start at v0.7.0, and v0.10.0, the newest release, still issues codes this way. internal/auth/oauth.go has not changed since 2025-10-11, so there is no fixed release.

How to fix

There is no fixed release. Put an authenticating reverse proxy in front of Unla's /authorize, /token and its OAuth2-protected MCP prefixes, and keep the gateway off untrusted networks. If an instance was reachable, rotate the upstream credentials it injects. Pin the first fixed release once it ships.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-UNLA-CVE-2026-108865-001

Limitations

Reads the three Unla image names in compose files, Kubernetes manifests, Helm values, Dockerfiles and MCP configs, up to and including v0.10.0, and latest, which was the v0.10.0 digest on 2026-10-13. The main tag and commit tags state no version and are not reported, and images from before the rename (mcp-ecosystem/mcp-gateway) are not read. The pin reads the image tag, not the gateway's configuration, so an instance with no OAuth2-protected MCP prefix is reported too.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-UNLA-CVE-2026-108865-001.md: the page then shows that text, with the registry reference appended under it.