CVE-2026-86726 WWBN CVE debrief

Who should care

Defenders managing AVideo instances, especially those with multiple streamers, should assess exposure and prioritize mitigation. They should verify AVideo version, restrict access to restreamsActive.json.php, and monitor for suspicious activity on AVideo instances. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified, and tracking exceptions, retesting remediated assets, and closing the item only

Why it matters

This information disclosure vulnerability in AVideo allows authenticated streamers to access sensitive information about other streamers' active restreams, potentially leading to unauthorized access and data exposure. Defenders managing AVideo instances should assess exposure, prioritize mitigation, and verify instance configurations.

• Streamer identity and transmission credential exposure
• Potential for unauthorized access to sensitive streaming data
• Need for verification of AVideo version and instance configuration
• Prioritization of updates and access controls

Technical summary

The restreamsActive.json.php endpoint in AVideo through 29.0 fails to filter results by user ownership, allowing authenticated streamers to enumerate source stream keys and identities of all other streamers' active restreams. This vulnerability can lead to unauthorized access and data exposure. Defenders should prioritize verifying and mitigating this vulnerability, especially for AVideo instances with multiple streamers, by verifying AVideo version, restricting access to restreamsActive.json.php, and monitoring for suspicious activity.

Defensive priority

Defenders should prioritize verifying and mitigating this vulnerability, especially for AVideo instances with multiple streamers.

Recommended defensive actions

• Verify AVideo version and check for updates to 29.0 or later
• Restrict access to restreamsActive.json.php
• Monitor for suspicious activity on AVideo instances
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the information disclosure vulnerability in AVideo. However, the corpus does not establish versions beyond 29.0, exploitation, impact, or remediation for earlier versions.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.