Quick answers
- Is CVE-2026-33457 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33457 being exploited in the wild.
- How severe is CVE-2026-33457?
- Medium severity, with a CVSS score of 6.3, published 10 April 2026.
- Which products and versions are affected?
- Checkmk Checkmk < 2.5.0b4, < 2.4.0p26, < 2.3.0p47.
- Is there a fix for CVE-2026-33457?
- A patch was published on 2026-03-23: Vendor fix released (Werk #17990) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33457 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-33457?
- 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 Livestatus injection vulnerability exists in Checkmk's user interface, specifically within the prediction graph page. The root cause is the improper neutralization of delimiters (CWE-140) where user-supplied service description values are interpolated into Livestatus queries without sufficient sanitization. An authenticated attacker with network access can exploit this by providing a crafted service name parameter to execute arbitrary Livestatus commands. This could lead to unauthorized data retrieval or modification within the monitoring core. The issue is addressed in versions 2.5.0b4, 2.4.0p26, and 2.3.0p47.
Affected products
- Checkmk Checkmk < 2.5.0b4, < 2.4.0p26, < 2.3.0p47
Timeline
- 2026-03-23: patched: Vendor fix released (Werk #17990)
- 2026-04-10: disclosed: Initial CVE publication
- 2026-04-20: advisory: NIST NVD analysis updated