> ## Content Index
> Fetch the complete content index at: https://ping2prompt.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# MISP correlation endpoint leaks hidden attribute values to any logged-in user
- URL: https://ping2prompt.com/misp-correlation-endpoint-leaks-hidden-attribute-values/
- Published: 2026-11-18T21:24:23.000Z
- Updated: 2026-11-19T14:01:06.000Z
- Description: MISP's eventCorrelations endpoint lets any logged-in user read hidden attribute values from other organisations' events (CVE-2026-132637, CVSS 4.0 score 5.3). No fixed version is named; check whether your git tree contains commit b7c1071d1.
- Author: Ping2Prompt Newsroom
- Tags: MISP, Security tools, Vulnerabilities, Medium, #auto, #short-ping

## Any MISP account can read other organisations' hidden attributes

An authenticated MISP user with any role can request correlation results for an event owned by another organisation, using only its event ID. The response includes attribute IDs and values from an organisation-only event. Correlations keyed by hidden attributes also come back with IDs and values.

That covers organisation-only attributes, attributes in sharing groups the user is not in, and attributes in organisation-only objects. The leaked data can include threat-intelligence values such as IP addresses and domain names. It also confirms that events the user cannot see exist.

NVD gives CVE-2026-132637 a CVSS 4.0 base score of 5.3, rated medium. ENISA reported the flaw.

## Missing view check in the eventCorrelations action

The flaw sits in the `eventCorrelations` action of `CorrelationsController`, at the `correlations/eventCorrelations` endpoint, and in the Default and OnDemand correlation engines. The action never checked whether the requesting user could view the event named by the event ID parameter. The engines also filtered only the related side of each correlation, not the queried event's own source attributes.

Separately, the Default engine's related-event listing used in `events/view` also included events related only through hidden attributes. An attacker needs a valid session with any role and must know or enumerate a target event ID.

## Which MISP versions are exposed is not listed

The NVD record does not list the affected MISP versions. Any instance with user accounts you do not fully trust, including accounts from partner organisations, is where the exposure matters, since any role is enough. The NVD record does not say whether the flaw has been exploited in the wild.

## No fixed MISP version yet: track commit b7c1071d1

No fixed MISP version is stated, only a referenced commit. The NVD reference for the fix is the MISP GitHub commit `b7c1071d1`. If you run MISP from a git checkout, you can check whether your tree contains that commit.

No workaround is given for affected instances. The NVD record lists the status as Deferred and gives no disclosure or publication date.

## Sources

- [nvd.nist.gov/vuln/detail/CVE-2026-132637](https://nvd.nist.gov/vuln/detail/CVE-2026-132637?ref=ping2prompt.com)

Image: [“Keys Padlocks” by Leeroy, CC0 1.0, via stocksnap (Openverse)](https://stocksnap.io/photo/keys-padlocks-D5D3B74933?ref=ping2prompt.com)

---

This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our [editorial methodology](https://ping2prompt.com/about-how-we-work/) and the [corrections log](https://ping2prompt.com/corrections/). Spotted an error? Email [editor@ping2prompt.com](mailto:editor@ping2prompt.com).