# CVE-2026-115750: mcp-from-openapi from 2.5.0 before 2.9.0 Credential Leak via Cross-Origin Redirects


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-3gr3-m4x5-3fpp

## What is CVE-2026-115750?

CVE-2026-115750 is a medium-severity vulnerability in agentfront mcp-from-openapi, published on 23 Oct 2026. 

### Official description

mcp-from-openapi from 2.5.0 before 2.9.0 contains a credential exposure vulnerability that allows attackers to capture Authorization and Cookie headers because safeFetch() forwards them on cross-origin redirects. Attackers controlling a spec host or abusing an open redirect can redirect fromURL() spec requests to their own origin to steal bearer tokens or cookies.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-115750 being exploited?

There is no known exploitation of CVE-2026-115750 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115750 is a medium-severity vulnerability in agentfront mcp-from-openapi, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115750 in the wild and no public exploit code.

Affected product: agentfront mcp-from-openapi. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-115750/ (Markdown: https://insights.sbomify.com/CVE-2026-115750/index.md)
```

## Sources

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

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