github.com/QuantumNous/new-api
Affected
- introduced
0, fixed0.11.4-alpha.2(semver)
Fixed versions
0.11.4-alpha.2
Fix
- Fixed version
0.11.4-alpha.2go get github.com/QuantumNous/[email protected]
Advisory
Also known as: CVE-2026-30886, GO-2026-4814
New API: IDOR in VideoProxy allows cross-user video content access via missing ownership check
Summary
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
GET /v1/videos/:task_id/contentTokenOrUserAuth()controller.VideoProxyDetails
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)
Impact
An authenticated attacker who knows another user's task_id can:
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.
Proof of Concept
curl -o stolen_video.mp4 \
"https://<instance>/v1/videos/<victim_task_id>/content" \
-H "Authorization: Bearer sk-<attacker_token>"
Expected result:
200 OKRecommended Fix
Replace the task lookup in VideoProxy with an ownership-checked query:
userId := c.GetInt("id")
task, exists, err := model.GetByTaskId(userId, taskID)Medium Basis: The source's own band: MODERATE
0, fixed 0.11.4-alpha.2 (semver)0.11.4-alpha.2
0.11.4-alpha.2go get github.com/QuantumNous/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0