AVideo Vulnerable to Unauthenticated .env File Exposure via Official Docker Compose Configuration

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-33692: 0.35% estimated exploitation activity in the next 30 days; percentile 28.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Vulnerability Details CWE: CWE-538 - Insertion of Sensitive Information into Externally-Accessible File or Directory The official docker-compose.yml (line 61) mounts the entire project root directory as the Apache document root: This causes the .env file — which contains database credentials, admin passwords, and infrastructure configuration — to be served as a static file at /.env. No .htaccess rule or Apache configuration blocks access to dotfiles. Exposed Information An unauthenticated request to GET /.env returns: Steps to Reproduce Prerequisites - AVideo deployed using the official docker-compose.yml - No modifications to the default configuration Steps 1. Deploy AVideo using docker compose up -d 2. Send: curl http://target/.env 3. The full .env file contents are returned, including database credentials and admin password Impact - Attacker: Unauthenticated (any remote user) - Victim: AVideo server and database - Specific damage: Attacker obtains database credentials…

Published by the source

22 Jun 2026, 19:54 UTC

Last modified by the source

22 Jun 2026, 19:54 UTC

Source last checked

26 Oct 2026, 14:49 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wf69-r4mx-43rr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33692

Advisory: AVideo Vulnerable to Unauthenticated .env File Exposure via Official Docker Compose Configuration
IDs: CVE-2026-33692, GHSA-wf69-r4mx-43rr
Record: https://patchnext.com/advisories/cve-2026-33692 (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: wwbn/avideo 29.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist wwbn/avideo: affected < 29.0; fixed in 29.0

## Suggested inspection (read-only)
- Packagist wwbn/avideo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wwbn/avideo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wf69-r4mx-43rr (GitHub-reviewed advisory GHSA-wf69-r4mx-43rr lists affected ranges: Packagist wwbn/avideo >=0 <29.0)

Commands are suggestions: review each one before running it.