CVE-2026-102764: BeyondTrust Remote Support Vulnerability Exploited in the Wild

CVE-2026-102764: BeyondTrust Remote Support Vulnerability Exploited in the Wild


Remote support tools help IT teams access and troubleshoot systems from anywhere. But when one of these tools is compromised, the impact can extend far beyond the platform itself, particularly when it provides access to privileged credentials and internal systems.

That is the concern with CVE-2026-102764, a critical vulnerability affecting BeyondTrust Remote Support. The vulnerability was exploited in the wild before public disclosure, making it an urgent concern for organizations that rely on the product for remote access and technical support.

What Is the Vulnerability?

CVE-2026-102764 stems from improper origin validation in an internal messaging component. The flaw could allow a remote attacker to perform file operations on a vulnerable appliance without authentication or user interaction.

The vulnerability has a CVSS v3.1 score of 9.1 and a CVSS v4.0 score of 9.3, placing it in the critical severity category.

BeyondTrust Remote Support is used by IT support teams to connect to endpoints and troubleshoot technical issues. A compromise of the appliance can therefore create risks beyond the appliance itself, especially if attackers gain access to privileged credentials or use existing remote support relationships to reach other systems.

How Was It Exploited?

Investigations linked exploitation activity in late August 2026 to a suspected China-linked espionage group tracked as ARMORY CASTLE.

Reported attacker activity included establishing web-shell access, escalating privileges to root, attempting to extract stored credentials and maintaining persistence. Investigators also observed attempts to delete logs, potentially making the activity harder to detect.

This is particularly concerning for enterprises because remote support platforms can sit close to privileged accounts and sensitive endpoints. If attackers compromise the platform, they may be able to use that position to pursue further access within the organization’s environment.

Affected Versions

  • BeyondTrust Remote Support: Versions up to and including 26.2.3 are affected.
  • Older deployments: Versions earlier than 24.3.1 must first be upgraded to a supported version before applying the security patch.
  • Privileged Remote Access (PRA): BeyondTrust also released a precautionary patch because the product shares the affected code. Its testing did not identify an exploitable path in PRA.

Organizations should verify their installed versions and follow BeyondTrust’s official security advisory for the appropriate upgrade and patch instructions.

What Should Organizations Do?

The immediate priority is to identify all self-hosted BeyondTrust Remote Support appliances and apply the vendor’s BT26-05-RS security update.

However, patching alone is not enough. Since exploitation occurred before public disclosure, security teams should investigate whether their appliances were exposed during the exploitation period.

Review appliance logs and SIEM alerts for unexpected web shells, suspicious administrative activity, privilege changes and unusual access to stored credentials. Investigate missing or deleted logs as well, since attackers may attempt to remove evidence of their activity.

If compromise is suspected, isolate the affected appliance and investigate related systems. Assess whether credentials accessible through the platform need to be rotated, and check for signs of unauthorized access to downstream systems.

BeyondTrust reported that its Remote Support SaaS customers were patched automatically by October 9, 2026. SaaS customers should verify their service status with the vendor and assess any relevant security telemetry rather than assuming that automatic patching rules out prior compromise.

Final Thoughts

CVE-2026-102764 is a reminder that remote support infrastructure deserves the same level of attention as other privileged systems. These platforms often sit at the intersection of IT operations, endpoint access and administrative credentials, making them attractive targets for attackers.

The priority is not just to close the vulnerability, but also to establish whether an attacker gained access before the fix was applied. Patching addresses the known flaw; investigation determines whether the organization may already have been compromised.

Official References

Comments

No comments yet. Why don’t you start the discussion?

    Leave a Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.