# CVE-2026-81846: runZero MCP 'Findings summaries' Data Leak

> An authorization bypass in the runZero Platform MCP service allows attackers to access findings summaries without proper permissions.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A: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:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-29cr-9cjx-c8cg

## What is CVE-2026-81846?

CVE-2026-81846 is a low-severity authentication bypass vulnerability in runZero Platform, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authorization bypass in the runZero Platform MCP service has been resolved in version 5.1.260826.0. This issue is an instance of CWE-639: Authorization Bypass Through User-Controlled Key and has an estimated CVSS score of CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N (3.5 Low).

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-81846 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81846 is a low-severity authentication bypass vulnerability in runZero Platform, published on 1 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-81846 in the wild and no public exploit code.

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

## Sources

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

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