# CVE-2026-30886: New API: IDOR in VideoProxy allows cross-user video content access via missing ownership check

> Authenticated users can access other users' video content and trigger upstream AI provider authentication due to missing ownership checks in the video proxy endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-f35r-v9x5-r8mc, GO-2026-4814

## What is CVE-2026-30886?

CVE-2026-30886 is a medium-severity missing authorization vulnerability in QuantumNous new-api, published on 23 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to version 0.11.4-alpha.2, an Insecure Direct Object Reference (IDOR) vulnerability in the video proxy endpoint (`GET /v1/videos/:task_id/content`) allows any authenticated user to access video content belonging to other users and causes the server to authenticate to upstream AI providers (Google Gemini, OpenAI) using credentials derived from tasks they do not own. The missing authorization check is a single function call — `model.GetByOnlyTaskId(taskID)` queries by `task_id` alone with no `user_id` filter, while every other task-lookup in the codebase enforces ownership via `model.GetByTaskId(userId, taskID)`. Version 0.11.4-alpha.2 contains a patch.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-30886?

3 open source packages ship an affected version, including github.com/QuantumNous/new-api. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/QuantumNous/new-api` | Go | All versions | 0.11.4-alpha.2 |
| `github.com/QuantumNous/new-api` | Go | All versions | 0.11.4-alpha.2 |
| `github.com/QuantumNous/new-api` | Go | All versions | 0.11.4-alpha.2 |

Products: Newapi New Api.

## How do I fix CVE-2026-30886?

Upgrade github.com/QuantumNous/new-api to 0.11.4-alpha.2 or later.

## Is CVE-2026-30886 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30886 exists.

## Other vulnerabilities in QuantumNous new-api

- [CVE-2025-55573](https://insights.sbomify.com/CVE-2025-55573/): Cross-site scripting in n/a (high 8.8)
- [CVE-2026-33655](https://insights.sbomify.com/CVE-2026-33655/): New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs (high 7.7)
- [CVE-2026-25802](https://insights.sbomify.com/CVE-2026-25802/): New API has Potential XSS in its MarkdownRenderer component (high 7.6)
- [CVE-2026-41432](https://insights.sbomify.com/CVE-2026-41432/): New API: Stripe Webhook Signature Bypass via Empty Secret Enables Unlimited Quota Fraud (high 7.1)
- [CVE-2026-42339](https://insights.sbomify.com/CVE-2026-42339/): New API: SSRF Filter Bypass via 0.0.0.0 (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30886 and fix it if it is affected.

What it is: CVE-2026-30886 is a medium-severity missing authorization vulnerability in QuantumNous new-api, published on 23 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30886 exists.

Affected packages and fixed versions:
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 0.11.4-alpha.2
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 0.11.4-alpha.2
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 0.11.4-alpha.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30886/ (Markdown: https://insights.sbomify.com/CVE-2026-30886/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30886
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30886
- OSV: https://osv.dev/vulnerability/CVE-2026-30886

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30886/
Summaries are generated and may contain mistakes; the official description above is the record.