blueprintUE: Active Sessions Are Not Invalidated After Password Change or Reset
blueprintUE is a tool to help Unreal Engine developers. Prior to 4.2.0, when a user changes their password via the profile edit page, or when a password reset is completed via the reset link, neither operation invalidates existing authenticated sessions for that user. A server-side session store associates userID → session; the current password change/reset flow updates only the password column in the users table and does not destroy or mark invalid any active sessions. As a result, an attacker who has already compromised a session retains full access to the account indefinitely — even after the legitimate user has detected the intrusion and changed their password — until the session's natural expiry time (configured as SESSION_GC_MAXLIFETIME, defaulting to 86400 seconds / 24 hours, with SESSION_LIFETIME=0 meaning persistent until browser close or GC, whichever is later). This vulnerability is fixed in 4.2.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-40587
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 03:24 UTC · Revision 1
Source evidence
blueprintUE: Active Sessions Are Not Invalidated After Password Change or Reset
core-osv · Original sourcePublished 21 Apr 2026, 17:11 UTC
blueprintUE is a tool to help Unreal Engine developers. Prior to 4.2.0, when a user changes their password via the profile edit page, or when a password reset is completed via the reset link, neither operation invalidates existing authenticated sessions for that user. A server-side session store associates userID → session; the current password change/reset flow updates only the password column in the users table and does not destroy or mark invalid any active sessions. As a result, an attacker who has already compromised a session retains full access to the account indefinitely — even after the legitimate user has detected the intrusion and changed their password — until the session's natural expiry time (configured as SESSION_GC_MAXLIFETIME, defaulting to 86400 seconds / 24 hours, with SESSION_LIFETIME=0 meaning persistent until browser close or GC, whichever is later). This vulnerability is fixed in 4.2.0.
osv:CVE-2026-40587
Complete source record
{
"id": "60a221313774e7cefa9ca6e68984f4773af41f3fe707bcf187be5dfc77faeebb",
"url": "https://osv.dev/vulnerability/CVE-2026-40587",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "blueprintUE: Active Sessions Are Not Invalidated After Password Change or Reset",
"summary": "blueprintUE is a tool to help Unreal Engine developers. Prior to 4.2.0, when a user changes their password via the profile edit page, or when a password reset is completed via the reset link, neither operation invalidates existing authenticated sessions for that user. A server-side session store associates userID → session; the current password change/reset flow updates only the password column in the users table and does not destroy or mark invalid any active sessions. As a result, an attacker who has already compromised a session retains full access to the account indefinitely — even after the legitimate user has detected the intrusion and changed their password — until the session's natural expiry time (configured as SESSION_GC_MAXLIFETIME, defaulting to 86400 seconds / 24 hours, with SESSION_LIFETIME=0 meaning persistent until browser close or GC, whichever is later). This vulnerability is fixed in 4.2.0.",
"evidence": "osv:CVE-2026-40587",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-40587",
"aliases": [
"CVE-2026-40587",
"GHSA-gqpq-x62g-p4mg"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/blueprintue/blueprintue-self-hosted-edition",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "28689950b0fc1c6a0c5db2a034a03fdc9747467c"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "4.2.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "4.2.0"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v4.1.2",
"v4.1.1",
"v4.1.0",
"v4.0.0",
"v3.2.0",
"v3.1.0",
"v3.0.0",
"v2.1.0",
"v2.0.1",
"v2.0.0",
"v1.0.6",
"v1.0.5",
"v1.0.4",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-40587.json"
}
}
],
"modified": "2026-10-28T02:30:25.539144845Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40587.json",
"https://github.com/blueprintue/blueprintue-self-hosted-edition/security/advisories/GHSA-gqpq-x62g-p4mg",
"https://nvd.nist.gov/vuln/detail/CVE-2026-40587"
],
"provider_metadata": {
"cwe_ids": [
"CWE-613"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40587.json"
}
},
"related_cves": [
{
"value": "CVE-2026-40587",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 492181,
"published_at": "2026-04-21T17:11:23.74+00:00"
}