# CVE-2026-44379: MISP: Improper UUID validation in MISP Collections

> Attackers can submit malformed UUIDs in MISP Collections, causing integrity issues or unexpected behavior in dependent code paths.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-jrvj-84mg-8f29

## What is CVE-2026-44379?

CVE-2026-44379 is a medium-severity vulnerability in Misp-Project Misp, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-44379?

It affects 1 product.


Products: Misp-Project Misp.

## How do I fix CVE-2026-44379?

No fix has been published for CVE-2026-44379 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44379 being exploited?

There is no known exploitation of CVE-2026-44379 in the wild and no public exploit code.

## Other vulnerabilities in Misp-Project Misp

- [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8)
- [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8)
- [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44379 and fix it if it is affected.

What it is: CVE-2026-44379 is a medium-severity vulnerability in Misp-Project Misp, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44379 in the wild and no public exploit code.

Affected product: Misp-Project Misp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44379/ (Markdown: https://insights.sbomify.com/CVE-2026-44379/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44379
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44379
- OSV: https://osv.dev/vulnerability/CVE-2026-44379

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44379/
Summaries are generated and may contain mistakes; the official description above is the record.