# CVE-2026-54396: MISP AuthKey edit endpoint allows authenticated user email enumeration

> Authenticated users can enumerate email addresses by manipulating user IDs in AuthKey edit requests, exposing sensitive user data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-xcgf-2j9f-cvgv

## What is CVE-2026-54396?

CVE-2026-54396 is a medium-severity vulnerability in misp, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An information disclosure vulnerability exists in the MISP AuthKey edit functionality. When a validation error occurs during an AuthKey edit request, the user dropdown was populated using the attacker-controlled AuthKey.user_id value from the submitted request data. An authenticated user with permission to edit an AuthKey could submit arbitrary user IDs and observe the returned dropdown data, allowing enumeration of user email addresses. The issue is fixed by deriving the dropdown user from the persisted AuthKey owner instead of the request body.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-54396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54396 is a medium-severity vulnerability in misp, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54396 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-54396/ (Markdown: https://insights.sbomify.com/CVE-2026-54396/index.md)
```

## Sources

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

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