CVE-2025-62155: QuantumNous new-api · Server-Side Request Forgery (SSRF)
Affects QuantumNous new-apiSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 0.9.6 soon.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.9.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade quantumnous/new-api to 0.9.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubquantumnous/new-apipkg:github/quantumnous/new-apiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately upgrade QuantumNous new-api to version 0.9.6 or later, which contains the patch addressing the SSRF bypass via HTTP redirects. 2. Implement strict network segmentation and firewall rules to limit the new-api server’s ability to make outbound requests to sensitive internal resources. 3. Deploy web application firewalls (WAFs) with custom rules to detect and block suspicious SSRF patterns, including unusual redirect chains. 4. Monitor logs for unexpected outbound HTTP requests and 302 redirect responses from the new-api server to identify potential exploitation attempts. 5. Conduct regular security assessments and penetration testing focusing on SSRF vectors and redirect handling in the new-api environment. 6. Educate development and security teams on the risks of incomplete SSRF mitigations, emphasizing validation of all redirect targets. 7. Where possible, disable or restrict HTTP redirects in the new-api configuration to reduce attack surface. 8. Employ network-level egress filtering to prevent unauthorized internal resource access even if SSRF is attempted. These measures combined will reduce the risk of exploitation and limit potential damage.
Description
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to version 0.9.6, a recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur. Because the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet. This issue has been patched in version 0.9.6.