# CVE-2026-133177: MISP: Insufficient Authorization Allows Sync Users and External Feeds to Overwrite Organisation Details


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-5wv5-vfhm-2wrf

## What is CVE-2026-133177?

CVE-2026-133177 is a medium-severity vulnerability in MISP, published on 19 Nov 2026. 

### Official description

MISP contains an authorization flaw in the sharing group capture logic. When a sharing group is re-captured with a newer modified timestamp and an updated roster, the application unconditionally overwrote the type, nationality, sector, and contacts fields of every organisation listed in the roster, including the host organisation. This behaviour was reachable by any user holding the perm_sync role, and additionally by any external server pulled from or any feed fetched, because those operations execute with the privileges of the site administrator who initiated them. As a result, a low-privileged sync user or a malicious/compromised external feed or pull source could silently corrupt organisation records on the receiving MISP instance without any site-admin or internal-sync authorization. The vulnerability does not disclose data or affect availability; the impact is limited to integrity of organisation metadata (type, nationality, sector, contacts). The fix restricts organisation detail updates to internal sync operations (pulls over links flagged as internal, or senders holding perm_sync_internal) and site administrators; all other sync, pull, and feed operations may only match existing organisations by UUID or create new ones, without modifying their stored details.

Weakness: CWE-862 (Missing Authorization), CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Misp.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*` up to 2.5.51

## How do I fix CVE-2026-133177?

No fix has been published for CVE-2026-133177 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-133177 being exploited?

There is no known exploitation of CVE-2026-133177 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133177 and fix it if it is affected.

What it is: CVE-2026-133177 is a medium-severity vulnerability in MISP, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133177 in the wild and no public exploit code.

Affected product: MISP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133177/ (Markdown: https://insights.sbomify.com/CVE-2026-133177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133177
- OSV: https://osv.dev/vulnerability/CVE-2026-133177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133177/
Summaries are generated and may contain mistakes; the official description above is the record.
