CVE-2026-30886

The video proxy endpoint GET /v1/videos/:task_id/content is vulnerable to an Insecure Direct Object Reference (IDOR). Any authenticated user who knows another user's task_id can retrieve that user's generated video content because the handler queries tasks by task_id alone and does not verify ownership.

Affected Component

• Endpoint: GET /v1/videos/:task_id/content
• Route middleware: TokenOrUserAuth()
• Vulnerable handler: controller.VideoProxy

Details

VideoProxy fetches the task with:

task, exists, err := model.GetByOnlyTaskId(taskID)

GetByOnlyTaskId performs a database lookup using only task_id:

err = DB.Where("task_id = ?", taskId).First(&task).Error

The authenticated user's ID is available in request context, but VideoProxy does not use it. This allows any authenticated user to request /v1/videos/<foreign_task_id>/content and access another user's video if they know a valid task ID.

Other task-fetch paths already enforce ownership correctly via:

model.GetByTaskId(userId, taskId)

Proof of Concept

curl -o stolen_video.mp4 \
  "https://<instance>/v1/videos/<victim_task_id>/content" \
  -H "Authorization: Bearer sk-<attacker_token>"

Expected result:

• Response returns 200 OK
• Response body contains the victim's video content

An authenticated attacker who knows another user's task_id can:

• Download video content belonging to another user
• Bypass tenant isolation for generated media assets
• Cause the server to fetch upstream video content for a task the attacker does not own

For Gemini tasks, the proxy also uses task.PrivateData.Key when contacting the upstream provider. In addition, full upstream response headers are forwarded back to the requester.

CVE-2026-30886 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.11.4-alpha.2); upgrading removes the vulnerable code path.

Kodem intelligence

Replace the task lookup in VideoProxy with an ownership-checked query:

userId := c.GetInt("id")
task, exists, err := model.GetByTaskId(userId, taskID)

1. What is CVE-2026-30886? CVE-2026-30886 is a medium-severity security vulnerability in github.com/QuantumNous/new-api (go), affecting versions < 0.11.4-alpha.2. It is fixed in 0.11.4-alpha.2.
2. How severe is CVE-2026-30886? CVE-2026-30886 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/QuantumNous/new-api are affected by CVE-2026-30886? github.com/QuantumNous/new-api (go) versions < 0.11.4-alpha.2 is affected.
4. Is there a fix for CVE-2026-30886? Yes. CVE-2026-30886 is fixed in 0.11.4-alpha.2. Upgrade to this version or later.
5. Is CVE-2026-30886 exploitable, and should I be worried? Whether CVE-2026-30886 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-30886 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-30886? Upgrade github.com/QuantumNous/new-api to 0.11.4-alpha.2 or later.