← All news
Vulnerability ManagementIncident ResponseSOC

BeyondTrust Remote Support Zero-Day CVE-2026-102764 Was Exploited for About Seven Weeks, and the Attackers Wiped Logs on the Way Out

Obiguard Research Team·October 17, 2026·5 min read

BeyondTrust has patched an authentication bypass in its Remote Support product, CVE-2026-102764, that attackers had been exploiting as a zero-day since late August. According to BleepingComputer, the flaw lets an unprivileged remote attacker perform file operations on unpatched appliances. Mandiant spotted the initial attacks and attributes them to a suspected China-nexus espionage actor it tracks as Armory Castle, formerly UNC5221. CrowdStrike tracks the same group as Warp Panda.

BeyondTrust published its customer advisory on 16 October. SaaS customers were patched on 8 October. Self-hosted customers have to patch manually unless automatic updates are on.

What is affected

  • CVE-2026-102764 is an authentication bypass (CWE-290) in BeyondTrust Remote Support (RS) 26.2.3 and earlier.
  • Privileged Remote Access (PRA) shares the vulnerable code. BeyondTrust says its internal testing found no way to exploit it in PRA, but it still recommends self-hosted PRA customers apply the patch immediately.
  • BleepingComputer's report does not give a CVSS score or say whether CISA has added the flaw to its Known Exploited Vulnerabilities catalog, so check the vendor advisory and the KEV catalog directly rather than waiting for either.

Shadowserver tracks more than 1,400 BeyondTrust remote support instances exposed online. It does not say how many are already patched or how many are honeypots.

How the attacks worked

Mandiant and Google Threat Intelligence Group described the chain they observed:

  1. Initial access through a web shell.
  2. Privilege escalation from the web service account to root by enabling SUID permissions.
  3. Deployment of the Sawfly web shell and Bareclaw tunneler.
  4. Log wiping to avoid detection.
  5. Lateral movement using compromised Administrator credentials to open remote sessions on downstream systems.

Steps 4 and 5 are the ones that change the response. A remote support appliance exists to open sessions into other machines, so a remote session launched from it looks like normal use. And if the attacker cleared the appliance's own logs, the box itself cannot tell you what happened.

Why this one is different from a typical edge bug

We covered the Citrix NetScaler zero-days last week, where the lesson was that patching does not remove a web shell already on the device. That applies here too. But a remote support tool adds a second problem: it holds or brokers credentials for the systems it connects to, and its whole purpose is reaching those systems.

That is why Mandiant's advice goes past the appliance. Treat any internet-reachable instance that ran a vulnerable version during the exploitation window as potentially compromised until reviewed, and include any credentials the appliance stored or brokered in that review. Mandiant also warns that wider opportunistic exploitation may follow, as it has after earlier Armory Castle campaigns.

The group's history supports that. It has previously exploited Citrix NetScaler (CVE-2023-4966) and Ivanti Connect Secure (CVE-2023-46805, CVE-2024-21887, CVE-2025-0282), and Volexity reported in January 2024 that UNC5221 had backdoored more than 2,100 Ivanti appliances. BeyondTrust products have been targeted before as well, including CVE-2024-12356 and CVE-2024-12686, which Silk Typhoon reportedly used to compromise 17 Remote Support SaaS instances, one of them used by the U.S. Treasury Department.

What to check this week

  • Patch self-hosted RS and PRA now. Confirm the version rather than assuming automatic updates ran.
  • Preserve before you rebuild. Take a snapshot or support bundle of any appliance that was exposed during late August to early October before changing it.
  • Do not rely on the appliance's local logs. Pull what you forwarded elsewhere: syslog, SIEM, firewall and proxy logs for traffic to and from the appliance.
  • Review downstream sessions. List remote sessions launched from the appliance since late August, especially those using Administrator accounts, outside normal support hours, or into systems that rarely get support sessions.
  • Rotate brokered credentials. Anything stored in or passed through the appliance during the window should be rotated, starting with privileged and service accounts.
  • Hunt on the box for unexpected SUID binaries and unfamiliar web-accessible files, and on the network for tunnelling traffic from the appliance.

Where Obiguard fits: logs the attacker cannot reach

Wiping logs only works if the logs live only on the machine being wiped. Obiguard SOC streams logs and host metrics off each system through OpenTelemetry as they are written, so a copy sits outside the appliance before an intruder gets root. Live Logs makes those events searchable by source and level, alerts fire on rule matches and log volume, and each alert keeps an evidence timeline linked to the raw events that triggered it. For a breach like this one, that is the difference between reconstructing which downstream sessions were opened and having nothing to look at.

SOC's CVE Radar cross-checks dependency findings in connected repos against CISA KEV and FIRST EPSS. That covers code you build, not a vendor appliance, so it will not flag this CVE on your BeyondTrust box. The useful step is getting the appliance and the systems it connects to forwarding logs before the next one.

The question to take away

If an attacker cleared the logs on your remote support appliance tonight, where else would a record exist of the sessions it opened, and would anyone notice the logs had stopped?

See how Obiguard SOC works or talk to us about getting logs off the systems that attackers most want to clean up.

How Obiguard helps

Turn this into enforced policy, not just awareness.

Obiguard sits in front of every AI request your organization makes — screening prompts and outputs against the guardrails, compliance frameworks, and audit trails that stories like this one make necessary.

See how it works →