# CVE-2026-95805: MISP ACLComponent: Typo in previewEventAttributes ACL key bypasses intended access restriction

> A typo in MISP's ACL configuration allows unauthorized users to access sensitive event attribute data via the previewEventAttributes endpoint.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-c2r5-m9w2-228q

## What is CVE-2026-95805?

CVE-2026-95805 is a medium-severity missing authorization vulnerability in MISP, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A typo in the MISP ACLComponent access control configuration caused the ACL rule for the previewEventAttributes action to reference the permission string 'theming_enabled*' (with a trailing asterisk) instead of the correct 'theming_enabled'. In the MISP ACL system, the array values define which role or permission grants access to a given controller action. The adjacent entry previewEventObjects correctly uses ['theming_enabled'], confirming the intended restriction. The malformed key 'theming_enabled*' does not match any valid permission identifier, causing the access control check for previewEventAttributes to malfunction. Depending on the ACL evaluation logic, this could result in either unauthorized users gaining access to the previewEventAttributes endpoint (authorization bypass) or legitimate users being denied access (availability impact). 

The previewEventAttributes endpoint exposes event attribute data within MISP so an authorization bypass could expose sensitive indicator and attribute data to users who should not have access.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-95805 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95805 is a medium-severity missing authorization vulnerability in MISP, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95805 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-95805/ (Markdown: https://insights.sbomify.com/CVE-2026-95805/index.md)
```

## Sources

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

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