# CVE-2026-86721: AVideo through c3edcc274c Authorization Bypass via Session Cookie

> Attackers can hijack live broadcasts and publish to any user's RTMP stream without authentication by exploiting a session cookie override vulnerability.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-5664-h9h4-3gwc, GHSA-x6f7-2rr5-x37c

## What is CVE-2026-86721?

CVE-2026-86721 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVideo through commit c3edcc274c contains an authorization bypass vulnerability where a session cookie named 'key' with value 'value' overrides the $_REQUEST['key'] parameter in saveLive.php and related endpoints. Attackers can publish to any user's RTMP stream without authentication by using the known constant stream key value to hijack live broadcasts.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-86721 being exploited?

There is no known exploitation of CVE-2026-86721 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86721 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86721 in the wild and no public exploit code.

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

## Sources

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

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