/

CVE-2026-59808

Severity:

HIGH RISK

(8.8)

Authentication Bypass (CWE-306) in AVideo Uploads Portal

CVE-2026-59808

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-306

Impact:

Administrative Account Takeover

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

AVideo contains an authentication bypass caused by video ownership credentials being disclosed without adequate authorization checks. An attacker with upload permission may obtain a video hash associated with an administrator and use it to establish an administrative session, potentially changing system configuration.

Affected context

The vulnerability occurs in AVideo workflows that resolve video credentials through an encoder queue identifier and later accept the resulting video hash as a passwordless login mechanism. Risk is increased when an attacker can submit or access encoder-related upload data, when the video identifier is omitted, and when ownership or authorization is not verified before credentials are returned.

Exploit preconditions

  • Attack surface: AVideo upload and video-authentication endpoints
  • Required access: Permission to upload or otherwise interact with encoder queue data
  • Trigger point: A request that resolves a video hash by encoder queue identifier, followed by the passwordless video-hash authentication flow
  • Authorization gap: The lookup may return credentials without confirming that the requester owns or is authorized to access the referenced video
  • Why exploitation is possible: A credential-like video hash can be converted into an authenticated session without an independent password or ownership check

Why this happens

The underlying bug is an authorization failure mapped to CWE-306: Missing Authentication for Critical Function. A function returns a sensitive authentication token based on an identifier without enforcing ownership, and another function treats that token as sufficient proof of identity. This insecure pattern conflates resource association with user authentication and allows a value exposed through an insufficiently protected workflow to provide privileged session access.

Potential impact

  • An attacker could obtain an administrative session
  • Unauthorized users may modify system configuration
  • Video ownership and access controls could be bypassed
  • Attackers could alter, delete, or expose managed media
  • The application could experience broader compromise depending on administrator privileges

General mitigation guidance

Mitigation generally focuses on separating resource lookup from authentication and enforcing authorization at every credential-producing and session-establishing boundary.

Common defensive patterns include:

  • Require authenticated identity and explicit ownership or authorization checks before returning sensitive video-linked values
  • Avoid using resource hashes or identifiers as standalone authentication credentials
  • Use independent, high-entropy session and login mechanisms with appropriate expiration and rotation
  • Apply least privilege to uploaders and administrative accounts
  • Return uniform responses that do not disclose whether privileged resources or credentials exist
  • Treat omitted identifiers and alternate request paths as invalid unless their behavior is explicitly authorized

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review rules for credential-like values returned without authorization checks
  • Review of functions that convert resource identifiers, hashes, or tokens directly into authenticated sessions
  • Tests covering missing parameters, cross-user resource access, and privilege-boundary transitions
  • Access-log analysis for upload users followed by video-hash authentication or administrative configuration changes
  • Policy enforcement requiring explicit authorization checks before sensitive data disclosure and session creation

Automated security review tools may help identify missing authorization checks, but endpoint-level tests should validate ownership and privilege behavior.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-q32p-rw3q-8x3r
vulncheck.comvulncheck.com/advisories/avideo-authentication-bypass-via-unkeyed-video-hash-disclosure

Frequently asked

questions

An attacker generally needs upload permission or equivalent access to the encoder queue workflow. The resulting impact depends on whether the exposed hash belongs to a privileged account.

The described attack path may not require the administrator's password because the video hash is accepted as a passwordless authentication factor. Access to the vulnerable lookup workflow remains an important prerequisite.

Enforce authenticated ownership or authorization checks before returning video-linked credentials, and do not treat resource hashes as standalone proof of identity.

Apply authorization checks consistently across alternate endpoints and missing-parameter cases, separate resource identifiers from login credentials, use least privilege, and test cross-account access boundaries.

Find out what's already
exploitable in your codebase.