CVE-2026-81846: runZero Platform MCP authorization bypass

CVE-2026-81846 · Severity: low · CVSS 3.5 · Published 2026-09-01

The runZero Platform's Model Context Protocol (MCP) service contains an authorization flaw that could allow authenticated users with limited privileges to access sensitive vulnerability findings summaries they should not have permission to view. This could lead to disclosure of security assessment data to unauthorized personnel within an organization.

Quick answers

Is CVE-2026-81846 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-81846 being exploited in the wild.
How severe is CVE-2026-81846?
Low severity, with a CVSS score of 3.5, published 1 September 2026.
Which products and versions are affected?
runZero Platform before 5.1.260826.0.
Is there a fix for CVE-2026-81846?
A patch was published on 2026-09-08: fix released in version 5.1.260826.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-81846 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-81846?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an authorization bypass (CWE-639: Authorization Bypass Through User-Controlled Key) in the runZero Platform MCP service that allows authenticated users to access findings summaries without proper authorization checks. The flaw requires an authenticated user with low privileges and specific network conditions (high complexity attack), but no user interaction. An attacker can read sensitive vulnerability data they are not authorized to access. The issue has been patched in version 5.1.260826.0 and later.

Affected products

  • runZero Platform before 5.1.260826.0

Timeline

  • 2026-09-01: disclosed
  • 2026-09-08: patched: fix released in version 5.1.260826.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.