Skip to main content
Mallory
CriticalVulnerability

CVE-2026-10868: Mass Assignment in MISP UsersController::edit()

Published Jun 4, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.0Critical · v4
EPSS0.24%15th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-10868CWE-915

CVE-2026-10868 is a mass assignment vulnerability in MISP affecting versions up to and including v2.5.38. The flaw exists in the user edit functionality, specifically in UsersController::edit(), where insufficient filtering of user-supplied fields allowed request data to include a user-controlled User.id value. By crafting an edit request that substitutes another user's identifier, an authenticated attacker could cause the application to apply updates to an unintended user account. The issue stems from trusting client-supplied model fields during update processing rather than enforcing the target user identifier server-side.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an authenticated attacker to modify attributes of another user's account without authorization. The exact impact depends on which fields are editable through the affected workflow and on the privileges of the attacking account, but it can compromise account integrity and potentially enable unauthorized changes to user profile or account-related settings. The advisory states there was no known active exploitation at disclosure time and no public proof of concept had been released.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to user edit functionality to the minimum necessary set of authenticated users, closely monitor for suspicious or unexpected account modification activity, and review logs for anomalous user update requests. No complete workaround is described in the advisory; applying the vendor fix is the recommended mitigation.

Remediation

Patch, then assume compromise.

Upgrade MISP to v2.5.39 or later. The vendor addressed the issue by explicitly removing the User.id field from request data before processing the user edit operation, preventing attackers from selecting an unintended target account via crafted input.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-10868 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-10868 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-10868?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-10868.
Is there a patch for CVE-2026-10868?
Upgrade MISP to v2.5.39 or later. The vendor addressed the issue by explicitly removing the User.id field from request data before processing the user edit operation, preventing attackers from selecting an unintended target account via crafted input.
How severe is CVE-2026-10868?
CVE-2026-10868 has a CVSS v4 score of 9.0 (Critical) and an EPSS score of 0.24% (15th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.