Is CVE-2026-15227 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-15227 being exploited in the wild.

How severe is CVE-2026-15227?

Informational severity, with a CVSS score of 5.3, published 31 July 2026.

Which products and versions are affected?

Checkmk GmbH Checkmk < 2.5.0p10, < 2.4.0p35, < 2.3.0p49, 2.2.0 (EOL).

Is there a fix for CVE-2026-15227?

A patch was published on 2026-07-09: Fix released in multiple versions via Werk #20003 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-15227 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-15227?

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.

CVE-2026-15227: Checkmk missing authorization in reporting component

Q: Is there a fix for CVE-2026-15227?

A patch was published on 2026-07-09: Fix released in multiple versions via Werk #20003 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-15227 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-15227?

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.

CVE-2026-15227 · Severity: info · CVSS 5.3 · Published 2026-07-31

Checkmk, an IT infrastructure monitoring platform, contains a security flaw that allows users to modify reports they do not own. Even if a user lacks the specific 'Edit foreign Reports' permission, they can still change reports created by other staff members. This could lead to unauthorized changes in monitoring data presentation or the disruption of reporting workflows. Organizations should update to the latest patched versions to ensure proper access controls are enforced.

Quick answers

Is CVE-2026-15227 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-15227 being exploited in the wild.
How severe is CVE-2026-15227?: Informational severity, with a CVSS score of 5.3, published 31 July 2026.
Which products and versions are affected?: Checkmk GmbH Checkmk < 2.5.0p10, < 2.4.0p35, < 2.3.0p49, 2.2.0 (EOL).
Is there a fix for CVE-2026-15227?: A patch was published on 2026-07-09: Fix released in multiple versions via Werk #20003 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-15227 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-15227?: 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

A missing authorization check (CWE-862) in the reporting component of Checkmk allows authenticated users to bypass intended access controls. Specifically, users who lack the 'Edit foreign Reports' permission can still modify reports belonging to other users. The vulnerability is reachable over the network by any user with basic authenticated access to the Checkmk interface. This issue affects Enterprise editions across several major versions. Patches have been released in versions 2.5.0p10, 2.4.0p35, and 2.3.0p49.

Affected products

Checkmk GmbH Checkmk < 2.5.0p10, < 2.4.0p35, < 2.3.0p49, 2.2.0 (EOL)

Timeline

2026-07-09: patched: Fix released in multiple versions via Werk #20003
2026-07-31: disclosed: CVE published to NVD

References

https://checkmk.com/werk/20003

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