MCP Server Exposure via Insecure Default Binding on alibabacloud-rds-openapi-mcp-server

published 2026-07-28 3mo ago modified 2026-10-24 18d ago also EUVD-2026-49727

cvss: 5.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits: 0; none known

Improper exposure of the MCP server in alibabacloud-rds-openapi-mcp-server allows remote attackers to invoke exposed MCP tools via network access to an MCP endpoint listening on all network interfaces by default.

Is CVE-2026-9680 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 3mo ago (2026-07-28)

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Affected products

Alibaba Alibaba Cloud RDS OpenAPI MCP Server

Classification

Weakness

CWE-1188 Initialization of a Resource with an Insecure Default

References

github.com /aliyun/alibabacloud-rds-openapi-mcp-server

Sources

CVE List CVE-2026-9680
NVD CVE-2026-9680

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.