Quick answers
- Is CVE-2026-7485 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7485 being exploited in the wild.
- How severe is CVE-2026-7485?
- Informational severity, with a CVSS score of 2.3, published 20 August 2026.
- Which products and versions are affected?
- Checkmk <2.5.0p2, <2.4.0p29, <2.3.0p47, all 2.2.0.
- Is there a fix for CVE-2026-7485?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-7485 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-7485?
- 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 an authorization bypass in Checkmk's frozen BI aggregation functionality. When restricted users query aggregations, inaccessible hosts or services are returned as "Service/Host not found" instead of being hidden, allowing attackers to infer the existence and names of monitored infrastructure. The flaw requires authentication and affects versions 2.5.0 before p2, 2.4.0 before p29, 2.3.0 before p47, and all 2.2.0 versions (EOL). The fix prevents restricted users from seeing any details about elements they lack authorization to access, while still reporting genuinely missing elements as "not found".
Affected products
- Checkmk Checkmk <2.5.0p2, <2.4.0p29, <2.3.0p47, all 2.2.0
Timeline
- 2026-04-29: disclosed: Fix released in Checkmk 2.5.0p2, 2.4.0p29, 2.3.0p47
- 2026-08-20: advisory: CVE-2026-7485 published