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

CVE-2026-5832

HIGH · 7.3 CVSS v3.1 Published 2026-04-09
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 weakness has been identified in atototo api-lab-mcp up to 0.2.1. This affects the function analyze_api_spec/generate_test_scenarios/test_http_endpoint of the file src/mcp/http-server.ts of the component HTTP Interface. This manipulation of the argument source/url causes server-side request forgery. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. 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

Server-side request forgery (SSRF) in the HTTP interface of api-lab-mcp (up to v0.2.1). The functions analyze_api_spec, generate_test_scenarios, and test_http_endpoint in src/mcp/http-server.ts accept user-controlled 'source' or 'url' arguments without proper validation, allowing attackers to make the server request arbitrary URLs.

MitigationImplement strict allowlist validation for URL/source inputs, restricting to expected domains or protocols; consider disabling the affected functions until a patched version is available; apply network segmentation to limit server outbound access.

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 api-lab-mcp installation
    Search for the file src/mcp/http-server.ts or check for api-lab-mcp in your project dependencies (package.json, requirements.txt, or similar). If using a package manager, run 'npm list api-lab-mcp' or equivalent.
    Affected if The api-lab-mcp package or http-server.ts file is present in your environment
  2. Identify the installed version
    Check the version field in package.json, pyproject.toml, or the installed package metadata. Compare against any available version tags in the repository.
    Affected if The installed version is unknown, unpatched, or predates the fix for this SSRF vulnerability
  3. Verify HTTP interface is enabled
    Inspect your application configuration or startup logs to confirm the HTTP server (src/mcp/http-server.ts) is actively serving requests. Look for port bindings or middleware registration.
    Affected if The HTTP interface is enabled and accessible to users or network attackers
  4. Confirm vulnerable endpoint exposure
    Check if the endpoints handling analyze_api_spec, generate_test_scenarios, or test_http_endpoint functions are exposed via the HTTP interface. Review route definitions or API gateway configuration.
    Affected if One or more of these functions are accessible via HTTP without authentication or additional validation layers
  5. Inspect parameter handling for source and url
    Examine the source code in src/mcp/http-server.ts or the running service to see how 'source' and 'url' parameters are processed. Look for lack of URL/host validation or allowlisting logic.
    Affected if The code accepts source or url parameters directly from user input without validating the target host or URL against an allowlist

You are affected if api-lab-mcp with the vulnerable HTTP interface is installed, the affected functions are exposed via HTTP, and URL/source parameters are accepted without host 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 allowlist validation for URL/source inputs, restricting to expected domains or protocols; consider disabling the affected functions until a patched version is available; apply network segmentation to limit server outbound access.

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-5832 — 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-5832 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