# CVE-2026-130750: Network-AI 5.11.0 before 5.17.2 CORS Misconfiguration via McpStreamableServer


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-5j7w-r89r-mrq2, GHSA-jw52-p54c-w7hj

## What is CVE-2026-130750?

CVE-2026-130750 is a medium-severity vulnerability in Jovancoding Network-AI, published on 18 Nov 2026. 

### Official description

Network-AI from 5.11.0 before 5.17.2 contains a CORS misconfiguration in McpStreamableServer that reflects localhost Origins into Access-Control-Allow-Origin regardless of bind interface. Attackers controlling a localhost-origin page or DNS-rebinding name can read unauthenticated /tools and /health responses, exposing tool catalogs and bridge metadata on non-loopback binds.

Weakness: CWE-346 (Origin Validation Error)

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

1 open source package ship an affected version, including network-ai.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `network-ai` | npm | `pkg:npm/network-ai` | From 5.11.0 | 5.17.2 |

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

Upgrade network-ai to 5.17.2 or later.

## Is CVE-2026-130750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130750 is a medium-severity vulnerability in Jovancoding Network-AI, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130750 in the wild and no public exploit code.

Affected packages and fixed versions:
- network-ai (npm): affected from 5.11.0; fixed in 5.17.2

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

## Sources

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

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