# CVE-2026-132144: MISP: Non-admin users can change login email under external authentication to capture a directory identity


- **Severity:** High 8.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-hprw-9pvx-h67v

## What is CVE-2026-132144?

CVE-2026-132144 is a high-severity vulnerability in misp, published on 18 Nov 2026. 

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-132144?

It affects 1 product.


Products: Misp.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*` up to 2.5.51

## How do I fix CVE-2026-132144?

No fix has been published for CVE-2026-132144 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-132144 being exploited?

There is no known exploitation of CVE-2026-132144 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132144 and fix it if it is affected.

What it is: CVE-2026-132144 is a high-severity vulnerability in misp, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132144 in the wild and no public exploit code.

Affected product: misp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132144/ (Markdown: https://insights.sbomify.com/CVE-2026-132144/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132144
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132144
- OSV: https://osv.dev/vulnerability/CVE-2026-132144

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132144/
Summaries are generated and may contain mistakes; the official description above is the record.
