Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Blue MISP Intelligence Network

    MISP correlation endpoint leaks hidden attribute values to any logged-in user

    Automated source check

    MISP

    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

    Image: “Keys Padlocks” by Leeroy, CC0 1.0, via stocksnap (Openverse)


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion