# AVideo has an Authorization Bypass via Path Traversal in HLS Endpoint Allows Streaming Private/Paid Videos

Advisory record · `GHSA-pw4v-x838-w5pg`

- **Identifiers:** `GHSA-pw4v-x838-w5pg` · `CVE-2026-33292` · `PKSA-ht27-8rcs-t939`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 19 Mar 2026
- **Updated:** 25 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Mar 2026, 16:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wwbn/avideo` (Packagist): affected `<=25.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> AVideo (wwbn/avideo, Packagist) versions up to and including 25.0 are affected, and no fixed version is listed. An unauthenticated attacker can send a crafted videoDirectory parameter to the HLS endpoint so that the authorization check runs against a public video while the stream comes from a private or paid video. This allows streaming of private and paid content. The source suggests no workaround is available; the advisory's recommended fix is input sanitization and a realpath check in the code.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0076, the 56th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pw4v-x838-w5pg)

## Sources

- [GitHub Advisory Database: GHSA-pw4v-x838-w5pg](https://github.com/advisories/GHSA-pw4v-x838-w5pg)
- [OSV: GHSA-pw4v-x838-w5pg](https://osv.dev/vulnerability/GHSA-pw4v-x838-w5pg)
- <https://github.com/WWBN/AVideo/security/advisories/GHSA-pw4v-x838-w5pg>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33292>
- <https://github.com/WWBN/AVideo/commit/bc034066281085af00e64b0d7b81d8a025a928c4>
- <https://github.com/WWBN/AVideo>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pw4v-x838-w5pg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pw4v-x838-w5pg/>. Everything for agents: <https://agentprime.io/llms.txt>.
