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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-30886: 0.28% estimated exploitation activity in the next 30 days; percentile 20.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The video proxy endpoint GET /v1/videos/:taskid/content is vulnerable to an Insecure Direct Object Reference (IDOR). Any authenticated user who knows another user's taskid can retrieve that user's generated video content because the handler queries tasks by taskid alone and does not verify ownership. Affected Component - Endpoint: GET /v1/videos/:taskid/content - Route middleware: TokenOrUserAuth() - Vulnerable handler: controller.VideoProxy Details VideoProxy fetches the task with: GetByOnlyTaskId performs a database lookup using only taskid: 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/<foreigntaskid/content and access another user's video if they know a valid task ID. Other task-fetch paths already enforce ownership correctly via: Impact An authenticated attacker who knows another user's taskid can: - Download video content belonging to another user - Bypass tenant…

Published by the source

23 Mar 2026, 20:30 UTC

Last modified by the source

25 Mar 2026, 20:44 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f35r-v9x5-r8mc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30886

Advisory: New API: IDOR in VideoProxy allows cross-user video content access via missing ownership check
IDs: CVE-2026-30886, GHSA-f35r-v9x5-r8mc
Record: https://patchnext.com/advisories/cve-2026-30886 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/QuantumNous/new-api 0.11.4-alpha.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/QuantumNous/new-api: affected < 0.11.4-alpha.2; fixed in 0.11.4-alpha.2

## Suggested inspection (read-only)
- Go github.com/QuantumNous/new-api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/QuantumNous/new-api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f35r-v9x5-r8mc (GitHub-reviewed advisory GHSA-f35r-v9x5-r8mc lists affected ranges: Go github.com/QuantumNous/new-api >=0 <0.11.4-alpha.2)

Commands are suggestions: review each one before running it.