dbcve.org
CheckmkApplication

CVE-2026-7765

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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
Incorrect authorization in the User Messages dashboard widget in Checkmk <2.5.0p5 causes the message-fetching endpoints to return the dashboard creator's messages rather than the viewer's, allowing an attacker who knows a valid public dashboard share token to read the issuer's personal messages by sending requests to the underlying endpoint, even without a User Messages widget present.

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

The User Messages dashboard widget in Checkmk versions before 2.5.0p5 has an authorization flaw where the message-fetching endpoints incorrectly return the dashboard creator's messages instead of the viewer's messages. An attacker with a valid public dashboard share token can directly call the underlying endpoint to read the creator's personal messages, even without the User Messages widget present.

MitigationUpdate Checkmk to version 2.5.0p5 or later to obtain the patched version with proper authorization checks in the message-fetching endpoints.

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.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the installed Checkmk version
    Access the Checkmk web interface and navigate to Setup > General > About Checkmk, or run 'cmk --version' on the command line to retrieve the exact version number
    Affected if The installed version is 2.5.0 (any patch level before p5) or earlier
  2. Determine if public dashboard sharing is enabled
    Review the dashboard settings in the Checkmk web interface under Setup > Dashboards > Embedded graphs or the dashboard's share configuration to see if any dashboards have public share tokens generated
    Affected if At least one dashboard has a public share token active, which allows unauthenticated or external access to the dashboard
  3. Identify dashboards using the User Messages widget
    Navigate through the dashboards in Setup > Dashboards and inspect each dashboard's widget configuration to find any that include the User Messages widget
    Affected if A dashboard with a public share token contains the User Messages widget
  4. Inspect API access logs for message endpoint calls
    Review Checkmk web server logs or audit logs for requests to API endpoints related to user messages (such as /webapi/.../get_messages or similar message retrieval paths) using dashboard share tokens
    Affected if There are API calls to message endpoints using share token authentication that return message data belonging to the dashboard creator rather than the requester

You are affected if running Checkmk 2.5.0 before patch 5, with at least one dashboard that has a public share token and contains the User Messages widget, or if API logs show message endpoints being accessed with share tokens.

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 Checkmk to version 2.5.0p5 or later to obtain the patched version with proper authorization checks in the message-fetching endpoints.

Recommended fix High confidence

2.5.0p5

  1. Identify the current Checkmk version by checking the installation
  2. Upgrade Checkmk to version 2.5.0p5 or later to remediate the authorization vulnerability

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-7765 — 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-7765 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