/

CVE-2026-85390

Severity:

HIGH RISK

(7.1)

Missing Authorization (CWE-862) in Checkmate Routes

CVE-2026-85390

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized administrative actions and incident-data tampering

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Checkmate through version 3.11.0 fails to apply its role-authorization middleware to several maintenance, notification, and check-deletion routes. A user with a read-only session may therefore perform administrative actions, including silencing alerts, changing notification channels, and deleting monitor history when those routes are accessible.

Affected context

The vulnerability occurs in Checkmate deployments where the affected

maintenance-window, notification, or check-deletion routes are reachable by

authenticated users. The routes may omit the isAllowed role guard, so

authorization depends on incomplete or absent server-side enforcement rather

than the user's intended read-only role.

Exploit preconditions

  • Attack surface: Authenticated Checkmate HTTP routes for maintenance

windows, notification channels, or monitor check deletion

  • Required access: A valid user-role session, including a read-only

account

  • Trigger point: A request to an affected administrative route
  • Why exploitation is possible: The expected isAllowed authorization

middleware is not applied consistently, allowing route handlers to process

actions without verifying the required role

Why this happens

The underlying bug is an authorization-enforcement omission. Administrative

route handlers are exposed without consistently invoking the middleware that

verifies whether the session's role is permitted to perform the requested

operation. This behavior maps to CWE-862: Missing Authorization, in which

an application fails to enforce an access-control decision for a protected

resource or action.

Potential impact

  • Attackers may create arbitrary maintenance windows and suppress monitoring

alerts.

  • Attackers may modify notification channels and disrupt incident delivery.
  • Attackers may delete monitor check history and remove evidence of incidents.
  • Organizations could experience delayed detection, impaired response, or

loss of operational records.

General mitigation guidance

Mitigation generally centers on enforcing authorization at every protected

server-side route and action, rather than relying on client-side visibility

or route grouping.

Common defensive patterns include:

  • Applying centralized role and permission checks consistently to all

administrative endpoints.

  • Denying access by default when a required permission is absent or

authorization context is unclear.

  • Separating read and write permissions for monitoring, notification, and

historical-data operations.

  • Requiring stronger privilege for destructive actions and preserving

tamper-resistant audit records.

  • Reducing trust in client-provided role indicators and deriving privileges

from validated server-side session or identity data.

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static analysis and route audits that identify administrative handlers

lacking centralized authorization middleware.

  • Code review checks confirming that every write or destructive operation

performs a server-side permission decision.

  • Integration tests that exercise protected routes with read-only and

unauthenticated sessions and verify consistent denial responses.

  • Policy enforcement requiring explicit authorization annotations or guards

for administrative endpoints.

  • Audit-log monitoring for unexpected maintenance-window, notification, or

history-deletion actions by low-privilege accounts.

Automated security review tools may help identify route-level authorization

gaps, but should be supplemented with permission-matrix testing.

Sources

SourceLink
github.comgithub.com/bluewave-labs/Checkmate
github.comgithub.com/bluewave-labs/Checkmate/blob/v3.11.0/server/src/api/routes/checkRoutes.ts
github.comgithub.com/bluewave-labs/Checkmate/blob/v3.11.0/server/src/api/routes/maintenanceWindowRoutes.ts
github.comgithub.com/bluewave-labs/Checkmate/blob/v3.11.0/server/src/api/routes/notificationRoutes.ts
github.comgithub.com/bluewave-labs/Checkmate/issues/3916
vulncheck.comvulncheck.com/advisories/checkmate-through-3.11.0-missing-authorization-on-maintenance-window-notification-and-check-deletion-routes

Frequently asked

questions

It may be exploitable through the Checkmate web interface or API when the

affected routes are network-accessible and the attacker has a valid session.

No. The described issue specifically allows users with read-only sessions to

reach actions intended for more privileged roles.

Enforce the required permission on the server side for every affected route

and action, using centralized, deny-by-default authorization checks.

Maintain an explicit permission matrix, test each protected endpoint with

multiple roles, review destructive operations separately, and monitor audit

logs for anomalous low-privilege activity.

Find out what's already
exploitable in your codebase.