dbcve.org
CheckmkApplication

CVE-2025-32915

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Packages downloaded by Checkmk's automatic agent updates on Linux and Solaris have incorrect permissions in Checkmk < 2.4.0p1, < 2.3.0p32, < 2.2.0p42 and <= 2.1.0p49 (EOL). This allows a local attacker to read sensitive data.

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

Checkmk's automatic agent update mechanism on Linux and Solaris downloads packages with overly permissive file permissions (likely world-readable), allowing local unprivileged users to read sensitive data contained within those agent update packages.

MitigationUpgrade to Checkmk versions 2.4.0p1, 2.3.0p32, 2.2.0p42 or later to receive the permission fix; for EOL versions, manually correct permissions on downloaded agent packages or migrate to supported releases.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Determine installed Checkmk version
    Run 'cmk --version' or check /opt/Checkmk/version
    Affected if Version is 2.1.0, 2.2.0, 2.3.0, or 2.4.0 (not patched with p32, p42, or p1 respectively)
  2. Verify automatic agent update is enabled
    Check Checkmk site configuration for agent updater settings, typically via 'omd config' or the Checkmk web interface under Setup > Agents > Agent update
    Affected if Automatic agent update mechanism is configured and active
  3. Locate downloaded agent update packages
    Find the directory where Checkmk stores downloaded agent packages; common paths include /var/lib/checkmk_agent/updates or within the site directory under var/check_mk/agent_cache
    Affected if Agent packages have been downloaded to the system
  4. Inspect file permissions on agent packages
    Use 'ls -la' on the agent package files and check if permissions include world-readable bits (such as 'r--r--r--' or 'rw-r--r--')
    Affected if Packages are readable by any local user (world-readable or group-readable with broad group membership)

User is affected if running a vulnerable Checkmk version (2.1.0 through 2.4.0 without their respective patches) AND the automatic agent update mechanism has downloaded packages that have overly permissive file permissions.

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 to Checkmk versions 2.4.0p1, 2.3.0p32, 2.2.0p42 or later to receive the permission fix; for EOL versions, manually correct permissions on downloaded agent packages or migrate to supported releases.

Recommended fix High confidence

2.4.0p1, 2.3.0p32, or 2.2.0p42 (depending on your branch); 2.1.0 is EOL and requires migration to a supported branch

  1. Identify your current Checkmk version using 'cmk --version' or the web interface
  2. For Checkmk 2.4.0.x: Upgrade to version 2.4.0p1 or later
  3. For Checkmk 2.3.0.x: Upgrade to version 2.3.0p32 or later
  4. For Checkmk 2.2.0.x: Upgrade to version 2.2.0p42 or later
  5. For Checkmk 2.1.0p49 or below: This version is EOL; plan migration to a supported branch (2.2.0p42+, 2.3.0p32+, or 2.4.0p1+)
  6. Download the appropriate patch/release from checkmk.com and follow standard upgrade procedures
  7. After upgrade, verify the automatic agent update functionality works with corrected package permissions
Caveat Review Checkmk release notes for your target version for any breaking changes; note that 2.1.0 is EOL and migration to a newer branch may require additional planning

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32915 — 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-32915 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