Quick answers
- Is CVE-2026-126659 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126659 being exploited in the wild.
- How severe is CVE-2026-126659?
- High severity, with a CVSS score of 7.5, published 11 November 2026.
- Which products and versions are affected?
- BlueprintUE Self-Hosted Edition 1.0.0 before 4.3.5.
- Is there a fix for CVE-2026-126659?
- Yes: fixed in 4.3.5. Until then: Configure the ANONYMOUS_BLUEPRINT_MAX_SIZE environment variable to restrict the maximum file size that anonymous users can upload, limiting the rate at which disk space can be consumed. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126659 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-126659?
- Check whether you run BlueprintUE Self-Hosted Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.3.5
Configure the ANONYMOUS_BLUEPRINT_MAX_SIZE environment variable to restrict the maximum file size that anonymous users can upload, limiting the rate at which disk space can be consumed.
Technical details
An unauthenticated remote attacker can send repeated requests to HomeController::doProcessCreateBlueprint() with large blueprint payloads and a "never" expiration setting, bypassing normal purge mechanisms to exhaust disk space. The vulnerability exists because the application does not enforce size limits or rate limits on anonymous blueprint creation. A fix is available in version 4.3.5 and later, which introduces a configurable maximum size limit for anonymous blueprint uploads.
Affected products
- BlueprintUE Self-Hosted Edition 1.0.0 before 4.3.5
Timeline
- 2026-11-11: disclosed
- 2026-11-10: patched: Fix committed to repository