# CVE-2026-86726: AVideo through 29.0 Information Disclosure via restreamsActive.json.php

> Authenticated streamers can enumerate other users' active restream keys and identities due to missing ownership checks in the AVideo platform.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 8 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-hmw7-mfxq-3455, GHSA-qh45-c3p8-jh4g

## What is CVE-2026-86726?

CVE-2026-86726 is a high-severity vulnerability in WWBN AVideo, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AVideo through 29.0 contains an information disclosure vulnerability in restreamsActive.json.php that allows authenticated streamers to enumerate source stream keys and identities of all other streamers' active restreams. The endpoint fails to filter results by user ownership, exposing sensitive transmission credentials and streamer identity across all accounts to any user with streaming capability.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-86726 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86726 is a high-severity vulnerability in WWBN AVideo, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86726 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-86726/ (Markdown: https://insights.sbomify.com/CVE-2026-86726/index.md)
```

## Sources

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

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