CVE-2026-74858
Received Received - Intake

Server-Side Request Forgery in Jae-Jae Fetcher-MCP

Vulnerability report for CVE-2026-74858, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-17

Last updated on: 2026-08-17

Assigner: VulDB

Description

A vulnerability has been found in jae-jae fetcher-mcp up to 0.3.9. Impacted is the function fetch_url/fetch_urls of the file /latest/meta-data/iam/security-credentials/ of the component URL Validation. Such manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The project was informed of the problem early through an issue report but has not responded yet.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-17
Last Modified
2026-08-17
Generated
2026-08-17
AI Q&A
2026-08-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
jae-jae fetcher-mcp to 0.3.9 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in the fetcher-mcp library up to version 0.3.9. It occurs due to insufficient URL validation in the fetch_url and fetch_urls functions. The only validation checks if the URL uses http or https, allowing attackers to bypass restrictions and access internal network addresses like loopback, private, or cloud metadata services. The validated URL is passed directly to Playwright for navigation, enabling the MCP server to fetch content from internal services.

Detection Guidance

Check if fetcher-mcp is running and inspect network logs for outbound requests to internal or metadata addresses like 127.0.0.1, 169.254.169.254, or RFC1918 ranges. Use tools like curl or netstat to verify if the service attempts to access unexpected local services.

Impact Analysis

An attacker could exploit this to make the vulnerable server fetch content from internal services, potentially exposing sensitive data or internal network information. For example, an attacker could host a local HTTP service on the MCP server and request it via fetch_url, receiving the response content. This could lead to unauthorized access to internal resources, data leaks, or further network reconnaissance.

Compliance Impact

This SSRF vulnerability could lead to unauthorized access to internal systems, potentially exposing sensitive data. For GDPR, this may violate principles of data protection and security. For HIPAA, it could risk unauthorized access to protected health information if internal services are compromised.

Mitigation Strategies

Update fetcher-mcp to the latest version if available. If not, disable the fetch_url and fetch_urls tools in the MCP server configuration. Restrict network access to the MCP server and monitor for unusual outbound connections.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-74858. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart