CVE-2026-44379: MISP: Improper UUID validation in MISP Collections
MISP is an open source threat intelligence and sharing platform. Prior to 2.5.37, MISP Collections did not enforce RFC 4122 UUID validation on the uuid field. As a result, a user able to create or modify Collection records could submit malformed UUID values, potentially causing integrity issues or unexpected behaviour in code paths that assume Collection UUIDs are valid identifiers. This vulnerability is fixed in 2.5.37.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MISP Collectionsto a version that resolves this vulnerability.Fixed in 2.5.37
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44379?
CVE-2026-44379 has been classified as a medium severity vulnerability due to improper validation of UUIDs in MISP Collections.
How do I fix CVE-2026-44379?
To mitigate CVE-2026-44379, upgrade to MISP version 2.5.37 or later, which enforces proper UUID validation.
What impact does CVE-2026-44379 have on MISP?
CVE-2026-44379 can lead to the potential submission of malformed UUIDs, which may compromise data integrity within MISP Collections.
Who is affected by CVE-2026-44379?
Users of MISP versions prior to 2.5.37 are at risk from CVE-2026-44379 due to the lack of UUID validation.
What components of MISP does CVE-2026-44379 affect?
CVE-2026-44379 specifically affects the MISP Collections component related to UUID handling.