Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62155: CWE-918: Server-Side Request Forgery (SSRF) in QuantumNous new-api

0
High
VulnerabilityCVE-2025-62155cvecve-2025-62155cwe-918
Published: Mon Nov 24 2025 (11/24/2025, 23:56:52 UTC)
Source: CVE Database V5
Vendor/Project: QuantumNous
Product: new-api

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.

AI-Powered Analysis

AILast updated: 12/02/2025, 00:30:23 UTC

Technical Analysis

CVE-2025-62155 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918 affecting QuantumNous new-api, an AI asset management and large language model gateway system. The vulnerability exists in versions prior to 0.9.6 due to an incomplete security fix that only applies restrictions to the initial URL request. Attackers can exploit HTTP 302 redirect responses to circumvent these restrictions, causing the server to make unauthorized requests to internal network resources. This bypass allows attackers to probe and potentially access sensitive intranet services that should be inaccessible externally. The vulnerability requires low privileges (PR:L) but no user interaction (UI:N), and the attack vector is network-based (AV:N), meaning it can be exploited remotely. The impact primarily compromises confidentiality (C:H), with limited integrity impact (I:L) and no availability impact (A:N). The scope is changed (S:C), indicating the vulnerability affects resources beyond the initially vulnerable component. Although no known exploits have been observed in the wild, the high CVSS score of 8.5 reflects the potential severity. The patch released in version 0.9.6 addresses this bypass by enforcing security restrictions on all redirected requests, closing the loophole. Organizations using QuantumNous new-api should urgently apply this patch to prevent exploitation. The vulnerability highlights the importance of comprehensive validation of all HTTP redirects in SSRF mitigation strategies.

Potential Impact

For European organizations, this SSRF vulnerability poses a significant risk to the confidentiality of internal network resources, including sensitive AI asset management data and potentially other intranet services. Exploitation could lead to unauthorized access to internal systems, data leakage, and reconnaissance that may facilitate further attacks. Given the increasing adoption of AI and LLM technologies in Europe, organizations relying on QuantumNous new-api could face targeted attacks aiming to exploit this flaw. Critical sectors such as finance, healthcare, and government agencies using this product may experience increased risk of data breaches. The vulnerability’s ability to bypass existing security controls via HTTP redirects complicates detection and mitigation. Additionally, the low privilege requirement and remote exploitability increase the likelihood of exploitation attempts. Although no active exploits are currently known, the vulnerability’s characteristics make it a high-priority threat that could be leveraged in multi-stage attacks against European infrastructure.

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-10-07T16:12:03.423Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6924f361c5f5f1e21b6201dc

Added to database: 11/25/2025, 12:08:01 AM

Last enriched: 12/2/2025, 12:30:23 AM

Last updated: 1/9/2026, 4:41:16 AM

Views: 84

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats