# CVE-2026-72748: AVideo Unauthenticated Arbitrary File Write via aVideoEncoderChunk.json.php

> Unauthenticated attackers can write arbitrary files to the server, enabling disk exhaustion or remote code execution via file inclusion.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-q6c7-vm4c-28mj, GHSA-v7p7-jccx-h37c

## What is CVE-2026-72748?

CVE-2026-72748 is a medium-severity vulnerability in WWBN AVideo, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AVideo contains an unauthenticated arbitrary file write vulnerability in the aVideoEncoderChunk.json.php endpoint that allows remote attackers to write up to 4 GB of arbitrary content to the server filesystem via HTTP PUT requests without authentication. Attackers can exhaust disk space causing denial of service, poison the video encoding pipeline, or chain this with local file inclusion to achieve remote code execution.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-72748?


## How do I fix CVE-2026-72748?

No fix has been published for CVE-2026-72748 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72748 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72748 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72748 and fix it if it is affected.

What it is: CVE-2026-72748 is a medium-severity vulnerability in WWBN AVideo, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72748 exists.

Affected product: WWBN AVideo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72748/ (Markdown: https://insights.sbomify.com/CVE-2026-72748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72748
- OSV: https://osv.dev/vulnerability/CVE-2026-72748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72748/
Summaries are generated and may contain mistakes; the official description above is the record.