CVE-2026-126812: CVE-2026-126812: blueprintUE Self-Hosted Edition before 4.3.7 contains an insecure default configuration in…
Unknown · · NVD published 2026-11-12 · posted 2026-11-11 · last modified 2026-11-12
CVE-2026-126812 at a glance
CVE-2026-126812 is a critical-severity vulnerability in the affected product, with a CVSS 4.0 base score of 9.3. NVD published it on 2026-11-12 and classifies the weakness as CWE-258. NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 1 MITRE ATT&CK technique across Initial Access, inferred from the CWE and the description. Its CVERadar threat level is 47/100.
What it is
blueprintUE Self-Hosted Edition before 4.3.7 contains an insecure default configuration in its Docker Compose examples that sets MYSQL_ALLOW_EMPTY_PASSWORD=yes in database.env and publishes MariaDB on port 3306. Unauthenticated attackers reaching the Docker host on port 3306 can log in as root without a password to read, modify, or delete user accounts, blueprints, and all databases.
| Weakness | CWE-258 definition |
|---|---|
| CVSS vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (source: VulnCheck) |
| ATT&CK tactics | Initial Access |
Defend the Chain
The attack chain for CVE-2026-126812 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.
Pick a red technique card on the board, then choose the defence that stops it.
Defend against T1190 Exploit Public-Facing Application Inferred
Inferred from description keywords (network-reachable flaw)
Patches, mitigations and detection
Fixed versions
NVD does not list a fixed version for this CVE. Use the vendor advisory below.
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
No vendor-tagged reference yet; see the full reference list.
MITRE ATT&CK mitigations for this chain
- M1048 Application Isolation and Sandboxing (for T1190) : Application isolation will limit what other processes and system features the exploited target can access.
- M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
- M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
- M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
- M1026 Privileged Account Management (for T1190) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
- M1050 Exploit Protection (for T1190) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
- M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
- M1051 Update Software (for T1190) : Update software regularly by employing patch management for externally exposed applications.
Detection Generic guidance
- Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.
Sources
- NVD: CVE-2026-126812
- CVE.org record for CVE-2026-126812
- FIRST EPSS score for CVE-2026-126812 (n/a)
- GitHub reference (github.com) github.com/blueprintue/blueprintue-self-hosted-edition/blob/v4.3.6/docker-exampl
- GitHub reference (github.com) github.com/blueprintue/blueprintue-self-hosted-edition/blob/v4.3.6/docker-exampl
- GitHub fix commit (github.com) github.com/blueprintue/blueprintue-self-hosted-edition/commit/e6a6e1d4c2f22efbba
- GitHub pull request (github.com) github.com/blueprintue/blueprintue-self-hosted-edition/pull/270
- GitHub reference (github.com) github.com/blueprintue/blueprintue-self-hosted-edition/releases/tag/v4.3.7
- GitHub security advisory (github.com) github.com/blueprintue/blueprintue-self-hosted-edition/security/advisories/GHSA-
- VulnCheck reference (vulncheck.com) vulncheck.com/advisories/blueprintue-self-hosted-edition-before-4.3.7-empty-mari