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

CVE-2026-5470

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-03
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

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 mixelpixx Google-Research-MCP 1e062d7bd887bfe5f6e582b6cc288bb897b35cf2/ca613b736ab787bc926932f59cddc69457185a83. This issue affects the function extractContent of the file src/services/content-extractor.service.ts of the component Model Context Protocol Handler. The manipulation of the argument URL leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. 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

This is a Server-Side Request Forgery (SSRF) vulnerability in the extractContent function within src/services/content-extractor.service.ts of the Model Context Protocol Handler. The function accepts a URL parameter that can be manipulated by an attacker to make the server request arbitrary URLs, potentially accessing internal services, cloud metadata endpoints, or internal network resources.

MitigationImplement strict URL allowlisting to only permit requests to trusted domains, validate URL schemes (whitelist http/https), implement request timeouts, and disable redirect following for untrusted URLs. Consider adding authentication barriers for internal-facing endpoints.

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. Identify if Model Context Protocol Handler content-extractor service is running
    Review running services or processes related to 'Model Context Protocol', 'MCP', or 'content-extractor'. Check for any service exposing endpoints that handle URL-based content extraction.
    Affected if The content-extractor service of MCP Handler is installed and running on the system.
  2. Locate and verify the installed version of the MCP Handler
    Check the installed package or application version for any Model Context Protocol Handler component. Compare the version string against publicly disclosed affected version ranges if available.
    Affected if The installed version falls within any affected version range that has been documented for this CVE.
  3. Determine if the extractContent function is exposed via API or CLI
    Review the service configuration, API endpoints, or command-line interfaces to identify if the extractContent function is publicly or internally accessible. Check for any endpoint accepting URL parameters.
    Affected if The extractContent function is enabled and accepts user-supplied URL input without additional authentication or validation layers.
  4. Inspect network logs for suspicious outbound requests originating from the service
    Review HTTP access logs, proxy logs, or network flow logs for any requests made by the content-extractor service to unexpected internal IP ranges (e.g., 127.0.0.1, 10.0.0.0/8, 169.254.169.254) or external untrusted domains.
  5. Review application or service configuration for URL validation settings
    Examine configuration files or environment settings related to the content-extractor service. Check if URL allowlist or domain restriction mechanisms are defined and actively enforced.
    Affected if No URL allowlist is configured, or the allowlist is missing entries for expected trusted domains, allowing arbitrary URL input.

A system is affected if the Model Context Protocol Handler content-extractor service is running with the extractContent function exposed and lacking proper URL 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 URL allowlisting to only permit requests to trusted domains, validate URL schemes (whitelist http/https), implement request timeouts, and disable redirect following for untrusted URLs. Consider adding authentication barriers for internal-facing endpoints.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5470 — 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-5470 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