CVE
MISP privilege escalation via email change in external auth
Affects MISP 2.5.51 and earlier when an external authentication backend (LDAP, Shibboleth, ApacheSecureAuth or CustomAuth) is active. The checked facts name no fixed version or patch ids.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. An external authentication backend (LDAP, Shibboleth, ApacheSecureAuth or CustomAuth) is active
Summary
MISP lets any logged-in non-admin user, including organization admins, change their login email to one that matches a higher-privilege account in an external directory when an external authentication backend such as LDAP or Shibboleth is configured. On the next login, the attacker takes on that directory account's organization and role. An attacker with network access and a low-privilege account can do this remotely.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
An external authentication backend (LDAP, Shibboleth, ApacheSecureAuth or CustomAuth) is activeApply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132144 (MISP: Non-admin users can change login email under external authentication to capture a directory identity), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132144 (entry last updated 2026-11-18):
Affected:
- misp misp: through 2.5.51
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- An external authentication backend (LDAP, Shibboleth, ApacheSecureAuth or CustomAuth) is active (source: https://www.cve.org/CVERecord?id=CVE-2026-132144)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-132144 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132144 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/MISP/MISP/commit/a1fe5058dc758b0e91bb0ff72f622fa99bdfd873
- https://www.cve.org/CVERecord?id=CVE-2026-132144
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132144
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132144"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- misp misp
through 2.5.51
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132144 |
| Record | NVD · CVE-2026-132144 |
| Other links 1 | |
| Patch | GitHub · MISP/MISP · Commit a1fe5058 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132144
Is CVE-2026-132144 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Non-admin users can change the email address tied to their login when external authentication is active. Because that login email is linked to the directory identity, this lets a user capture a directory identity.Source: cve.org
Which versions are affected by CVE-2026-132144?
misp: through 2.5.51.Source: cve.now feed data
Am I affected, and how do I check?
MISP versions up to and including 2.5.51 are affected, but only when an external authentication backend (LDAP, Shibboleth, ApacheSecureAuth or CustomAuth) is active. To check, look at the MISP version and whether external authentication is enabled in the configuration.Source: cve.org
How do I fix CVE-2026-132144?
The checked facts do not name a fixed version or patch identifiers, so the fix cannot be confirmed from them. Check the MISP advisory for the fixed release or patch ids.Source: cve.org