# CVE-2026-33655: New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs

> Authenticated users can bypass SSRF protections to access internal resources via notification URLs due to missing IP validation on hostnames.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-6qcr-qxgr-m7fv, GO-2026-5930

## What is CVE-2026-33655?

CVE-2026-33655 is a high-severity server-side request forgery vulnerability in QuantumNous new-api, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 0.12.0-alpha.1, the default SSRF protection configuration did not apply IP filtering to hostnames; with ApplyIPFilterForDomain disabled by default, URL validation checked domain allow/block rules but did not resolve a hostname and validate the resolved IP address, allowing authenticated users to configure Webhook, Bark, or Gotify notification URLs that point at an internal or metadata IP address. This issue is fixed in version 0.12.0-alpha.1.

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

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

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 | 0.12.0-alpha.1 |
| `github.com/QuantumNous/new-api` | Go | All versions | 0.12.0-alpha.1 |
| `github.com/QuantumNous/new-api` | Go | All versions | 0.12.0-alpha.1 |

Products: Newapi New Api.

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

Upgrade github.com/QuantumNous/new-api to 0.12.0-alpha.1 or later.

## Is CVE-2026-33655 being exploited?

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

## 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-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-42339](https://insights.sbomify.com/CVE-2026-42339/): New API: SSRF Filter Bypass via 0.0.0.0 (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-33655 and fix it if it is affected.

What it is: CVE-2026-33655 is a high-severity server-side request forgery vulnerability in QuantumNous new-api, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33655 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 0.12.0-alpha.1
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 0.12.0-alpha.1
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 0.12.0-alpha.1

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

## Sources

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

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