CVE-2026-132144
8.3HighPublished 18 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite
High
0CVSS v4.010
- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User action
- None
- Impact
- High impact on integrity
- Weakness
- CWE-285, CWE-639
What an attacker gets
Authenticated users can escalate privileges to any account within the external directory by changing their login email. This requires an active session and an instance configured with external authentication like LDAP or Shibboleth.
Root cause
The __canChangeLogin() method fails to verify if an external authentication backend is active before allowing users to modify their login email address.
Affected versions
Versions not listed — check the vendor advisory.
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade to the latest version of MISP containing the fix for the __canChangeLogin() logic. As an interim mitigation, disable user login changes in the MISP configuration settings.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
MISP contains an authorization flaw in the user login-email change logic. When an external authentication backend is configured (LDAP, Shibboleth, ApacheSecureAuth, or CustomAuth), the login email address serves as the key by which the directory service resolves a user's identity, organization, and role on each login. The __canChangeLogin() method in UsersController only checked the MISP.disable_user_login_change setting and site-admin status; it did not account for whether an external authentication backend was active. As a result, any authenticated non-admin user (including org admins) could change their own login email to an address that matches a higher-privilege account in the external directory. On the user's next login, the external backend would resolve that email to the target directory identity, granting the attacker the organization and role associated with that identity. This constitutes an account-identity capture and privilege escalation: the attacker effectively assumes the identity of any directory account whose email they can guess or discover. The vulnerability requires an authenticated session with a valid API key or session token and a MISP instance configured with at least one external authentication backend. The impact is limited to the scope of the captured directory identity's privileges within MISP.