Quick answers
- Is CVE-2026-122138 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122138 being exploited in the wild.
- How severe is CVE-2026-122138?
- Medium severity, with a CVSS score of 5.3, published 4 November 2026.
- Which products and versions are affected?
- BlueprintUE Self-Hosted Edition 4.2.0 before 4.3.4.
- Is there a fix for CVE-2026-122138?
- Yes: fixed in 4.3.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-122138 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-122138?
- 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.4
Technical details
The LoginMiddleware.php component keys failed-login rate limit counters on the case-sensitive username, while the database uses case-insensitive lookups. An attacker can vary username casing (e.g., "admin", "Admin", "ADMIN") to evade the per-account lockout mechanism. The vulnerability requires network access and no authentication; the fix applies mb_strtolower() to normalize usernames when checking rate limits.
Affected products
- BlueprintUE Self-Hosted Edition 4.2.0 before 4.3.4
Timeline
- 2026-11-04: disclosed