dbcve.org
CheckmkApplication

CVE-2026-3466

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Insufficient sanitization of dashboard dashlet title links in Checkmk 2.2.0 (EOL), Checkmk 2.3.0 before 2.3.0p46, Checkmk 2.4.0 before 2.4.0p25, and Checkmk 2.5.0 (beta) before 2.5.0 allows an attacker with dashboard creation privileges to perform stored cross-site scripting (XSS) attacks by tricking a victim into clicking a crafted dashlet title link on a shared dashboard.

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

Stored XSS vulnerability in Checkmk's dashboard dashlet title links allows attackers with dashboard creation privileges to inject malicious JavaScript through crafted links. When victims interact with these links on shared dashboards, the injected script executes in their browser context.

MitigationUpdate to patched versions (2.3.0p46, 2.4.0p25, 2.5.0p10 or later). Implement proper URL sanitization and output encoding for dashlet title links in dashboard code.

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.2.0= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installed Checkmk version
    Run command: omd version or check the Checkmk web interface under 'Help > About' to view the exact version number
    Affected if The installed version equals 2.2.0, 2.3.0, 2.4.0, or 2.5.0 exactly (not patched point releases)
  2. Locate custom dashboards with dashlet title links
    Navigate to Checkmk web UI > Dashboards > Review any custom or shared dashboards that contain visualizations or data views with configured title links
    Affected if Custom dashboards exist that use dashlet title links pointing to external or custom URLs
  3. Inspect dashlet title link configuration
    Edit a dashboard, open each dashlet, and examine the 'Title URL' or 'Link' field in the dashlet properties to see if any contain unsanitized or crafted URL values
    Affected if Any dashlet title link contains JavaScript://, javascript:, or other script injection patterns in the URL field
  4. Check for shared dashboard usage
    Review which dashboards are shared with other users or published across the organization via the dashboard permission settings
    Affected if Dashboards with configured title links are shared with multiple users who could trigger the stored XSS

A user is affected if their Checkmk version matches exactly 2.2.0, 2.3.0, 2.4.0, or 2.5.0 AND they have shared dashboards containing dashlets with custom title link configurations.

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

Update to patched versions (2.3.0p46, 2.4.0p25, 2.5.0p10 or later). Implement proper URL sanitization and output encoding for dashlet title links in dashboard code.

Recommended fix High confidence

Checkmk 2.3.0p46 (or latest 2.3.x), 2.4.0p25 (or latest 2.4.x), or latest stable 2.5.x - 2.2.0 is EOL with no patch

  1. 1. Identify current Checkmk version using 'cmk --version' command or web interface
  2. 2. Determine which version branch you are on (2.2.x, 2.3.x, 2.4.x, or 2.5.x)
  3. 3. For 2.2.x: This version is End-of-Life (EOL) with no patch available - plan migration to a supported version
  4. 4. For 2.3.x: Upgrade to version 2.3.0p46 or later
  5. 5. For 2.4.x: Upgrade to version 2.4.0p25 or later
  6. 6. For 2.5.x: Upgrade to version 2.5.0 or later stable release
  7. 7. Create a full backup of the Checkmk site before upgrading
  8. 8. Stop the Checkmk site with 'omd stop <sitename>'
Caveat Checkmk 2.2.0 is EOL; upgrade to supported branches. 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
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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