dbcve.org
CheckmkApplication

CVE-2025-2092

HIGH · 7.5 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Insertion of Sensitive Information into Log File in Checkmk GmbH's Checkmk versions <2.3.0p29, <2.2.0p41 and <=2.1.0p49 (EOL) causes remote site authentication secrets to be written to log files accessible to administrators.

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 versions prior to 2.3.0p29 and 2.2.0p41 contain a log injection vulnerability where remote site authentication secrets are written in plaintext to log files. These logs are accessible to administrators with file system access, exposing credentials that could be used to compromise remote monitoring sites.

MitigationUpgrade Checkmk to version 2.3.0p29 or 2.2.0p41 or later. Additionally, audit and purge existing log files that may contain exposed authentication secrets.

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.1.0= 2.2.0= 2.3.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Checkmk version
    Run 'omd version' or check /omd/lib/python/cmk/gui/versions.py or the Checkmk web interface under 'Help > About'. Compare the installed version to the affected ranges: versions 2.1.0 through 2.3.0 (prior to patches 2.3.0p29 and 2.2.0p41).
    Affected if The installed version is 2.1.0, 2.2.0, 2.3.0, or any version below 2.3.0p29 or 2.2.0p41.
  2. Determine if remote site monitoring is configured
    Check the Checkmk configuration for distributed monitoring or remote site connections. This is typically found in the web UI under 'Setup > General > Distributed Monitoring' or by inspecting the distributed monitoring configuration file.
    Affected if Remote site monitoring or distributed monitoring is enabled with authentication secrets configured.
  3. Locate log files that may contain authentication data
    Check the Checkmk log directory. Typical locations include /omd/sites/{sitename}/var/log/ or the logs directory specified in the Checkmk configuration. Look for logs related to distributed monitoring, remote site sync, or authentication.
    Affected if Log files exist in Checkmk log directories, particularly those recording site synchronization or authentication events.
  4. Inspect logs for plaintext authentication secrets
    Search log files for patterns that may indicate authentication secrets, API keys, or passwords in plaintext. Use commands like 'grep -r "secret"' or 'grep -r "password"' on log directories, focusing on files related to remote site communication.
    Affected if Log files contain plaintext authentication credentials, API keys, or secrets associated with remote site connections.

You are affected if you run Checkmk version 2.1.0 through 2.3.0 (prior to patches), have remote site monitoring configured, and log files contain plaintext authentication secrets.

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
Upgrade available Upgrade to 2.1.0 or later
Fixed in 2.1.0
Interim mitigation

Upgrade Checkmk to version 2.3.0p29 or 2.2.0p41 or later. Additionally, audit and purge existing log files that may contain exposed authentication secrets.

Recommended fix High confidence

2.3.0p29 (or latest 2.3.x), 2.2.0p41 (or latest 2.2.x), or 2.1.0p49 (2.1.x is EOL)

  1. 1. Identify your current Checkmk version by running 'cmk --version' or checking the version in the GUI
  2. 2. Determine which version branch you are on (2.1.x, 2.2.x, or 2.3.x)
  3. 3. For 2.3.x branch: upgrade to version 2.3.0p29 or later
  4. 4. For 2.2.x branch: upgrade to version 2.2.0p41 or later
  5. 5. For 2.1.x branch: upgrade to version 2.1.0p49 or later (note: 2.1.x is EOL, consider migrating to a supported branch)
  6. 6. After upgrade, review and secure log files that may contain previously logged sensitive information
  7. 7. Rotate any exposed authentication secrets for remote sites
Caveat Version 2.1.0 is End-of-Life; consider migrating to 2.2.x or 2.3.x branch for continued support

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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