CVE-2026-72748 WWBN CVE debrief

Who should care

Defenders responsible for AVideo installations, security teams, and administrators should assess exposure and prioritize mitigation. Defenders should verify AVideo installations, restrict access to the vulnerable endpoint, and apply patches or mitigations as available. Defenders should also monitor for suspicious activity and track exceptions. Security teams should review compensating controls for exposed systems while remediation is scheduled and verified

Why it matters

CVE-2026-72748 is a medium-severity vulnerability in AVideo that allows unauthenticated arbitrary file writes, potentially leading to denial of service, data poisoning, or remote code execution. Defenders should verify AVideo installations, restrict access to the vulnerable endpoint, and apply patches or mitigations as available. Evidence is limited, and additional information from the vendor and other sources is needed for a comprehensive understanding.

• Denial of service through disk space exhaustion
• Potential poisoning of the video encoding pipeline
• Possible remote code execution when chained with local file inclusion
• Verification of AVideo installations for exposure

Technical summary

The aVideoEncoderChunk.json.php endpoint in AVideo allows unauthenticated attackers to write up to 4 GB of arbitrary content to the server filesystem via HTTP PUT requests. This vulnerability can be chained with local file inclusion to achieve remote code execution. Defenders should prioritize verifying and mitigating this vulnerability, especially in environments where AVideo is used. The vulnerability has a medium severity score of 6.9 and defenders should assess exposure and prioritize mitigation accordingly. AVideo's unauthenticated arbitrary file write vulnerability allows attackers to write up to 4 GB of content to the server filesystem, potentially causing denial of service, poisoning the video encoding

Defensive priority

Defenders should prioritize verifying and mitigating this vulnerability, especially in environments where AVideo is used.

Recommended defensive actions

• Verify AVideo installations for exposure
• Restrict access to the aVideoEncoderChunk.json.php endpoint
• Monitor for suspicious activity
• Apply patches or mitigations as available
• 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

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, but additional information from the vendor and other sources is limited. Evidence is limited, and defenders should verify AVideo installations, restrict access to the vulnerable endpoint, and apply patches or mitigations as available. Defenders should also monitor for suspicious activity and track exceptions.

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.