# CVE-2026-132643: MISP Anonymised Sightings Reporter Identity Disclosure via Organisation Filter


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-qmpj-rw2f-69jj

## What is CVE-2026-132643?

CVE-2026-132643 is a medium-severity vulnerability in misp, published on 18 Nov 2026. 

### Official description

MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter's organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation's ID in the filter. The query would then return only that organisation's sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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-132643?

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

## Is CVE-2026-132643 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132643 is a medium-severity vulnerability in misp, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132643 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-132643/ (Markdown: https://insights.sbomify.com/CVE-2026-132643/index.md)
```

## Sources

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

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