CVE-2026-94381

MISP Privilege Escalation: Read-Only API Key User Can Regain Full Role via updateLoginTime

Published Sep 21, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
MISP has a security issue that can let a user gain more access than their API key is supposed to allow.

A read-only API key should only let someone view information. However, after logging in with such a key, a specific MISP function could accidentally restore the user’s normal account permissions. This means someone with a read-only API key could potentially gain write, delete, or even administrator access if their underlying account has those permissions.

Exploiting the issue requires a valid read-only API key and a single request to the affected function.

The main impact is that MISP’s API key restrictions can be bypassed, allowing actions that the API key was specifically meant to prevent.




Version affected: <2.5.47

Analysis

AI-generated

Technical impact

The vulnerability in MISP allows a user with a read‑only API key to gain the full permissions associated with their underlying account. The flaw is triggered when the updateLoginTime() method re‑authenticates the user, substituting the restricted API‑key permissions with the account’s normal role. An attacker who owns or can obtain a read‑only key, therefore, can effectively elevate privileges to write, delete, or even administrative levels. The impact is a loss of the intended restriction that API keys provide, thereby enabling unauthorized actions on the MISP instance.

Affected Systems

This issue affects the MISP application, specifically versions older than 2.5.47. Any instance running these versions deploys the updateLoginTime() method that performs the re‑authentication step. The vulnerability is tied to the user authentication system within MISP and does not depend on external services.

Risk and Exploitability

The CVSS score of 8.7 classifies this as high severity. The EPSS score is not reported, indicating that no quantified exploitation probability is available, but the flaw can be exercised with a single API request once a read‑only key is in possession. The vulnerability is not listed in the CISA KEV catalog. Based on the description, the likely attack vector is remotely via the MISP REST API, where an actor can send a crafted request to the updateLoginTime endpoint. The condition for exploitation is a valid read‑only API key associated with an account that has elevated roles.

Remediation

Vendor Solution

The fix removes the call to User::getAuthUser() and Auth::login() from the updateLoginTime() method, which was re-authenticating the user with their full role permissions. It replaces this with a call to _refreshAuth(), which refreshes the authentication state while preserving the current (restricted) permission level associated with the API key, preventing privilege escalation.


OpenCVE Recommended Actions

  • Upgrade to MISP 2.5.47 or later, which replaces the re‑authentication call with _refreshAuth() to preserve API‑key restrictions
  • If an upgrade cannot be performed immediately, revoke or delete all read‑only API keys from the affected instance to eliminate the attack surface
  • Verify that no application code or custom plugins invoke updateLoginTime() externally, and disable the endpoint if it is unnecessary for operations

Generated by OpenCVE AI on September 21, 2026 at 15:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Misp
Misp misp
Vendors & Products Misp
Misp misp
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description MISP has a security issue that can let a user gain more access than their API key is supposed to allow. A read-only API key should only let someone view information. However, after logging in with such a key, a specific MISP function could accidentally restore the user’s normal account permissions. This means someone with a read-only API key could potentially gain write, delete, or even administrator access if their underlying account has those permissions. Exploiting the issue requires a valid read-only API key and a single request to the affected function. The main impact is that MISP’s API key restrictions can be bypassed, allowing actions that the API key was specifically meant to prevent. Version affected: <2.5.47
Title MISP Privilege Escalation: Read-Only API Key User Can Regain Full Role via updateLoginTime
Weaknesses CWE-269
References
Metrics cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-269

    Improper Privilege Management

Sources

Status
PUBLISHED
Assigner
CIRCL
Published
Updated
Sep 21, 2026, 2:48 PM
Reserved
Sep 21, 2026, 12:42 PM
Status
Deferred
Published
Sep 21, 2026, 1:17 PM
Modified
Sep 21, 2026, 3:17 PM