Credential disclosure via exposed Docker environment file
Published Jul 16, 2026 · Updated Jul 16, 2026
Information disclosure in World Wide Broadcast Network AVideo before 29.0 allows remote attackers to read deployment secrets via /.env. The official Docker Compose file mounts the project root under Apache's document root, while no access rule blocks dotfiles, so Apache serves the environment file as static content. The default official Compose deployment is required; exposed database and administrator credentials enable direct database access and administrative takeover.
Summary
What happened
Information disclosure in World Wide Broadcast Network AVideo before 29.0 allows remote attackers to read deployment secrets via /.env. The official Docker Compose file mounts the project root under Apache's document root, while no access rule blocks dotfiles, so Apache serves the environment file as static content. The default official Compose deployment is required; exposed database and administrator credentials enable direct database access and administrative takeover.
The record
- CVE
- CVE-2026-33692
- Published
- Jul 16, 2026
- Updated
- Jul 16, 2026
- Vendor
- WWBN
- Product
- AVideo
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2026CVE publishedPublication date reported by the CVE source.
- Jul 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 29.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub advisory reproduction steps for /.env exposureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo