SSRF (Server-Side Request Forgery) in TencentCloudBase CloudBase-MCP (CVE-2026-7221)
Summary
SSRF in TencentCloudBase CloudBase-MCP (CVE-2026-7221). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability was found in TencentCloudBase CloudBase-MCP up to 2.17.0. Affected is the function openUrl of the file mcp/src/interactive-server.ts of the component open-url API Endpoint. The manipulation of the argument req.body.url results in server-side request forgery. It is possible to launch the attack remotely. The exploit has been made public and could be used. Upgrading to version 2.17.1 is able to address this issue. The patch is identified as 3f678a1e7bd400cd76469d61024097d4920dc6b5. It is recommended to upgrade the affected component.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-7221 has been found in TencentCloudBase CloudBase-MCP.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "TencentCloudBase CloudBase-MCP CVE-2026-7221" on the vendor's site.
CVE-2026-7221 (TencentCloudBase CloudBase-MCP) — CWE-918 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in TencentCloudBase CloudBase-MCP.
Check the vendor advisory for the affected versions of TencentCloudBase CloudBase-MCP.
Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで TencentCloudBase CloudBase-MCP を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com