dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-15501

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security vulnerability has been detected in AstrBotDevs AstrBot up to 4.25.2. Affected by this issue is the function ToolsRoute.test_mcp_connection of the file astrbot/dashboard/routes/tools.py of the component MCP Test Endpoint. The manipulation of the argument mcp_server_config.url leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in AstrBot's MCP test endpoint. The function ToolsRoute.test_mcp_connection in astrbot/dashboard/routes/tools.py accepts a user-controlled URL parameter (mcp_server_config.url) without proper validation, allowing attackers to make the server request arbitrary URLs. This can enable access to internal services, cloud metadata endpoints, or internal network reconnaissance.

MitigationImplement strict allowlist-based URL validation for the mcp_server_config.url parameter, restrict outbound network connections from the server, and apply network segmentation to prevent the application server from accessing internal resources or cloud metadata services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate AstrBot installation and vulnerable file
    Search for the file astrbot/dashboard/routes/tools.py in your environment. This file contains the vulnerable function ToolsRoute.test_mcp_connection.
    Affected if The file exists and contains the test_mcp_connection function handling mcp_server_config.url parameter
  2. Identify installed AstrBot version
    Run 'pip show astrbot' or check your package manager for the installed AstrBot version. Compare against any available fixed version.
    Affected if The installed version is unpatched and contains the vulnerable code pattern without URL validation logic
  3. Verify MCP test endpoint is accessible
    Check if the /tools/mcp/test or equivalent endpoint is exposed in your AstrBot dashboard routing configuration. Inspect the routes registration in your deployment.
    Affected if The MCP test endpoint is exposed without authentication or with insufficient access controls
  4. Confirm mcp_server_config parameter handling
    Examine the source code in tools.py to verify the test_mcp_connection function accepts a user-controlled URL via mcp_server_config.url without proper validation or allowlisting.
    Affected if The code accepts arbitrary URLs in the mcp_server_config.url parameter without validation before making outbound requests
  5. Check network exposure of the service
    Determine if the AstrBot dashboard service is accessible from untrusted networks. Review firewall rules and reverse proxy configuration.
    Affected if The service is externally accessible, allowing attackers to trigger SSRF requests to internal endpoints or cloud metadata services

Your environment is affected if AstrBot is installed with the vulnerable tools.py file containing the unauthenticated or poorly secured test_mcp_connection endpoint that accepts arbitrary URLs without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based URL validation for the mcp_server_config.url parameter, restrict outbound network connections from the server, and apply network segmentation to prevent the application server from accessing internal resources or cloud metadata services.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15501 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data