# CVE-2026-42339: New API: SSRF Filter Bypass via 0.0.0.0


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-v5c3-6wvc-pc2q, GO-2026-5652

## What is CVE-2026-42339?

CVE-2026-42339 is a high-severity vulnerability in QuantumNous new-api, published on 8 May 2026. 

### Official description

New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. In versions 0.11.9-alpha.1 and prior, the SSRF protection introduced in v0.9.0.5 (CVE-2025-59146) and hardened in v0.9.6 (CVE-2025-62155) does not block the unspecified address 0.0.0.0. A regular (non-admin) user holding any valid API token can send a multimodal request to /v1/chat/completions, /v1/responses, or /v1/messages with 0.0.0.0 as the image/file URL host, bypassing the private-IP filter and causing the server to issue HTTP requests to localhost. This constitutes at minimum a blind SSRF; when the request is routed through an AWS/Bedrock Claude adaptor, the fetched content is inlined into the model response, upgrading it to a full-read SSRF. At time of publication, there are no publicly available patches.

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

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

3 open source packages ship an affected version, including github.com/QuantumNous/new-api. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/QuantumNous/new-api` | Go | All versions | None |
| `github.com/QuantumNous/new-api` | Go | All versions to 0.11.9-alpha.1 | None |
| `github.com/QuantumNous/new-api` | Go | All versions to 0.11.9-alpha.1 | None |

Products: Newapi New Api.

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

Upgrade to a fixed version.

## Is CVE-2026-42339 being exploited?

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

## Other vulnerabilities in QuantumNous new-api

- [CVE-2025-55573](https://insights.sbomify.com/CVE-2025-55573/): Cross-site scripting in n/a (high 8.8)
- [CVE-2026-33655](https://insights.sbomify.com/CVE-2026-33655/): New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs (high 7.7)
- [CVE-2026-25802](https://insights.sbomify.com/CVE-2026-25802/): New API has Potential XSS in its MarkdownRenderer component (high 7.6)
- [CVE-2026-41432](https://insights.sbomify.com/CVE-2026-41432/): New API: Stripe Webhook Signature Bypass via Empty Secret Enables Unlimited Quota Fraud (high 7.1)
- [CVE-2026-25591](https://insights.sbomify.com/CVE-2026-25591/): New API has an SQL LIKE Wildcard Injection DoS via Token Search (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42339 is a high-severity vulnerability in QuantumNous new-api, published on 8 May 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42339 exists.

Affected packages and fixed versions:
- github.com/QuantumNous/new-api (Go): affected all versions; no fix listed
- github.com/QuantumNous/new-api (Go): affected all versions up to 0.11.9-alpha.1; no fix listed
- github.com/QuantumNous/new-api (Go): affected all versions up to 0.11.9-alpha.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-42339/ (Markdown: https://insights.sbomify.com/CVE-2026-42339/index.md)
```

## Sources

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

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