GCVE-1-2026-20341 (CVE-2026-133165)

Vulnerability from gna-1 – Published: 2026-11-19 14:00 – Updated: 2026-11-19 14:00
VLAI
Title
MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass
Summary
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.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CNA (v2.0.3)
Decision recorded 2026-11-19 13:57 UTC
CWE
  • CWE-639 - Authorization Bypass Through User-Controlled Key
  • CWE-640 - Weak Reference Resolution
Assigner
CIRCL GNA GNA-1
GNA scorecard A 91/100 over 279 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
misp misp Affected: 0 , ≤ 2.5.51 (semver)
    cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-19 13:57
Model
qwen3.8:27b
Input
https://github.com/MISP/MISP/commit/c9bd0eff5.patch e307b313d1d2…
Confidence
high
Commit Subject Patch SHA-256
c9bd0eff523b fix: [security] Event saves no longer rewrite other events' e307b313d1d2…
Fix summary

The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference's event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID.

Patch summary

In app/Model/ObjectReference.php, a nine-line guard is inserted in captureReference() immediately after the existing-reference lookup: it casts both the stored event_id and the incoming $eventId to integers and compares them; on mismatch it calls loadLog()->createLogEntry() with a 'warning' severity and a descriptive message, then returns true to skip the update. In tests/testregressions.py, a new ObjectReferenceCaptureScope test class (156 lines) is added with four test methods: (1) event add with a forged foreign UUID leaves the victim reference unchanged and does not create a copy; (2) event edit with a forged foreign UUID leaves the victim reference unchanged; (3) the owner can still update their own reference's comment and timestamp; (4) a genuinely new reference UUID is still created normally. The tests use two separate organizations and least-privileged users to verify cross-tenant isolation.

CVSS rationale

AV:N: MISP is a network-accessible web application with a REST API. AC:L: the attacker only needs to include a known or discovered UUID in a standard event save payload; no race conditions or special timing required. AT:N: no need to intercept or tamper with in-transit data. PR:L: requires an authenticated user with permission to add or edit events (least-privileged role suffices per the regression tests). UI:N: no victim interaction needed. VC:N: the attack writes to records; no confidentiality impact is demonstrated. VI:H: multiple fields (relationship_type, comment, deleted, timestamp) on foreign references can be overwritten, corrupting data integrity. VA:N: setting the deleted flag is a data modification, not a service denial. SC:N: no impact on external systems' confidentiality. SI:H: integrity of data belonging to other organizations within the same MISP instance is compromised. SA:N: no security-functionality impact on other components.

Weakness rationale
  • CWE-639 The object reference UUID is a user-supplied key used to look up and modify a record. The lookup was performed without verifying that the record belongs to the event (and by extension the organization) of the authenticated user, allowing modification of records outside the user's authorization scope.
  • CWE-640 The reference UUID was resolved against the entire instance's object references table rather than being constrained to the event being saved, resulting in resolution to an unintended record in a different event/organization.
Attack pattern rationale
  • CAPEC-114 The attacker manipulates the UUID parameter within a legitimate event save request to target a different object reference record. The application trusts the UUID as a direct pointer without validating ownership scope. CAPEC-114 is the closest match because the core technique is supplying a crafted identifier parameter to redirect a write operation to an unintended resource. Uncertainty: no dedicated CAPEC exists for cross-tenant IDOR via UUID; CAPEC-114 is the best available approximation.
Assumptions to verify
  • The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
  • PR:L assumes the attacker needs only a standard authenticated user with event add/edit permission; the regression tests confirm a least-privileged role suffices.
  • The CAPEC-114 mapping is an approximation; no CAPEC specifically covers cross-tenant IDOR via UUID in a multi-tenant application.
  • VC:N assumes the attack does not enable reading foreign reference data; the patch evidence shows only write/overwrite impact.
  • VA:N assumes setting the 'deleted' flag on a reference is an integrity modification rather than an availability denial; the reference record still exists in the database.
  • The commit date of 2026-11-11 is taken at face value from the patch metadata.
  • No evidence of active exploitation or public PoC was found in the patch or metadata; SSVC exploitation is set to 'none'.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 6 11 high 7
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-11 13:24 UTC Fix developed Corrective change authored (c9bd0eff523b6936b66923830c1c26fe3bee3d53): fix: [security] Event saves no longer rewrite other events' https://github.com/MISP/MISP/commit/c9bd0eff5.patch
  2. 2026-11-19 13:56 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/c9bd0eff5.patch

{
  "containers": {
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "ObjectReference model (app/Model/ObjectReference.php)",
            "Event add/edit (REST, sync, feeds)"
          ],
          "product": "misp",
          "programFiles": [
            "app/Model/ObjectReference.php"
          ],
          "repo": "https://github.com/MISP/MISP",
          "vendor": "misp",
          "versions": [
            {
              "lessThanOrEqual": "2.5.51",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2.5.51",
                  "versionStartIncluding": "0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "iglocska"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Claude Opus 5.5"
        },
        {
          "lang": "en",
          "type": "reporter",
          "value": "ENISA"
        },
        {
          "lang": "en",
          "type": "reporter",
          "value": "Jeroen Pinoy"
        },
        {
          "lang": "en",
          "type": "reporter",
          "value": "CERT.pl"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "MISP contains an authorization and scope flaw in the ObjectReference model\u0027s 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\u2014including events in other organizations that the user cannot view\u2014and cause the system to overwrite that foreign reference\u0027s relationship_type, comment, deleted flag, and timestamp with attacker-supplied values. The affected reference is neither deleted nor recreated in the attacker\u0027s 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."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-114",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-114 Parameter Tampering"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "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",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-19T13:57:00Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-639",
              "description": "CWE-639 Authorization Bypass Through User-Controlled Key",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-640",
              "description": "CWE-640 Weak Reference Resolution",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/MISP/MISP/commit/c9bd0eff5"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference\u0027s event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID."
        }
      ],
      "title": "MISP Object Reference Cross-Event Integrity Violation via UUID Scope Bypass",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.",
                  "PR:L assumes the attacker needs only a standard authenticated user with event add/edit permission; the regression tests confirm a least-privileged role suffices.",
                  "The CAPEC-114 mapping is an approximation; no CAPEC specifically covers cross-tenant IDOR via UUID in a multi-tenant application.",
                  "VC:N assumes the attack does not enable reading foreign reference data; the patch evidence shows only write/overwrite impact.",
                  "VA:N assumes setting the \u0027deleted\u0027 flag on a reference is an integrity modification rather than an availability denial; the reference record still exists in the database.",
                  "The commit date of 2026-11-11 is taken at face value from the patch metadata.",
                  "No evidence of active exploitation or public PoC was found in the patch or metadata; SSVC exploitation is set to \u0027none\u0027."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-114",
                    "rationale": "The attacker manipulates the UUID parameter within a legitimate event save request to target a different object reference record. The application trusts the UUID as a direct pointer without validating ownership scope. CAPEC-114 is the closest match because the core technique is supplying a crafted identifier parameter to redirect a write operation to an unintended resource. Uncertainty: no dedicated CAPEC exists for cross-tenant IDOR via UUID; CAPEC-114 is the best available approximation."
                  }
                ],
                "commit": "c9bd0eff523b6936b66923830c1c26fe3bee3d53",
                "confidence": "high",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "ENISA, Jeroen Pinoy and CERT.pl"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "iglocska"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "Claude Opus 5.5"
                  },
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "ENISA"
                  },
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "Jeroen Pinoy"
                  },
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "CERT.pl"
                  }
                ],
                "cvssRationale": "AV:N: MISP is a network-accessible web application with a REST API. AC:L: the attacker only needs to include a known or discovered UUID in a standard event save payload; no race conditions or special timing required. AT:N: no need to intercept or tamper with in-transit data. PR:L: requires an authenticated user with permission to add or edit events (least-privileged role suffices per the regression tests). UI:N: no victim interaction needed. VC:N: the attack writes to records; no confidentiality impact is demonstrated. VI:H: multiple fields (relationship_type, comment, deleted, timestamp) on foreign references can be overwritten, corrupting data integrity. VA:N: setting the deleted flag is a data modification, not a service denial. SC:N: no impact on external systems\u0027 confidentiality. SI:H: integrity of data belonging to other organizations within the same MISP instance is compromised. SA:N: no security-functionality impact on other components.",
                "draft": false,
                "fixSummary": "The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference\u0027s event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID.",
                "generatedAt": "2026-11-19T13:57:00.911027Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 7,
                      "confidence": "high",
                      "model": "qwen3.8:27b",
                      "score": 6
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "e307b313d1d2d25606f7daa11657394949688c2721f729461a37761c268012e9",
                "patchSummary": "In app/Model/ObjectReference.php, a nine-line guard is inserted in captureReference() immediately after the existing-reference lookup: it casts both the stored event_id and the incoming $eventId to integers and compares them; on mismatch it calls loadLog()-\u003ecreateLogEntry() with a \u0027warning\u0027 severity and a descriptive message, then returns true to skip the update. In tests/testregressions.py, a new ObjectReferenceCaptureScope test class (156 lines) is added with four test methods: (1) event add with a forged foreign UUID leaves the victim reference unchanged and does not create a copy; (2) event edit with a forged foreign UUID leaves the victim reference unchanged; (3) the owner can still update their own reference\u0027s comment and timestamp; (4) a genuinely new reference UUID is still created normally. The tests use two separate organizations and least-privileged users to verify cross-tenant isolation.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "c9bd0eff523b6936b66923830c1c26fe3bee3d53",
                    "date": "Wed, 11 Nov 2026 14:24:50 +0100",
                    "patchSha256": "e307b313d1d2d25606f7daa11657394949688c2721f729461a37761c268012e9",
                    "retrievedAt": "2026-11-19T13:56:17.554618Z",
                    "source": "https://github.com/MISP/MISP/commit/c9bd0eff5.patch",
                    "sourceUrl": "https://github.com/MISP/MISP/commit/c9bd0eff5.patch",
                    "subject": "fix: [security] Event saves no longer rewrite other events\u0027"
                  }
                ],
                "source": "https://github.com/MISP/MISP/commit/c9bd0eff5.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-19T13:57:00Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Event saves no longer rewrite other events\u0027",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-639",
                    "rationale": "The object reference UUID is a user-supplied key used to look up and modify a record. The lookup was performed without verifying that the record belongs to the event (and by extension the organization) of the authenticated user, allowing modification of records outside the user\u0027s authorization scope."
                  },
                  {
                    "cweId": "CWE-640",
                    "rationale": "The reference UUID was resolved against the entire instance\u0027s object references table rather than being constrained to the event being saved, resulting in resolution to an unintended record in a different event/organization."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (c9bd0eff523b6936b66923830c1c26fe3bee3d53): fix: [security] Event saves no longer rewrite other events\u0027",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/c9bd0eff5.patch"
                    ],
                    "timestamp": "2026-11-11T13:24:50Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/MISP/MISP/commit/c9bd0eff5.patch"
                    ],
                    "timestamp": "2026-11-19T13:56:17.554618Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-20341"
        }
      ]
    }
  },
  "cveMetadata": {
    "cveId": "CVE-2026-133165",
    "datePublished": "2026-11-19T14:00:29.363592Z",
    "dateReserved": "2026-11-19T14:00:45.542Z",
    "dateUpdated": "2026-11-19T14:00:45.683673Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2.0"
}


Solutions

CNA
The fix adds an event-scope ownership check in ObjectReference::captureReference(). After locating an existing reference by UUID, the code now verifies that the reference's event_id matches the event currently being saved. If the UUID belongs to a different event, the reference is skipped (neither updated nor recreated in the saving event) and a warning-level system log entry is written recording the blocked operation, the target event ID, and the foreign event ID that owns the UUID.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.