> ## 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 sharing group flaw lets sync users read restricted events (CVE-2026-132069)
- URL: https://ping2prompt.com/misp-sharing-group-flaw-sync-users-read-restricted-events-cve-2026-132069/
- Published: 2026-11-18T12:44:31.000Z
- Updated: 2026-11-19T15:26:21.000Z
- Description: CVE-2026-132069, a medium-severity (CVSS 4.0 score 6.3) flaw in MISP's captureSGExisting method, lets sync-role accounts read events in sharing groups they don't belong to. No fixed release is named; check which accounts hold the sync role.
- Author: Ping2Prompt Newsroom
- Tags: MISP, Security tools, Vulnerabilities, Medium, #updated, #short-ping

**Update (2026-11-19):** This advisory has changed: CVE-2026-133190 (MEDIUM): revoked PGP keys still validate protected events, and key revocations pushed by sync partners can be silently dropped., according to [nvd.nist.gov/vuln/detail/CVE-2026-133190](https://nvd.nist.gov/vuln/detail/CVE-2026-133190?ref=ping2prompt.com).

## A sync-role account can read events from foreign sharing groups

CVE-2026-132069 is an authorization bypass in MISP's SharingGroup model, in the `captureSGExisting` method. An account with the sync role can use it to read events in sharing groups it does not belong to. It scores 6.3 under CVSS 4.0, rated medium.

The attacker rewrites the sharing group record, either adding their own organisation as a member or inserting an `all_orgs` server entry for their own MISP instance. Either change gives read access to every event in that group, which exposes restricted threat intelligence. It also allows limited modification of the sharing group record itself.

## Why the sync permission skips the membership check

The authorization check combined two conditions with a logical AND: the membership check and a test that the user lacks the sync permission (`perm_sync`). The original condition was `if (!checkIfAuthorised(...) && !perm_sync) return false`, so any sync-role user passes whether or not they belong to the target group.

## Who can reach the bug and how

The attacker needs an authenticated account with the sync role and a valid UUID for a non-local sharing group. They can send the request to the `/sharing_groups/add` endpoint or embed a SharingGroup object in pushed sync data. No user interaction is needed.

The sources do not say which releases are affected, so you cannot confirm exposure from a release number. The exploitation status is unknown (the sources do not say).

## No fixed MISP release is named yet

No fixed version or release number is published. According to the NVD, its record is marked "Deferred" and references one MISP GitHub commit, `58b38a20f7231a569b896432f6cedcd7bf31a4b4`. The sources do not describe that commit as the fix, and they list no workaround.

The flaw needs a sync-role account plus a group UUID, so it is worth knowing which accounts on your instance hold that role. Watch the MISP project for a release or advisory that names this CVE.

## Sources

- [nvd.nist.gov/vuln/detail/CVE-2026-133190](https://nvd.nist.gov/vuln/detail/CVE-2026-133190?ref=ping2prompt.com)
- [nvd.nist.gov/vuln/detail/CVE-2026-132069](https://nvd.nist.gov/vuln/detail/CVE-2026-132069?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).