Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-86173 – Unauthenticated SSRF – MindsDB (mindsdb) through 26.1.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86173 is a Server-Side Request Forgery (SSRF) vulnerability affecting MindsDB (the mindsdb Python package), impacting all versions through 26.1.0. The flaw resides in the web crawler handler’s CrawlerTable.list method, which allows unauthenticated attackers to make the MindsDB server fetch arbitrary, caller-supplied URLs. Because MindsDB’s crawler allowlist configuration is empty by default, exploitation requires no authentication and no prior access controls to bypass, earning the flaw a HIGH severity rating.

Technical details

  • Root cause: CrawlerTable.list accepts a caller-controlled URL parameter and passes it to the web crawling functionality without adequately restricting the target host, relying on an allowlist (web_crawling_allowed_sites) that is empty/permissive by default.
  • Trigger conditions: An attacker with network access to a MindsDB instance’s crawler-capable interface can submit a request specifying an arbitrary URL for the crawler to fetch, without needing to authenticate.
  • Attack vector: Network (AV:N) — remotely exploitable with low attack complexity and no privileges or user interaction required.
  • Impact: The server can be coerced into issuing outbound requests to internal-only services or cloud instance metadata endpoints (e.g., 169.254.169.254), potentially exposing internal network topology, internal service responses, or cloud credentials/metadata. The CVSS impact metrics indicate high confidentiality impact with no direct integrity or availability impact.

Affected software

  • MindsDB (PyPI package mindsdb), all versions 0 through 26.1.0

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • (A CVSS v4.0 score of 8.7 (HIGH) has also been assigned: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N)

Mitigation and recommended actions

  • Immediate: As of publication, no official patched release has been confirmed by the vendor for this specific issue. Security teams should monitor the MindsDB GitHub repository for a fixed release beyond 26.1.0 and upgrade as soon as one is available.
  • If no patch is available:
    • Explicitly configure the web_crawling_allowed_sites setting in config.json to a strict allowlist of only trusted, external domains that the crawler is permitted to fetch — do not leave this setting empty/unrestricted.
    • Block outbound access from the MindsDB host to internal/private IP ranges (RFC 1918) and cloud metadata endpoints (e.g., 169.254.169.254) at the network or firewall layer.
    • Restrict network exposure of MindsDB management/API interfaces to trusted internal networks only, and require authentication in front of the service (e.g., via a reverse proxy or VPN) until a vendor fix is confirmed.
    • Monitor outbound request logs from the MindsDB host for unexpected connections to internal addresses or metadata services.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge