CVE-2026-30886: CWE-639: Authorization Bypass Through User-Controlled Key in QuantumNous new-api
CVE-2026-30886 is an authorization bypass vulnerability in QuantumNous new-api versions prior to 0. 11. 4-alpha. 2. It arises from an Insecure Direct Object Reference (IDOR) in the video proxy endpoint, allowing any authenticated user to access video content belonging to other users. The root cause is a missing ownership check in a key function that queries video tasks by task_id without verifying user ownership. Exploiting this flaw can also cause the server to authenticate to upstream AI providers using credentials tied to other users' tasks. The vulnerability has a CVSS score of 6. 5 (medium severity) and does not require user interaction but does require authentication. A patch was introduced in version 0.
AI Analysis
Technical Summary
QuantumNous new-api is an AI asset management system and LLM gateway that, prior to version 0.11.4-alpha.2, contained a critical authorization bypass vulnerability classified as CWE-639 (Authorization Bypass Through User-Controlled Key). The vulnerability exists in the video proxy endpoint (`GET /v1/videos/:task_id/content`), where the function `model.GetByOnlyTaskId(taskID)` retrieves video content based solely on the task_id parameter without verifying the user_id ownership. This contrasts with other parts of the codebase that correctly enforce ownership by querying with both userId and taskID. As a result, any authenticated user can access video content and associated AI task data belonging to other users. Furthermore, the server may authenticate to upstream AI providers such as Google Gemini and OpenAI using credentials derived from tasks it does not own, potentially exposing sensitive API credentials or causing unauthorized actions. The vulnerability requires authentication but no user interaction and can be exploited remotely over the network. The issue was addressed in version 0.11.4-alpha.2 by adding the missing user ownership check in the task lookup function. No known exploits are currently reported in the wild. The CVSS v3.1 base score is 6.5, reflecting a medium severity due to high confidentiality impact but no integrity or availability impact.
Potential Impact
The primary impact of this vulnerability is unauthorized disclosure of video content and AI task data belonging to other users within the QuantumNous new-api system. This can lead to leakage of sensitive or proprietary information, violating confidentiality. Additionally, because the server authenticates to upstream AI providers using credentials tied to other users' tasks, attackers may indirectly gain access to or misuse these external AI services, potentially causing data leakage or unauthorized AI operations. Organizations relying on QuantumNous new-api for managing AI assets and video content may face data privacy violations, regulatory compliance issues, and reputational damage. While the vulnerability does not affect data integrity or system availability, the exposure of sensitive content and credentials can have significant operational and legal consequences. The requirement for authentication limits exploitation to insiders or compromised accounts, but the ease of bypassing authorization checks makes it a serious concern for multi-tenant environments or shared platforms.
Mitigation Recommendations
The primary mitigation is to upgrade QuantumNous new-api to version 0.11.4-alpha.2 or later, which contains the patch enforcing proper user ownership checks on task queries. Organizations should immediately apply this update to eliminate the authorization bypass. In addition, conduct a thorough audit of access control mechanisms across all API endpoints to ensure consistent enforcement of user ownership and authorization policies. Implement monitoring and alerting for unusual access patterns to video content or AI tasks that do not align with user roles or ownership. Consider employing API gateways or web application firewalls (WAFs) to add an additional layer of authorization validation. Review and rotate credentials used for upstream AI provider authentication to mitigate risks from any previously exposed credentials. Finally, educate developers on secure coding practices to avoid similar IDOR vulnerabilities, emphasizing the importance of verifying user context in all resource access functions.
Affected Countries
United States, Canada, United Kingdom, Germany, France, Japan, South Korea, Australia, India, Singapore
CVE-2026-30886: CWE-639: Authorization Bypass Through User-Controlled Key in QuantumNous new-api
Description
CVE-2026-30886 is an authorization bypass vulnerability in QuantumNous new-api versions prior to 0. 11. 4-alpha. 2. It arises from an Insecure Direct Object Reference (IDOR) in the video proxy endpoint, allowing any authenticated user to access video content belonging to other users. The root cause is a missing ownership check in a key function that queries video tasks by task_id without verifying user ownership. Exploiting this flaw can also cause the server to authenticate to upstream AI providers using credentials tied to other users' tasks. The vulnerability has a CVSS score of 6. 5 (medium severity) and does not require user interaction but does require authentication. A patch was introduced in version 0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
QuantumNous new-api is an AI asset management system and LLM gateway that, prior to version 0.11.4-alpha.2, contained a critical authorization bypass vulnerability classified as CWE-639 (Authorization Bypass Through User-Controlled Key). The vulnerability exists in the video proxy endpoint (`GET /v1/videos/:task_id/content`), where the function `model.GetByOnlyTaskId(taskID)` retrieves video content based solely on the task_id parameter without verifying the user_id ownership. This contrasts with other parts of the codebase that correctly enforce ownership by querying with both userId and taskID. As a result, any authenticated user can access video content and associated AI task data belonging to other users. Furthermore, the server may authenticate to upstream AI providers such as Google Gemini and OpenAI using credentials derived from tasks it does not own, potentially exposing sensitive API credentials or causing unauthorized actions. The vulnerability requires authentication but no user interaction and can be exploited remotely over the network. The issue was addressed in version 0.11.4-alpha.2 by adding the missing user ownership check in the task lookup function. No known exploits are currently reported in the wild. The CVSS v3.1 base score is 6.5, reflecting a medium severity due to high confidentiality impact but no integrity or availability impact.
Potential Impact
The primary impact of this vulnerability is unauthorized disclosure of video content and AI task data belonging to other users within the QuantumNous new-api system. This can lead to leakage of sensitive or proprietary information, violating confidentiality. Additionally, because the server authenticates to upstream AI providers using credentials tied to other users' tasks, attackers may indirectly gain access to or misuse these external AI services, potentially causing data leakage or unauthorized AI operations. Organizations relying on QuantumNous new-api for managing AI assets and video content may face data privacy violations, regulatory compliance issues, and reputational damage. While the vulnerability does not affect data integrity or system availability, the exposure of sensitive content and credentials can have significant operational and legal consequences. The requirement for authentication limits exploitation to insiders or compromised accounts, but the ease of bypassing authorization checks makes it a serious concern for multi-tenant environments or shared platforms.
Mitigation Recommendations
The primary mitigation is to upgrade QuantumNous new-api to version 0.11.4-alpha.2 or later, which contains the patch enforcing proper user ownership checks on task queries. Organizations should immediately apply this update to eliminate the authorization bypass. In addition, conduct a thorough audit of access control mechanisms across all API endpoints to ensure consistent enforcement of user ownership and authorization policies. Implement monitoring and alerting for unusual access patterns to video content or AI tasks that do not align with user roles or ownership. Consider employing API gateways or web application firewalls (WAFs) to add an additional layer of authorization validation. Review and rotate credentials used for upstream AI provider authentication to mitigate risks from any previously exposed credentials. Finally, educate developers on secure coding practices to avoid similar IDOR vulnerabilities, emphasizing the importance of verifying user context in all resource access functions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-06T00:04:56.700Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c1986ff4197a8e3b86e7bb
Added to database: 3/23/2026, 7:45:51 PM
Last enriched: 3/23/2026, 8:01:25 PM
Last updated: 3/23/2026, 9:08:18 PM
Views: 3
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.