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: 11/25/2025, 00:21:52 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 this by leveraging HTTP 302 redirects to bypass the security controls, causing the server to make unauthorized requests to internal or otherwise restricted network resources. This can lead to unauthorized access to intranet services, potentially exposing sensitive data or enabling further internal attacks. The vulnerability requires low privileges (PR:L) but no user interaction (UI:N), and the attack vector is network-based (AV:N). The impact on confidentiality is high, as attackers can access internal endpoints, while integrity impact is low and availability is unaffected. The vulnerability has been publicly disclosed with a CVSS 3.1 score of 8.5, indicating a high severity level. Although no known exploits are currently reported in the wild, the nature of SSRF and the bypass of existing fixes make this a critical issue for affected deployments. The patch released in version 0.9.6 addresses the redirect bypass by enforcing security restrictions on redirected requests as well.

Potential Impact

For European organizations, this SSRF vulnerability poses a significant risk to the confidentiality of internal systems and data. Organizations using QuantumNous new-api in sectors such as finance, healthcare, government, and critical infrastructure could face unauthorized exposure of sensitive internal services, potentially leading to data breaches or lateral movement within networks. The ability to bypass existing security fixes via redirects increases the likelihood of exploitation, especially in environments where network segmentation or internal access controls are insufficient. Given the AI asset management context, attackers might also gain access to proprietary AI models or sensitive operational data. The vulnerability does not directly impact system availability or integrity but can serve as a foothold for further attacks. The lack of required user interaction and the network-based attack vector mean that attackers can exploit this remotely once they have low-level access, increasing the threat surface. European organizations with complex internal networks and reliance on QuantumNous products should consider this vulnerability a high priority for remediation.

Mitigation Recommendations

1. Upgrade QuantumNous new-api to version 0.9.6 or later immediately to apply the official patch that fixes the redirect bypass in SSRF protections. 2. Implement strict network segmentation and firewall rules to limit the new-api server's ability to make outbound requests to sensitive internal resources, minimizing the impact of potential SSRF exploitation. 3. Deploy web application firewalls (WAFs) with rules specifically designed to detect and block SSRF attempts, including those involving HTTP redirects. 4. Monitor logs for unusual outbound HTTP requests from the new-api server, especially those involving redirects or requests to internal IP ranges. 5. Conduct internal penetration testing focusing on SSRF vectors and redirect handling to validate the effectiveness of applied mitigations. 6. Restrict privileges of the new-api service account to the minimum necessary, reducing the potential impact if exploited. 7. Educate development and security teams about SSRF risks and ensure secure coding practices are followed for any future API gateway or AI asset management system development.

Need more detailed analysis?Get Pro

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: 11/25/2025, 12:21:52 AM

Last updated: 11/25/2025, 1:13:25 AM

Views: 5

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats