Quick answers
- Is CVE-2026-17548 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17548 being exploited in the wild.
- How severe is CVE-2026-17548?
- Informational severity, with a CVSS score of 5.3, published 25 August 2026.
- Which products and versions are affected?
- Checkmk <2.5.0p12, <2.4.0p36, <2.3.0p50, all 2.2.0 versions.
- Is there a fix for CVE-2026-17548?
- A patch was published on 2026-08-05: Patches released for versions 2.5.0p12, 2.4.0p36, 2.3.0p50, and 3.0.0b1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17548 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-17548?
- Check whether you run Checkmk at an affected version. 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 a missing authorization check in Checkmk's background job viewing functionality. An authenticated user who obtains the ID of a background job—either through guessing (for predictable jobs like autodiscovery) or from other means—can access the job's status and results without proper permission validation. The vulnerability requires network access and valid authentication credentials. While background jobs like "activate changes" use random UUIDs making exploitation unlikely, others like "autodiscovery" are more discoverable. The vendor did not identify confirmed sensitive data exposure in testing, but job results could potentially contain system configuration or monitoring details. Patches are available in Checkmk 2.5.0p12, 2.4.0p36, 2.3.0p50, and 3.0.0b1 or later.
Affected products
- Checkmk Checkmk <2.5.0p12, <2.4.0p36, <2.3.0p50, all 2.2.0 versions
Timeline
- 2026-08-25: disclosed
- 2026-08-05: patched: Patches released for versions 2.5.0p12, 2.4.0p36, 2.3.0p50, and 3.0.0b1