dbcve.org
CheckmkApplication

CVE-2026-7186

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-08
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
Stored cross-site scripting in the URL dashboard widget in Checkmk <2.5.0p5, <2.4.0p31, <2.3.0p48, and all 2.2.0 versions allows a user with dashboard editing permissions to store a URL with a dangerous URI scheme such as javascript: that executes scripts in other users' browsers when they view the 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 in Checkmk's URL dashboard widget allows authenticated users with dashboard editing permissions to inject malicious JavaScript via javascript: URIs. When other users view the affected dashboard, the injected script executes in their browsers, potentially allowing session hijacking or data theft.

MitigationUpgrade to Checkmk versions 2.5.0p5, 2.4.0p31, or 2.3.0p48 or later. Until patched, restrict dashboard editing permissions to trusted users only.

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 Checkmk version
    Run 'cmk --version' or check the About page in the Checkmk web interface
    Affected if Installed version is 2.2.0, 2.3.0, 2.4.0, or 2.5.0 (prior to respective patches)
  2. Check for URL dashboard widgets
    Navigate to Setup > Dashboards > Monitors and review each dashboard for URL widgets, or query the configuration database for widgets of type 'url'
    Affected if Any dashboard contains a URL widget that could accept arbitrary URIs
  3. Inspect URL widget configurations for javascript: URIs
    Examine the URL field in each URL widget configuration for 'javascript:' scheme entries; export dashboards to JSON and search for 'javascript:' strings
    Affected if Any URL widget contains a URI starting with 'javascript:'
  4. Review dashboard editing permissions
    Check user/role permissions under Setup > Users or Setup > Roles to identify which users have 'Edit dashboards' permission
    Affected if Non-admin users have dashboard editing permissions and could inject malicious URLs

You are affected if you run an unpatched Checkmk version (2.2.0, 2.3.0, 2.4.0, or 2.5.0) and have dashboards with URL widgets that may contain or could accept javascript: URIs from users with editing rights.

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.0p5, 2.4.0p31, or 2.3.0p48 or later. Until patched, restrict dashboard editing permissions to trusted users only.

Recommended fix High confidence

2.5.0p5 (or later), 2.4.0p31 (or later), 2.3.0p48 (or later), or migrate off 2.2.0 to a supported branch

  1. Identify the currently installed Checkmk version using 'cmk --version' or the web interface
  2. Based on the current version, upgrade to the minimum patched version: For 2.5.0.x, upgrade to 2.5.0p5 or later; For 2.4.0.x, upgrade to 2.4.0p31 or later; For 2.3.0.x, upgrade to 2.3.0p48 or later; For 2.2.0.x, upgrade to a supported newer branch (2.3.0p48+, 2.4.0p31+, or 2.5.0p5+)
  3. Download the appropriate Checkmk package from the official Checkmk download site (checkmk.com)
  4. Follow standard Checkmk upgrade procedures: backup the site, stop the site, install the new package, start the site, and run the automated migration
Caveat Checkmk minor version upgrades may require migration steps; review release notes before upgrading; test in non-production environment first

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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