dbcve.org
CheckmkApplication

CVE-2026-33457

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
Livestatus injection in the prediction graph page in Checkmk <2.5.0b4, <2.4.0p26, and <2.3.0p47 allows an authenticated user to inject arbitrary Livestatus commands via a crafted service name parameter due to insufficient sanitization of the service description value.

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

Livestatus injection in Checkmk's prediction graph page allows authenticated users to inject arbitrary Livestatus commands via a crafted service name parameter. The service description value is not properly sanitized before being used in Livestatus queries, enabling command injection similar to SQL injection but for Checkmk's monitoring data API.

MitigationUpgrade to Checkmk versions 2.5.0b4, 2.4.0p26, or 2.3.0p47 (or later) which contain proper input sanitization for the service description parameter in the prediction graph page.

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.3.0= 2.4.0= 2.5.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
Low
Integrity
Low
Availability
Low

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

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 installation and version
    Run 'cmk --version' or check /omd/sites/*/version file to determine the installed Checkmk version
    Affected if The installed version matches 2.3.0, 2.4.0, or 2.5.0 (or falls within these major version branches)
  2. Verify Livestatus module is enabled
    Check the Checkmk configuration for Livestatus status - typically via 'cmk -L' or by inspecting etc/check_mk/mk-livestatus.mk in the site directory
    Affected if Livestatus is enabled and the service description parameter can be passed to it via the prediction graph interface
  3. Confirm prediction graph feature accessibility
    Check if the prediction graph page is accessible to authenticated users - this is typically accessed via the 'Graphs' or 'Forecast' option in the Checkmk web interface for services
    Affected if Authenticated users can access the prediction graph page and provide a service description parameter

You are affected if your Checkmk version is 2.3.0, 2.4.0, or 2.5.0, Livestatus is enabled, and authenticated users can access the prediction graph page with a service description parameter.

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.5.0b4, 2.4.0p26, or 2.3.0p47 (or later) which contain proper input sanitization for the service description parameter in the prediction graph page.

Recommended fix High confidence

Upgrade to Checkmk 2.3.0p47+ (2.3.x), 2.4.0p26+ (2.4.x), or 2.5.0b4+ (2.5.x); preferably the latest stable patch in your branch

  1. 1. Identify your current Checkmk installation version using 'cmk --version' or the GUI version info
  2. 2. Based on your current version, upgrade to the minimum patched release: 2.3.0p47 or later for the 2.3.x branch, 2.4.0p26 or later for the 2.4.x branch, or 2.5.0b4 or later for the 2.5.x branch
  3. 3. For production environments, upgrade to the latest stable patch version in your current branch to include additional security fixes
  4. 4. If running an older major version, consider upgrading to the latest stable 2.4.x or 2.5.x release for comprehensive security updates
  5. 5. After upgrade, verify the version matches a patched release using 'cmk --version'
Caveat Checkmk upgrades typically require standard backup and test procedures; review release notes for breaking changes between minor versions

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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