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

CVE-2026-7146

HIGH · 7.3 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 AlejandroArciniegas mcp-data-vis up to de5a51525a69822290eaee569a1ab447b490746d. Affected by this vulnerability is the function axios of the file src/servers/web-scraper/server.js of the component HTTP Request Handler. Such manipulation leads to server-side request forgery. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

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 · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the mcp-data-vis project's web-scraper component. The axios function in src/servers/web-scraper/server.js allows unvalidated user input to be used in HTTP requests, enabling attackers to make the server request arbitrary URLs, potentially accessing internal services or cloud metadata endpoints.

MitigationImplement strict input validation on URLs passed to the axios function, using an allowlist approach for permitted domains or URL patterns, and validate that requests are not directed to internal/private network addresses (e.g., localhost, 127.0.0.1, private IP ranges).

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the mcp-data-vis project
    Search your codebase or node_modules for the 'mcp-data-vis' package directory, or grep for files containing 'web-scraper' in your project structure
    Affected if The mcp-data-vis project with a web-scraper component is present in your environment
  2. Find the vulnerable server.js file
    Locate the file at src/servers/web-scraper/server.js within the mcp-data-vis package or your project
    Affected if The file src/servers/web-scraper/server.js exists in your environment
  3. Inspect axios usage in the web-scraper
    Open src/servers/web-scraper/server.js and examine how the axios function is called - look for places where user input flows directly into axios request URL parameters without validation
    Affected if The code contains axios calls that accept user-supplied URLs without validation or allowlist checks
  4. Check if user input reaches the vulnerable axios call
    Trace the data flow in server.js - identify function parameters or API endpoints that accept URL input and are passed to axios without validation functions
    Affected if User-controllable input (request parameters, query strings, body data) is passed directly to axios without sanitization or allowlist validation
  5. Verify if the web-scraper endpoint is exposed
    Check your application's routes or API definitions to confirm the web-scraper endpoint is registered and accessible
    Affected if The web-scraper functionality is exposed via a reachable API endpoint or route

You are affected if the mcp-data-vis web-scraper component is present and its server.js file contains axios calls that accept user-supplied URLs without validation or allowlist filtering.

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 input validation on URLs passed to the axios function, using an allowlist approach for permitted domains or URL patterns, and validate that requests are not directed to internal/private network addresses (e.g., localhost, 127.0.0.1, private IP ranges).

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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