Quick answers
- Is CVE-2026-15501 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15501 being exploited in the wild.
- How severe is CVE-2026-15501?
- Medium severity, with a CVSS score of 6.3, published 12 July 2026.
- Which products and versions are affected?
- AstrBotDevs AstrBot <= 4.25.2.
- Is there a fix for CVE-2026-15501?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15501 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-15501?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in AstrBot up to version 4.25.2 within the `ToolsRoute.test_mcp_connection` function in `astrbot/dashboard/routes/tools.py`. The endpoint `POST /api/tools/mcp/test` accepts a JSON payload containing an `mcp_server_config.url` parameter which is passed to `_quick_test_mcp_connection` without sufficient validation of the scheme, hostname, or destination IP. An authenticated attacker can provide a malicious URL (e.g., targeting loopback or RFC1918 addresses) to probe internal network services or access cloud metadata endpoints. The vulnerability is exploitable even if the subsequent MCP handshake fails, as the initial HTTP request is issued by the `aiohttp` client during the connection test. As of the advisory date, the vendor has not responded to the disclosure.
Affected products
- AstrBotDevs AstrBot <= 4.25.2
Timeline
- 2026-06-01: disclosed: Initial researcher disclosure via GitHub Gist
- 2026-07-12: advisory: NVD/VulDB publication