CVE-2026-40585: blueprintue-self-hosted-edition · Weak Password Recovery
Affects blueprintue-self-hosted-editionSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 4.2.0 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.2.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade blueprintue-self-hosted-edition and blueprintue/blueprintue-self-hosted-edition to 4.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| blueprintueblueprintue-self-hosted-edition | Affected
| Fixed in
|
GitHubblueprintue/blueprintue-self-hosted-editionpkg:github/blueprintue/blueprintue-self-hosted-editionOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade blueprintue-self-hosted-edition to version 4.2.0 or later, where the password reset token expiration check is properly implemented. Until upgraded, consider invalidating outstanding password reset tokens manually if possible. Patch status is not explicitly stated but the vendor fixed the issue in version 4.2.0, so applying this official fix is the recommended remediation.
Description
blueprintUE is a tool to help Unreal Engine developers. Prior to 4.2.0, when a password reset is initiated, a 128-character CSPRNG token is generated and stored alongside a password_reset_at timestamp. However, the token redemption function findUserIDFromEmailAndToken() queries only for a matching email + password_reset token pair — it does not check whether the password_reset_at timestamp has elapsed any maximum window. A generated reset token is valid indefinitely until it is explicitly consumed or overwritten by a subsequent reset request. This vulnerability is fixed in 4.2.0.