dbcve.org
CheckmkApplication

CVE-2025-32917

HIGH · 8.8 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Privilege escalation in jar_signature agent plugin in Checkmk versions <2.4.0b7 (beta), <2.3.0p32, <2.2.0p42, and 2.1.0p49 (EOL) allow user with write access to JAVA_HOME/bin directory to escalate privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The jar_signature agent plugin in Checkmk contains a privilege escalation vulnerability. An attacker with write access to the JAVA_HOME/bin directory can manipulate JAR files executed by the plugin to gain elevated privileges. The vulnerability affects multiple versions across multiple Checkmk branches.

MitigationUpgrade Checkmk to version 2.4.0b7 or later, 2.3.0p32 or later, 2.2.0p42 or later. Restrict write access to the JAVA_HOME/bin directory to prevent exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CheckmkApplication
Affected:= 2.1.0= 2.2.0= 2.3.0= 2.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Checkmk version
    Run command: omd version or check /etc/checkmk/version file
    Affected if Version is 2.1.0, 2.2.0, 2.3.0, or 2.4.0 exactly as listed in affected versions
  2. Verify jar_signature plugin is enabled
    Check for jar_signature in the agent plugins directory (usually ~/share/check_mk/agents/plugins/ or /usr/lib/check_mk_agent/plugins/) and confirm it is deployed on the monitored system
    Affected if The jar_signature plugin is installed and active on the monitored system
  3. Locate JAVA_HOME directory
    Run: echo $JAVA_HOME or check Checkmk agent configuration for JAVA_HOME setting
    Affected if JAVA_HOME is set and points to a directory on the system
  4. Check write permissions on JAVA_HOME/bin
    Run: ls -la $JAVA_HOME/bin (or the discovered JAVA bin path) and inspect write permissions for non-privileged users
    Affected if Any unprivileged user or attacker has write access to the JAVA_HOME/bin directory and can modify JAR files executed by the jar_signature plugin

You are affected if you run Checkmk versions 2.1.0, 2.2.0, 2.3.0, or 2.4.0 with the jar_signature plugin enabled and the JAVA_HOME/bin directory is writable by non-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Checkmk to version 2.4.0b7 or later, 2.3.0p32 or later, 2.2.0p42 or later. Restrict write access to the JAVA_HOME/bin directory to prevent exploitation.

Recommended fix High confidence

Minimum fixed versions: 2.2.0p42, 2.3.0p32, 2.4.0b7 (or latest stable 2.4.x); 2.1.0p49 is EOL - migrate to supported branch

  1. Identify your current Checkmk version using 'cmk --version' or the web interface
  2. Backup your Checkmk configuration and data before proceeding
  3. For Checkmk 2.1.x: Upgrade to version 2.1.0p49 or migrate to a supported branch (2.2.x, 2.3.x, or 2.4.x)
  4. For Checkmk 2.2.x: Upgrade to version 2.2.0p42 or later
  5. For Checkmk 2.3.x: Upgrade to version 2.3.0p32 or later
  6. For Checkmk 2.4.x: Upgrade to version 2.4.0b7 (beta) or later stable release
  7. After upgrade, verify the jar_signature agent plugin works correctly and restrict write access to JAVA_HOME/bin directory
Caveat 2.1.0 is End-of-Life; migration to 2.2.x/2.3.x/2.4.x required; review Checkmk migration guides for breaking changes between major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Checkmk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32917 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32917 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data