Executive Summary

CVE-2026-7146 is a Server-Side Request Forgery (SSRF) vulnerability found in the mcp-data-vis project, specifically in the HTTP Request Handler component using the axios library in the file src/servers/web-scraper/server.js.

The vulnerability arises because the function that validates URLs before making HTTP requests does not comprehensively block all sensitive internal IP address ranges. While it blocks some local addresses like localhost and certain private IP ranges, it fails to block others such as 172.16.0.0/12, 169.254.0.0/16, and IPv6 loopback or link-local addresses.

This incomplete validation allows an attacker who can invoke certain exposed server methods to cause the server to send HTTP requests to arbitrary internal or external resources, potentially accessing sensitive internal services.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can impact you by allowing an attacker to make the vulnerable server send requests to internal or sensitive network resources that are normally inaccessible externally.

The security impact is rated high for confidentiality because attackers may access internal HTTP services, administrative interfaces, or cloud metadata endpoints, potentially exposing sensitive information.

Integrity and availability impacts are considered low to medium depending on what internal services are accessed and how they might be abused.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves server-side request forgery (SSRF) through the axios function in the web scraper server component. Detection can focus on monitoring for unusual outbound HTTP requests initiated by the vulnerable handlers such as scrape_page, api_request, extract_links, get_page_metadata, and download_content.

You can detect exploitation attempts by inspecting logs for requests invoking these handlers with URLs pointing to internal IP ranges that should normally be inaccessible, such as 172.16.0.0/12, 169.254.0.0/16, or cloud metadata service IPs like 169.254.169.254.

Network monitoring tools or intrusion detection systems can be configured to alert on outbound HTTP requests to private or sensitive IP ranges originating from the server running the vulnerable component.

Suggested commands to detect suspicious activity include:

• Using tcpdump or tshark to capture outbound HTTP requests from the server: tcpdump -i <interface> 'tcp dst port 80 or 443'
• Filtering logs for suspicious URLs or IPs, e.g., grep for internal IP ranges in application logs or web server logs.
• Using curl or similar tools to test the vulnerable endpoints with crafted JSON-RPC calls to see if SSRF is possible, for example:
• curl -X POST http://<server>/rpc -H 'Content-Type: application/json' -d '{"method":"scrape_page","params":{"url":"http://169.254.169.254/latest/meta-data/"}}'

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include implementing strict validation and filtering of URLs passed to the axios HTTP request handler to prevent SSRF.

Specifically, you should:

• Implement a comprehensive allowlist for URL schemes, hosts, ports, and resolved IP addresses.
• Reject requests to loopback, RFC1918 private IP ranges (including 172.16.0.0/12), link-local, carrier-grade NAT, multicast, and cloud metadata IP ranges for both IPv4 and IPv6.
• Re-resolve and re-validate destination IP addresses after any redirects to prevent bypass.
• Restrict usage of the web-scraper tool to trusted callers only.

Additionally, monitor and block any suspicious outbound requests from the server to internal or sensitive IP addresses until a patch or fix is applied.

Useful 0 Not Useful 0

Compliance Impact

The vulnerability is a Server-Side Request Forgery (SSRF) that allows attackers to make the server send requests to arbitrary internal or external resources. This can lead to exposure of internal HTTP services, administrative interfaces, or metadata endpoints, resulting in a high confidentiality impact.

Such exposure of sensitive internal data could potentially lead to violations of data protection regulations like GDPR or HIPAA, which require strict controls over access to personal and sensitive information. The SSRF vulnerability may enable unauthorized access to confidential data, thereby affecting compliance with these standards.

Mitigations recommended include implementing comprehensive allowlists, rejecting requests to private and sensitive IP ranges, and restricting tool usage to trusted callers, which are necessary steps to maintain compliance with security requirements in these regulations.

Useful 0 Not Useful 0