Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

MeshCentral cross-site websocket hijacking (CSWSH) vulnerability

CVE-2024-26135GHSA-cp68-qrhr-g9h8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (meshcentral 1.1.21), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.3 · CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
  • CVE-2024-26135: 0.46% estimated exploitation activity in the next 30 days; percentile 39.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

We have identified a cross-site websocket hijacking (CSWSH) vulnerability within the control.ashx endpoint of MeshCentral. This component is the primary mechanism used within MeshCentral to perform administrative actions on the server. To demonstrate the impact of the vulnerability we developed a proof-of-concept which leveraged the cross-site websocket hijacking vulnerability to read the server configuration file to leak the sessionKey variable, generating login tokens, and generating an authentication cookie. The vulnerability is exploitable when an attacker is able to convince a victim end-user to click on a malicious link to a page hosting an attacker-controlled site. The attacker can then originate a cross-site websocket connection using client-side JavaScript code to connect to “control.ashx” as the victim user within MeshCentral. There are some caveats to exploiting this issue however as MeshCentral configures SameSite=Lax security setting on cookies which introduces some…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-cp68-qrhr-g9h8

  2. Revision 1 · created ·

    Published from osv record GHSA-cp68-qrhr-g9h8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-26135

Advisory: MeshCentral cross-site websocket hijacking (CSWSH) vulnerability
IDs: CVE-2024-26135, GHSA-cp68-qrhr-g9h8
Record: https://patchnext.com/advisories/cve-2024-26135 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: meshcentral 1.1.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm meshcentral: affected < 1.1.21; fixed in 1.1.21

## Suggested inspection (read-only)
- `npm ls meshcentral --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on meshcentral.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cp68-qrhr-g9h8 (OSV record GHSA-cp68-qrhr-g9h8 lists affected ranges: npm meshcentral >=0 <1.1.21 (fixed))
- Verified: https://github.com/advisories/GHSA-cp68-qrhr-g9h8 (GitHub-reviewed advisory GHSA-cp68-qrhr-g9h8 lists affected ranges: npm meshcentral >=0 <1.1.21)

Commands are suggestions: review each one before running it.

Loading voting…