{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40587 exists.","fix":"No fix has been published for CVE-2026-40587 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40587 is a medium-severity vulnerability in blueprintue-self-hosted-edition, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40587 and fix it if it is affected.\n\nWhat it is: CVE-2026-40587 is a medium-severity vulnerability in blueprintue-self-hosted-edition, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40587 exists.\n\nAffected product: blueprintue-self-hosted-edition. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40587/ (Markdown: https://insights.sbomify.com/CVE-2026-40587/index.md)","id":"CVE-2026-40587","markdown":"https://insights.sbomify.com/CVE-2026-40587/index.md","name":"CVE-2026-40587","record":{"aliases":["GHSA-gqpq-x62g-p4mg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Unreal Engine developer tool","requires_auth":"high_privilege","summary":"Attackers with compromised sessions retain account access indefinitely after password changes because active sessions are not invalidated.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"blueprintUE: Active Sessions Are Not Invalidated After Password Change or Reset","id":"CVE-2026-40587","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"blueprintUE: Authenticated Password Change Does Not Verify Current Password","id":"CVE-2026-40588"},"packages":[],"prev":{"headline":"blueprintUE: Login Endpoint Has No Rate Limiting, Lockout, or Brute-Force Protection","id":"CVE-2026-40586"},"products":["blueprintue-self-hosted-edition"],"published":"2026-04-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-21","vendors":["blueprintue"]},"summary":"Attackers with compromised sessions retain account access indefinitely after password changes because active sessions are not invalidated.","url":"https://insights.sbomify.com/CVE-2026-40587/"}