# CVE-2026-59808: AVideo Authentication Bypass via Unkeyed Video Hash Disclosure

> Attackers with upload permissions can bypass authentication to gain administrative access and modify system configuration in AVideo.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-q32p-rw3q-8x3r, GHSA-wx4f-hq3h-2p8m

## What is CVE-2026-59808?

CVE-2026-59808 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 22 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AVideo through commit 9c39d8c8 contains an authentication bypass vulnerability where deduplicateByEncoderQueueId() returns video_id_hash credentials for any video by encoder_queue_id without ownership verification, and useVideoHashOrLogin() converts this hash into passwordless login as the video owner. Attackers with upload permission can retrieve an administrator's video_id_hash by omitting the videos_id parameter, then use that hash in an unauthenticated request to gain administrative session access and modify system configuration.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

No fix has been published for CVE-2026-59808 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59808 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59808 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 22 Aug 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-59808 exists.

Affected product: WWBN AVideo. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-59808/ (Markdown: https://insights.sbomify.com/CVE-2026-59808/index.md)
```

## Sources

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

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