Skip to main content
Menu
CVEs

MISP cross-event object reference tampering via UUID bypass

CVE-2026-133165Published November 19, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

MISP has a flaw in how it handles object references when an event is saved through its REST API, sync, or feed ingestion. A remote attacker with low privileges and a valid login can overwrite the relationship type, comment, deleted flag, and timestamp of object references in other events, including events in other organizations they cannot view, if they know the reference's UUID and have permission to add or edit events.

Written by a model

Original 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.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133165 (MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133165 (entry last updated 2026-11-19):
Affected:
- misp misp: through 2.5.51
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133165 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133165 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/MISP/MISP/commit/c9bd0eff5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133165
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133165"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133165
RecordNVD · CVE-2026-133165
Other links 1
PatchGitHub · MISP/MISP · Commit c9bd0eff

Questions about CVE-2026-133165

Is CVE-2026-133165 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133165?

misp: through 2.5.51.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.