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

CVE-2026-5607

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-06
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 imprvhub mcp-browser-agent up to 0.8.0. This impacts the function CallToolRequestSchema of the file src/handlers.ts of the component URL Parameter Handler. The manipulation of the argument request.params.name/request.params.arguments leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. 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 · high confidence

This is a server-side request forgery (SSRF) vulnerability in imprvhub mcp-browser-agent up to version 0.8.0. The issue exists in the URL Parameter Handler component within the CallToolRequestSchema function in src/handlers.ts. Attackers can manipulate the request.params.name or request.params.arguments arguments to cause the server to make arbitrary HTTP requests to internal or external resources.

MitigationSince the vendor has not responded to disclosure, users should implement input validation/allowlisting on the URL parameter handler to restrict which URLs or endpoints can be accessed. Consider upgrading to a patched version once available, or implementing network segmentation to limit the impact of potential SSRF attacks.

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 imprvhub mcp-browser-agent is installed
    Search for mcp-browser-agent in installed packages, running processes, or service configurations. Common commands: npm list -g | grep mcp, pip list | grep mcp, or ps aux | grep mcp-browser-agent
    Affected if The software is present in the environment
  2. Determine the installed version of mcp-browser-agent
    Run the package manager command to check the version: npm list mcp-browser-agent, pip show mcp-browser-agent, or check package.json dependencies
    Affected if Version cannot be determined or is below the patched version (once released)
  3. Check if the CallToolRequestSchema endpoint is exposed
    Review web server configuration and routing to identify if CallToolRequestSchema or its endpoint is publicly or internally accessible. Check proxy_pass directives and route definitions
    Affected if The endpoint is accessible without authentication or validation controls
  4. Inspect request handling configuration for the vulnerable parameters
    Examine the application's configuration files and source code for how request.params.name and request.params.arguments are processed. Look for validation logic around these parameters
    Affected if No input validation or allowlisting is implemented for these parameters
  5. Review network configuration for outbound request capabilities
    Check firewall rules, proxy settings, and application network policies to determine if the server can make outbound HTTP/HTTPS requests to arbitrary URLs
    Affected if The application can initiate outbound connections to arbitrary URLs without restriction

A user is affected if imprvhub mcp-browser-agent is running and the CallToolRequestSchema function is accessible without proper input validation on request.params.name and request.params.arguments parameters.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not responded to disclosure, users should implement input validation/allowlisting on the URL parameter handler to restrict which URLs or endpoints can be accessed. Consider upgrading to a patched version once available, or implementing network segmentation to limit the impact of potential SSRF attacks.

Recommended fix Moderate confidence

latest version > 0.8.0 (check GitHub releases for fixed version)

  1. 1. Identify the current version of imprvhub mcp-browser-agent in use by checking package.json or package-lock.json
  2. 2. Check the official GitHub repository (github.com/imprvhub/mcp-browser-agent or similar) for the latest release version
  3. 3. Upgrade to the latest available version that addresses the SSRF vulnerability in src/handlers.ts
  4. 4. Verify the upgrade by reviewing the changelog or release notes for security fixes
  5. 5. Test the application to ensure the URL parameter handling no longer allows arbitrary server-side requests

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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