Cybersecurity

BeyondTrust Patches Zero-Day Vulnerability in Remote Support Exploited Since August

BeyondTrust released an update for a critical authentication-bypass vulnerability in Remote Support after it was actively exploited since late August by an espionage actor suspected of ties to China. The vulnerability allows unauthenticated attackers to perform file operations and escalate their privileges to root on affected devices.

2026-10-16
3 min read
17 views
certi.news Editorial Team
BeyondTrust Patches Zero-Day Vulnerability in Remote Support Exploited Since August

BeyondTrust warned its customers of a critical security vulnerability in its Remote Support (RS) solution after confirming that it had been exploited in zero-day attacks since late August. The vulnerability, tracked as CVE-2026-102764, affects versions 26.2.3 and earlier and allows a remote, unauthenticated attacker to bypass authentication and perform file operations on unpatched devices.

The company issued the patch on October 8 for Remote Support and Privileged Remote Access customers using SaaS versions. In self-hosted environments, administrators must install the update manually if automatic updates are not enabled. Although BeyondTrust’s internal testing did not identify a way to exploit the vulnerability in Privileged Remote Access, the product shares the affected code with Remote Support. The company therefore also issued a patch for it and recommends that its self-hosted customers apply it immediately.

Exploitation for Access and Privilege Escalation

Mandiant and the Google Threat Intelligence Group observed the attacks and attributed them to an actor called Armory Castle, formerly known as UNC5221, while CrowdStrike calls it Warp Panda. The group is suspected of having ties to China.

Advertisement

The attackers exploited the vulnerability to gain initial access to devices, then escalated their privileges to root by enabling Set User ID (SUID) permissions. They subsequently deployed the Sawfly web shell and the Bareclaw tool for lateral movement, erased logs to reduce the chances of detection, and used compromised Administrator credentials to open remote sessions on other systems inside the network.

According to Mandiant, root-level access to the host gave the attackers the ability to access credentials stored or relayed by the device, modify files that persist after reboot, and reset configurations. The researchers therefore recommended treating any internet-exposed device running an affected version during the exploitation period as compromised until it has been reviewed.

Why Does This Matter?

The vulnerability combines three factors that increase its severity: exploitation in the wild before a patch was available, Remote Support’s position at the network perimeter, and the possibility of accessing credentials used by support teams and connected systems. Shadowserver is also tracking more than 1,400 BeyondTrust Remote Support instances exposed on the internet, without clarifying how many devices have been secured or represent test honeypots.

This does not mean that all exposed devices have been compromised, but it makes checking logs, reviewing accounts and files, and installing the patch an immediate priority, especially for organizations using self-hosted versions.

Threat Context and Open Questions

Armory Castle has a history of targeting network-edge devices, including Citrix NetScaler and Ivanti Connect Secure, to gain access to enterprise networks and deploy custom malware. Mandiant warned that exploitation could expand after the disclosure of CVE-2026-102764, as occurred in previous campaigns that began with selective exploitation of vulnerabilities and then turned into widespread activity after information about them emerged.

The source does not specify how many organizations were compromised in the current campaign or whether the credentials of specific customers were stolen. Installing the patch therefore remains essential, but it does not replace investigating devices that were exposed during the exploitation window.

News source
BleepingComputer
Open original source ↗
c
Author

certi.news Editorial Team

What you need to know

BeyondTrust has released a patch for a critical zero-day vulnerability in Remote Support, tracked as CVE-2026-102764, after it was actively exploited since late August. Affected systems should be updated, and devices that were exposed should be investigated because applying the patch alone does not prove that a prior compromise did not occur.

  • The vulnerability affects Remote Support version 26.2.3 and earlier, allowing authentication bypass and file operations, followed by privilege escalation to root.
  • BeyondTrust released the patch on October 8 for Remote Support and Privileged Remote Access customers using SaaS versions, while users of self-hosted environments must install the update manually when required.
  • Mandiant and Google Threat Intelligence Group observed the attacks and attributed them to Armory Castle, formerly known as UNC5221, which CrowdStrike calls Warp Panda.
  • The attackers used SUID permissions to escalate privileges, then deployed Sawfly and Bareclaw, wiped logs, and used compromised Administrator credentials to move through the network.
  • Shadowserver estimated that more than 1,400 BeyondTrust Remote Support instances were exposed to the internet, without determining how many devices were compromised or secured.
  • Mandiant recommends reviewing logs, accounts, and files, and examining any internet-exposed device running an affected version during the exploitation period.

FAQ

Which products are affected by the vulnerability?

The vulnerability affects Remote Support version 26.2.3 and earlier. BeyondTrust also released a patch for Privileged Remote Access because the two products share the affected code, although internal testing did not identify a way to exploit it in that product.

What should organizations do?

They should install the patch immediately, especially in self-hosted environments, review logs, accounts, and files, and investigate devices that were exposed during the exploitation period.

Does exposure mean that a device was compromised?

No. The article explains that not all exposed devices were necessarily compromised, but considers them in need of review, particularly if they were running an affected version during the exploitation period.

In the same category

You may also like

View all news