CVE-2026-92912

AVideo Cryptographically Weak PRNG via uniqid Stream Key

Published Sep 17, 2026 CVSS 4.0 · 8.3 High EPSS < 1% KEV · Not listed
Description
AVideo through c3edcc274c389816d434acadac07ee78eaf330c1 uses cryptographically weak uniqid() values for RTMP publish keys in LiveTransmition, reducing key entropy to approximately one million possibilities per creation second. Attackers who know the channel creation time can brute-force the five-digit microsecond component to forge valid stream keys and broadcast content as the channel owner.

Analysis

AI-generated

Technical impact

The vulnerability is caused by AVideo's use of PHP's uniqid() function to generate RTMP publish keys. This creates a key space of only about one million possibilities per second, far too small for secure unique identifiers. If an attacker can determine the channel creation time, the five‑digit microsecond component can be brute‑forced rapidly, allowing the attacker to forge a valid stream key and publish content as the legitimate channel owner. With control of the stream, an attacker could inject misinformation, malicious content, or disrupt legitimate broadcasts, undermining the platform’s integrity and trustworthiness.

Affected Systems

The affected product is AVideo from WWBN, as identified in the public advisory. The flaw appears in code at commit c3edcc274c389816d434acadac07ee78eaf330c1; no specific version numbers are provided, so any install of AVideo prior to the fix is potentially vulnerable.

Risk and Exploitability

This issue carries a CVSS score of 8.3, indicating high severity. The exploitation probability is not quantified by EPSS, but the limited keyspace means that an attacker who can approximate the stream creation time can brute‑force a valid key in a short period. The vulnerability is not listed in the CISA KEV catalog, yet it can enable unauthenticated broadcast impersonation, representing a significant risk to content integrity and platform reputation. The most likely attack vector is a network‑based brute‑force on the stream key derived from the known creation time.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update AVideo to the latest version that replaces uniqid() with a cryptographically secure random generator for stream keys.
  • Alter the stream‑key generation to include a longer, truly random component, or enforce a minimum key length that exceeds the 10⁶ keyspace limitation.
  • Configure monitoring or firewalls to detect and block duplicate stream keys or unexpected stream activity, and consider disabling unused or orphaned channels to reduce attackers’ opportunities.

Generated by OpenCVE AI on September 18, 2026 at 06:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description AVideo through c3edcc274c389816d434acadac07ee78eaf330c1 uses cryptographically weak uniqid() values for RTMP publish keys in LiveTransmition, reducing key entropy to approximately one million possibilities per creation second. Attackers who know the channel creation time can brute-force the five-digit microsecond component to forge valid stream keys and broadcast content as the channel owner.
Title AVideo Cryptographically Weak PRNG via uniqid Stream Key
First Time appeared Wwbn
Wwbn avideo
Weaknesses CWE-330
CPEs cpe:2.3:a:wwbn:avideo:-:*:*:*:*:*:*:*
Vendors & Products Wwbn
Wwbn avideo
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N'}

cvssV4_0

{'score': 8.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-330

    Use of Insufficiently Random Values

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 19, 2026, 2:14 AM
Reserved
Sep 17, 2026, 11:07 AM
Status
Deferred
Published
Sep 17, 2026, 12:18 PM
Modified
Sep 22, 2026, 8:43 PM