Quick answers
- Is CVE-2026-44379 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44379 being exploited in the wild.
- How severe is CVE-2026-44379?
- Medium severity, with a CVSS score of 5.3, published 13 May 2026.
- Which products and versions are affected?
- MISP Project MISP < 2.5.37.
- Is there a fix for CVE-2026-44379?
- A patch was published on 2026-05-13: Fixed in version 2.5.37 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44379 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44379?
- Check whether you run Misp. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An improper input validation vulnerability (CWE-20) exists in MISP prior to version 2.5.37 within the Collections component. The application failed to validate the 'uuid' field against the RFC 4122 standard during record creation or modification. An authenticated attacker with permissions to manage Collections can submit arbitrary strings in place of valid UUIDs. This can cause downstream logic errors or database integrity issues in components that assume these identifiers are strictly formatted. The issue was resolved in version 2.5.37 by implementing model-level validation in app/Model/Collection.php.
Affected products
- MISP Project MISP < 2.5.37
Timeline
- 2026-04-29: advisory: GitHub Security Advisory published
- 2026-05-13: disclosed: CVE published to NVD
- 2026-05-13: patched: Fixed in version 2.5.37