# CVE-2026-133165: MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass


- **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
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-3vv6-qprv-c8m6

## What is CVE-2026-133165?

CVE-2026-133165 is a medium-severity vulnerability in misp, published on 19 Nov 2026. 

### Official description

MISP contains an authorization and scope flaw in the ObjectReference model's captureReference method. When a user saves an event (via REST API, sync, or feeds), any object reference included in the payload is looked up by its UUID across the entire MISP instance rather than being scoped to the event being saved. An authenticated user with permission to add or edit events can therefore include the UUID of an object reference belonging to a different event—including events in other organizations that the user cannot view—and cause the system to overwrite that foreign reference's relationship_type, comment, deleted flag, and timestamp with attacker-supplied values. The affected reference is neither deleted nor recreated in the attacker's event; its fields are silently rewritten in place. This constitutes a cross-tenant integrity violation: data integrity of object references in events the attacker has no read or write access to is compromised. The vulnerability is reachable through any event save path (REST add/edit, inter-instance sync, feed ingestion) and requires only a valid authenticated session with event modification privileges and knowledge or discovery of a target reference UUID.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Misp.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*` up to 2.5.51

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

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

## Is CVE-2026-133165 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133165 is a medium-severity vulnerability in misp, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133165 in the wild and no public exploit code.

Affected product: 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-133165/ (Markdown: https://insights.sbomify.com/CVE-2026-133165/index.md)
```

## Sources

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

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