CVE-2026-33655: CWE-918: Server-Side Request Forgery (SSRF) in QuantumNous new-api
QuantumNous new-api versions prior to 0.12.0-alpha.1 have a Server-Side Request Forgery (SSRF) vulnerability due to incomplete IP filtering in the default configuration. The vulnerability arises because hostname resolution and IP address validation were not enforced, allowing authenticated users to configure notification URLs that could target internal or metadata IP addresses. This issue is fixed in version 0.12.0-alpha.1.
AI Analysis
Technical Summary
The QuantumNous new-api, an LLM gateway and AI asset management system, had an SSRF vulnerability (CWE-918) before version 0.12.0-alpha.1. The default SSRF protection did not apply IP filtering to hostnames because the ApplyIPFilterForDomain setting was disabled by default. URL validation only checked domain allow/block rules without resolving hostnames to validate their IP addresses. This allowed authenticated users to specify Webhook, Bark, or Gotify notification URLs pointing to internal or metadata IP addresses. The vulnerability is addressed in version 0.12.0-alpha.1 by enabling proper IP filtering on resolved hostnames.
Potential Impact
An attacker with authentication privileges could exploit this SSRF vulnerability to make the server send requests to internal or metadata IP addresses, potentially exposing sensitive internal resources or metadata services. The CVSS score of 7.7 (high) reflects the network attack vector, low complexity, required privileges, no user interaction, and high confidentiality impact without integrity or availability impact.
Mitigation Recommendations
Upgrade QuantumNous new-api to version 0.12.0-alpha.1 or later, where the SSRF vulnerability is fixed by enabling IP filtering on resolved hostnames. Since this is an official fix, applying this update is the recommended remediation. Patch status is confirmed fixed in 0.12.0-alpha.1. No other mitigations are indicated by the vendor advisory.
CVE-2026-33655: CWE-918: Server-Side Request Forgery (SSRF) in QuantumNous new-api
Description
QuantumNous new-api versions prior to 0.12.0-alpha.1 have a Server-Side Request Forgery (SSRF) vulnerability due to incomplete IP filtering in the default configuration. The vulnerability arises because hostname resolution and IP address validation were not enforced, allowing authenticated users to configure notification URLs that could target internal or metadata IP addresses. This issue is fixed in version 0.12.0-alpha.1.
CVSS v3.1
Score 7.7high
Affected software
pkg:github/quantumnous/new-apiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The QuantumNous new-api, an LLM gateway and AI asset management system, had an SSRF vulnerability (CWE-918) before version 0.12.0-alpha.1. The default SSRF protection did not apply IP filtering to hostnames because the ApplyIPFilterForDomain setting was disabled by default. URL validation only checked domain allow/block rules without resolving hostnames to validate their IP addresses. This allowed authenticated users to specify Webhook, Bark, or Gotify notification URLs pointing to internal or metadata IP addresses. The vulnerability is addressed in version 0.12.0-alpha.1 by enabling proper IP filtering on resolved hostnames.
Potential Impact
An attacker with authentication privileges could exploit this SSRF vulnerability to make the server send requests to internal or metadata IP addresses, potentially exposing sensitive internal resources or metadata services. The CVSS score of 7.7 (high) reflects the network attack vector, low complexity, required privileges, no user interaction, and high confidentiality impact without integrity or availability impact.
Mitigation Recommendations
Upgrade QuantumNous new-api to version 0.12.0-alpha.1 or later, where the SSRF vulnerability is fixed by enabling IP filtering on resolved hostnames. Since this is an official fix, applying this update is the recommended remediation. Patch status is confirmed fixed in 0.12.0-alpha.1. No other mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-23T15:23:42.218Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a50252a68715ace43310ccb
Added to database: 07/09/2026, 22:48:10 UTC
Last enriched: 07/09/2026, 23:02:49 UTC
Last updated: 07/10/2026, 01:06:17 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.