/

CVE-2026-72748

Severity:

CRITICAL RISK

(9.1)

Unauthenticated File Write (CWE-306) in AVideo Encoder

CVE-2026-72748

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthenticated Arbitrary File Write and Denial of Service

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

AVideo exposes an encoder endpoint that may accept unauthenticated HTTP PUT requests to write attacker-controlled content to the server filesystem. An attacker could consume available disk space, alter video-processing inputs, or combine the file-write primitive with another weakness to pursue code execution.

Affected context

The issue occurs where the AVideo encoder's aVideoEncoderChunk.json.php endpoint is reachable over HTTP and does not adequately verify the requester's identity or authorization before accepting file content. Risk is higher when the endpoint can write to broadly accessible paths, consume substantial storage, or affect files used by the encoding pipeline.

Exploit preconditions

  • Attack surface: The HTTP-accessible aVideoEncoderChunk.json.php endpoint
  • Required access: Network reachability; no prior authentication is expected
  • Trigger point: An HTTP PUT request that submits content for filesystem storage
  • Why exploitation is possible: The endpoint may authorize file-writing behavior insufficiently or not at all, allowing remote input to control filesystem writes and consume up to approximately 4 GB per request

Why this happens

The underlying flaw is missing or ineffective authentication and authorization on a state-changing file-write endpoint. This maps to CWE-306: Missing Authentication for Critical Function, because a sensitive operation is exposed without reliably establishing the caller's identity before processing the request. Excessive write size, permissive path handling, or insufficient separation between upload storage and executable or pipeline-sensitive locations can increase the resulting impact.

Potential impact

  • An attacker may exhaust server disk capacity and cause denial of service
  • The video encoding pipeline could be disrupted or fed attacker-controlled content
  • Application data or operational files could be overwritten, depending on write-path controls
  • The file-write capability could be chained with local file inclusion or another execution weakness
  • A successful chain could result in remote code execution under the service account

General mitigation guidance

Mitigation generally focuses on placing strong identity and authorization checks before every file-writing operation.

Common defensive patterns include:

  • Require authentication and narrowly scoped authorization for encoder upload actions
  • Enforce strict server-side limits on request size, cumulative storage, and upload frequency
  • Generate server-controlled filenames and constrain writes to a dedicated non-executable directory
  • Use canonicalized paths and reject traversal, unexpected extensions, and ambiguous file locations
  • Separate encoder storage permissions from application, configuration, and executable paths
  • Apply quotas, monitoring, and automatic cleanup for temporary encoding data
  • Run the encoder with least privilege and isolate it from sensitive filesystem resources
  • Treat uploaded content as untrusted and validate it before it enters processing pipelines

How teams detect issues like this

High-level detection can combine:

  • Static analysis for unauthenticated routes that invoke filesystem write APIs
  • Code review checks for missing authorization middleware on state-changing endpoints
  • Tests confirming that anonymous requests cannot create or replace files
  • Policy enforcement for upload size, storage quotas, path confinement, and non-executable upload directories
  • Web-server and application monitoring for unusual PUT requests, repeated large uploads, storage growth, and writes outside approved directories
  • File-integrity monitoring for unexpected changes to pipeline inputs, configuration files, or executable locations

Automated application security testing and code-review tools may help identify exposed write operations, but authorization and deployment-specific validation remain important.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/commit/1b55a9b3c4911d2f31594ce2e60566c70c6b95e8
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-v7p7-jccx-h37c
vulncheck.comvulncheck.com/advisories/avideo-unauthenticated-arbitrary-file-write-via-avideoencoderchunk-json-php

Frequently asked

questions

Yes, where the encoder endpoint is network-reachable and accepts unauthenticated HTTP PUT requests. The attacker does not need an existing application account under those conditions.

Network access to the affected endpoint may be sufficient. The exact impact depends on the endpoint's write locations, storage permissions, request limits, and surrounding server configuration.

Require authentication and authorization before accepting file content, then constrain writes to a dedicated non-executable area with strict quotas, path controls, and server-generated names.

Review every state-changing endpoint for explicit authorization, test anonymous and low-privilege access paths, enforce upload and storage policies, and monitor filesystem activity for unexpected writes or rapid disk consumption.

Find out what's already
exploitable in your codebase.