# CVE-2026-5832: atototo api-lab-mcp HTTP http-server.ts test_http_endpoint server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the api-lab-mcp library to access internal resources via the HTTP interface.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-crh9-3gjh-m6gc

## What is CVE-2026-5832?

CVE-2026-5832 is a medium-severity server-side request forgery vulnerability in atototo api-lab-mcp, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-5832?

2 open source packages ship an affected version, including api-lab-mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `api-lab-mcp` | npm | All versions to 0.2.1 | None |
| `api-lab-mcp` | npm | All versions to 0.2.1 | None |

## How do I fix CVE-2026-5832?

No fix has been published for CVE-2026-5832 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5832 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5832 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5832 and fix it if it is affected.

What it is: CVE-2026-5832 is a medium-severity server-side request forgery vulnerability in atototo api-lab-mcp, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5832 exists.

Affected packages and fixed versions:
- api-lab-mcp (npm): affected all versions up to 0.2.1; no fix listed
- api-lab-mcp (npm): affected all versions up to 0.2.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5832/ (Markdown: https://insights.sbomify.com/CVE-2026-5832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5832
- OSV: https://osv.dev/vulnerability/CVE-2026-5832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5832/
Summaries are generated and may contain mistakes; the official description above is the record.