# CVE-2026-24095: Missing Permission Check on Analyze Configuration Page

> Users with WATO permissions can bypass authorization checks to access configuration analysis and perform unauthorized actions like disabling checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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:** 9 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-2wv3-wwxg-29gh, UBUNTU-CVE-2026-24095

## What is CVE-2026-24095?

CVE-2026-24095 is a medium-severity missing authorization vulnerability in Checkmk, published on 9 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper permission enforcement in Checkmk versions 2.4.0 before 2.4.0p21, 2.3.0 before 2.3.0p43, and 2.2.0 (EOL) allows users with the "Use WATO" permission to access the "Analyze configuration" page by directly navigating to its URL, bypassing the intended "Access analyze configuration" permission check. If these users also have the "Make changes, perform actions" permission, they can perform unauthorized actions such as disabling checks or acknowledging results.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-24095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24095 is a medium-severity missing authorization vulnerability in Checkmk, published on 9 Feb 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-24095 in the wild and no public exploit code.

Affected product: Checkmk. 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-24095/ (Markdown: https://insights.sbomify.com/CVE-2026-24095/index.md)
```

## Sources

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

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