CVE-2025-65513: fetch-mcp v1.0.2 and before is vulnerable to Server-Side Request Forgery (SSRF) vulnerability, which allows at

Q: How do I fix CVE-2025-65513?

fetch mcp server: upgrade to newer than 1.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-65513 being exploited?

CVE-2025-65513 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-65513 affect?

CVE-2025-65513 affects fetch mcp server. Severity is high (CVSS 7.5). fetch-mcp v1.0.2 and before is vulnerable to Server-Side Request Forgery (SSRF) vulnerability, which allows attackers to bypass private IP validation and access internal network resources.

Q: How urgent is CVE-2025-65513?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2025-65513 is a high-severity flaw (CVSS 7.5) affecting fetch mcp server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

fetch-mcp v1.0.2 and before is vulnerable to Server-Side Request Forgery (SSRF) vulnerability, which allows attackers to bypass private IP validation and access internal network resources.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 61%)
CISA exploited list	No
Weakness	CWE-918
Published	2025-12-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: zcaceres

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-12-09 22:16 UTCPublished CVE record published
2026-06-17 09:55 UTCUpdated Record last modified

zcaceres fetch mcp server UPGRADE

Affected: <= 1.0.2

Fixed in: newer than 1.0.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy fetch-mcp-server || rpm -q fetch-mcp-server || fetch-mcp-server --version

2. UPGRADE to newer than 1.0.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fetch-mcp-server

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fetch-mcp-server

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-65513?

fetch mcp server: upgrade to newer than 1.0.2. Exact commands for each OS are on this page.

Is CVE-2025-65513 being exploited?

CVE-2025-65513 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-65513 affect?

CVE-2025-65513 affects fetch mcp server. Severity is high (CVSS 7.5). fetch-mcp v1.0.2 and before is vulnerable to Server-Side Request Forgery (SSRF) vulnerability, which allows attackers to bypass private IP validation and access internal network resources.

How urgent is CVE-2025-65513?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs