On this page (7 sections)
A critical flaw tracked as CVE-2026-126812 affects the Docker Compose examples that ship with blueprintUE Self-Hosted Edition before version 4.3.7. According to the GitHub Advisory Database, the examples set an empty-password option for the MariaDB database and publish the database port, so anyone who can reach the Docker host on port 3306 can log in as root without a password.
This is a configuration problem rather than a bug in application code. If you copied the example files into a real deployment, you should check it today, especially if the host is reachable from the internet or from networks you do not fully control.
What happened
The advisory states that the Docker Compose examples in blueprintUE Self-Hosted Edition set MYSQL_ALLOW_EMPTY_PASSWORD=yes in a file called database.env and publish MariaDB on port 3306. The result is a database server that accepts a root login with no password and is listening on the host's network interface, not just inside the Docker network.
The advisory was published on November 11, 2026 and is mirrored by NVD, which repeats the same description. The affected example files are visible in the project's v4.3.6 database.env and docker-compose-smtp.yml. The fix is referenced in pull request 270 and the v4.3.7 release. A VulnCheck advisory is also listed as a reference.
Why this is dangerous
Two separate settings combine here. The first allows MariaDB to start with a blank root password. The second publishes port 3306 on the Docker host. Either one alone is a weakness; together they let a remote, unauthenticated user connect to the database server with full administrative rights.
The CVSS v4 metrics in the advisory reflect that: network attack vector, low complexity, no privileges, no user interaction, and high impact to confidentiality, integrity and availability. According to the advisory, an attacker can read, modify or delete user accounts, blueprints and all databases on that server.
This class of problem, an insecure default copied from example files, is common with Docker setups. Example files are meant for trying software out, but they often end up in production unchanged.
Who is affected
- Teams that deployed blueprintUE Self-Hosted Edition using the Docker Compose examples from a version before 4.3.7 and kept the database.env and port settings as shipped.
- Hosts where port 3306 is reachable from the internet, a shared network, or other containers and machines you do not trust.
- Deployments where someone changed the password or removed the port mapping are likely less exposed, but verify rather than assume.
The research does not say how many installations are affected or whether anyone is exploiting this. Treat any internet-reachable instance with the default configuration as potentially already accessed.
How to check your exposure
Start by looking at your own files. This command searches your deployment directory for the empty-password setting named in the advisory. Run it on the Docker host from the folder holding your compose and env files; any match means the option is enabled.
grep -rn "MYSQL_ALLOW_EMPTY_PASSWORD" .Next, see whether MariaDB is published on the host. This lists running containers with their port mappings; a database container showing 3306 mapped to 0.0.0.0 or to a host address means it is reachable beyond the Docker network.
docker ps --format "table {{.Names}}\t{{.Image}}\t{{.Ports}}"Also check from a different machine whether port 3306 on your host answers at all. Only test hosts you own. You can use the free SSL checker for certificates, but for open ports you need a network tool run from outside your firewall.
What to do now
- Block inbound access to port 3306 on the Docker host at the firewall or cloud security group right away, allowing only trusted addresses if remote access is truly needed.
- Upgrade blueprintUE Self-Hosted Edition to 4.3.7 or later and review the changes in the v4.3.7 release.
- Remove MYSQL_ALLOW_EMPTY_PASSWORD=yes from database.env and set a strong, unique root password and a separate application user.
- Remove the 3306 port mapping from your compose file unless you need external database access, so MariaDB is reachable only on the internal Docker network.
- Rotate secrets that could have been exposed: application database credentials, SMTP credentials and any user passwords stored in the database.
- Review the database for unexpected users, changed or deleted records, and check access logs for connections from addresses you do not recognize.
- If you find signs of access, restore from a known-good backup and follow a website hacked response plan.
Detection and monitoring
Because the database could be read without any password, normal application logs may show nothing unusual. Look at MariaDB's own connection logs if enabled, your firewall or flow logs for inbound connections to port 3306, and the user table for accounts you did not create.
After fixing, keep watching for drift. Port mappings and environment files tend to creep back when someone redeploys from an old example. Periodic external scans and monitoring of your public-facing services help you notice when something unexpected becomes reachable. For general hardening of small sites, see the small business website security guide.
Lessons for Docker deployments
- Treat example compose files as a starting point, never as production configuration.
- Do not publish database ports to the host unless required; let application containers reach the database over an internal network.
- Never allow empty database passwords, even for internal services.
- Search your other self-hosted stacks for the same pattern, since this default is not unique to one project.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
