CVE-2026-9136

What it is

A vulnerability was identified in the ShadowAttribute proposal creation workflow. The add action accepted user-controlled ShadowAttribute request data without removing the id field before saving the record. Because the underlying framework treats a supplied primary key as an instruction to update an existing record, an authenticated user able to submit shadow attribute proposals could provide the identifier of an existing ShadowAttribute and cause that record to be updated instead of creating a new proposal. This can result in unauthorized modification of existing shadow attributes, potentially affecting proposals associated with events the user should not be able to alter. Depending on deployment configuration and accessible API responses, the issue may also expose or move proposal data across event contexts. The vulnerability is caused by trusting a client-supplied primary key during object creation. The fix removes the id field from incoming ShadowAttribute data before processing, ensuring that the endpoint always creates a new proposal rather than updating an existing one. This has been fixed in MISP 2.5.38.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data tampering.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-05-20 20:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-07-23 15:10 UTC Last updatedMost recent change to the record

Details

Published

2026-05-20 20:16 UTC

Last modified

2026-07-23 15:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-639 · Insecure direct object reference

Record status

Analyzed

Affected

• misp-project Misp < 2.5.38

Attack profile CVSS 4.0 · 8.3

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

None

Integrity

High

Availability

None