VulnerabilityPublished 23 Mar 2026Updated 24 Mar 2026

CVE-2026-33483: WWBN AVideo · Unthrottled Resource Allocation

Affects WWBN AVideoSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
WWBNAVideo	Affected <=26.0	Fixed in–
GitHubwwbn/AVideo`pkg:github/wwbn/AVideo`Other threats	Affected <=26.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-33483, organizations should immediately upgrade WWBN AVideo to a version later than 26.0 that includes the patch from commit 33d1bae6c731ef1682fcdc47b428313be073a5d1. If upgrading is not immediately possible, administrators should implement temporary controls such as: 1) Restricting access to the aVideoEncoderChunk.json.php endpoint via network-level controls (firewalls, IP whitelisting) to trusted sources only. 2) Implementing web application firewall (WAF) rules to detect and block abnormal POST request sizes or rates targeting this endpoint. 3) Monitoring disk usage on servers hosting AVideo closely and setting alerts for unusual growth in /tmp/ directory files. 4) Applying OS-level quotas or limits on /tmp/ directory usage per process or user to prevent total disk exhaustion. 5) Regularly cleaning up temporary files manually or via automated scripts until the patch is applied. Additionally, reviewing server and application logs for suspicious POST requests to this endpoint can help detect exploitation attempts early. Finally, organizations should incorporate this vulnerability into their incident response plans and ensure backups and recovery procedures are tested to minimize downtime in case of an attack.

Description

CVE-2026-33483 is a high-severity vulnerability in WWBN AVideo versions up to 26.0 involving an unauthenticated PHP endpoint that allows remote attackers to write unlimited data to temporary files without size or rate limits. This flaw enables trivial disk space exhaustion, resulting in denial of service (DoS) of the entire server hosting the video platform. The vulnerable endpoint, aVideoEncoderChunk.json.php, lacks authentication, framework protections, and cleanup mechanisms, making exploitation straightforward. No user interaction or privileges are required, and the attack surface is fully remote. A patch addressing this issue is available in commit 33d1bae6c731ef1682fcdc47b428313be073a5d1. Organizations using affected versions should prioritize applying the patch to prevent service disruption. The vulnerability impacts confidentiality and integrity minimally but severely affects availability.

Impact

The primary impact of CVE-2026-33483 is denial of service through disk space exhaustion. Organizations running vulnerable versions of WWBN AVideo risk complete service disruption of their video streaming platforms, which can affect user experience, business continuity, and reputation. The attack can also impact other applications sharing the same server or storage resources, potentially causing broader operational outages. Since the vulnerability requires no authentication or user interaction, it can be exploited by any remote attacker, increasing the risk of automated attacks and large-scale disruptions. For organizations relying on AVideo for critical communications, media delivery, or educational content, this vulnerability could lead to significant downtime and financial losses. Additionally, recovery from disk exhaustion may require manual intervention, including cleanup and potential server reboots, increasing operational overhead. While confidentiality and integrity are not directly compromised, the availability impact alone justifies urgent remediation.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Mar 2026, 20:31 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats