Quick answers
- Is CVE-2026-103682 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103682 being exploited in the wild.
- How severe is CVE-2026-103682?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Checkmk 2.5.0 before 2.5.0p16.
- Is there a fix for CVE-2026-103682?
- Yes: fixed in 2.5.0p16, 3.0.0b1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103682 attacked?
- It is attacked with local access, in a web application.
- Am I affected by CVE-2026-103682?
- 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.
How to fix
- Fixed in: 2.5.0p16, 3.0.0b1
Technical details
The Jolokia special agent passed login passwords as plain-text command-line arguments, making them visible to any user on the Checkmk server who could list processes (ps command). This affected both explicitly configured passwords and those retrieved from the password store. An attacker with local access could harvest credentials while the agent was running, gaining unauthorized access to monitored resources.
Affected products
- Checkmk Checkmk 2.5.0 before 2.5.0p16
Timeline
- 2026-11-06: disclosed
- 2026-09-30: patched