Vulnary
← back to the feed
Critical· 9official fix available

CVE-2026-10868

A critical vulnerability in the MISP user edit feature allows an attacker to change another user's account by supplying a different User.id in the request. The flaw arises from insufficient filtering of user-supplied data, enabling unauthorized modifications of account attributes. The issue has been fixed by removing the User.id field from the request before processing edits.

publishedJun 4, 2026
last modifiedJul 22, 2026
sourcesNVD
severity · cvss
9
critical · how bad it is
exploitation · epss
<1%
15th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 23, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

The vulnerability affects the MISP platform’s user editing functionality, regardless of specific version, as the flaw exists in the UsersController::edit() method.

02

Real-world impact

An attacker who can authenticate to the system could craft a request that updates another user's account, potentially altering permissions, email addresses, or other sensitive settings, thereby compromising account integrity.

03

Why this severity

The CVSS score of 9 reflects a network-based attack with low complexity, no privileges required, and no user interaction. The vulnerability allows an attacker to modify user data, which is a high-impact action, leading to a critical rating.

04

What to do about it

official fix available
recommended steps
  1. 01Apply the vendor-provided patch that removes the User.id field from request data before processing user edits.

NVD-referenced vendor advisory

05

Timeline

  1. Jun 4, 2026 · Jun 4, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 22, 2026 · 13d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 24, 2026 · 11d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsPresent
Privileges requiredNone
User interactionNone needed
Confidentiality impactLow
Integrity impactHigh
Availability impactNone
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →