SecurityNovember 13, 20267 min read

BeyondTrust Remote Support CVE-2026-102764

An authentication bypass in BeyondTrust Remote Support was exploited as a zero-day for weeks before the patch. Remote support appliances hold the keys to everything they touch, so a tester should treat them as tier zero assets.

What happened

On October 15, BeyondTrust told customers to patch CVE-2026-102764, an authentication bypass in Remote Support (RS) that lets an unauthenticated remote attacker perform file operations on unpatched appliances. It affects RS 26.2.3 and earlier. BeyondTrust patched its Remote Support and Privileged Remote Access SaaS customers on October 8. Self-hosted installs need a manual update unless automatic updates are on. BeyondTrust also shipped the fix for Privileged Remote Access because it shares the affected code. (BleepingComputer)

The flaw had been exploited as a zero-day since late August. BeyondTrust attributed the activity to a suspected China-nexus espionage actor that Mandiant and Google Threat Intelligence Group track as Armory Castle (formerly UNC5221) and CrowdStrike tracks as Warp Panda. CISA added the CVE to the Known Exploited Vulnerabilities catalog on October 16. (CISA)

Why it worked

Per Mandiant, the actor used the bypass for initial access, escalated to root on the appliance by enabling SUID permissions, deployed a web shell and a tunneler, wiped logs, and then used compromised Administrator credentials to open remote sessions on downstream systems.

That last step is the whole point of attacking a remote support box. Mandiant put it plainly: root on the appliance "gave them access to every credential the appliance stored or brokered and the ability to modify files that survive reboot and configuration reset." A remote access tool is a trust broker for the help desk. Whoever owns it inherits that trust.

Exposure made it practical. Shadowserver tracks more than 1,400 BeyondTrust Remote Support instances reachable from the internet. Mandiant also warned that this actor has a history of moving from selective zero-day use to widespread opportunistic exploitation once a bug becomes public, so the window after disclosure matters as much as the weeks before it.

What a tester should check

For a tester, the useful work starts at disclosure, and it is the same work for every remote access product in scope:

  • Exposure inventory. Find every RS and PRA instance, including the forgotten ones on a secondary domain or a lab subnet. Confirm which are reachable from the internet and which only from inside.
  • Patch verification. Record the running version against the fixed release, and confirm self-hosted appliances actually received the update. SaaS customers were patched by the vendor; on-prem customers had to act.
  • Compromise assumptions. Mandiant advises treating any appliance that was internet reachable on a vulnerable version during the exploitation window as potentially compromised until reviewed. A report should say that clearly and point the client to the vendor and Mandiant guidance.
  • Credential blast radius. Map which accounts and downstream systems the appliance brokers sessions to. Shared Administrator credentials used through the tool are the chain that turned one appliance into a network intrusion.
  • Management plane hardening. Check whether the admin interface is restricted to trusted networks and whether logs ship off the box, since this actor wiped local logs.

How Zypheron helps a human tester move faster

Zypheron is a semi-automated, human-led pentest workspace. When a KEV entry like this lands mid engagement, the operator can run recon and service fingerprinting across scope from one place, review the results, and tag every remote access appliance as a high value asset. AI helps triage the output and drafts the finding. Nothing fires on its own: each tool command waits for the operator to approve it.

The part that saves real time is the chain. Zypheron keeps hosts, credentials, and attack paths in one graph with AD and cloud collectors, so a tester can show the client exactly which systems a compromised support appliance could reach, with evidence attached. The finding moves into the client report when the operator signs off, already linked to the advisory and the version evidence.

The honest pitch is narrower and more useful: Zypheron helps a tester answer the questions a CISO asks the morning after a disclosure: are we exposed, are we patched, and what could this box reach.

Try it on your next engagement

Start a 14-day free trial of the Zypheron IDE. No card required, and the Operator plan is $99.99 when you keep going.

Sources

ShareLinkedInX
Email List

Get AD security drops in your inbox

Release notes, identity attack-path research, and early access. Low volume, real signal only. Unsubscribe anytime.

ZYPHERON

ZYPHERON Desktop is a cybersecurity IDE for offensive and defensive workflows. The open source CLI remains available for terminal-first users.

AUTHORIZED USE ONLY

Solutions

Infrastructure

Network

© 2025 ZYPHERON SYSTEMS//DESKTOP + CLI