BeyondTrust Remote Support attacks, 2026: what to do now

Attackers exploited two critical BeyondTrust Remote Support vulnerabilities in 2026: CVE-2026-1731 in February and CVE-2026-102764, disclosed in October. If you run your own appliance, confirm both fixes are installed and check for signs of earlier access. Patching closes the hole. It does not remove an intruder who got in first.

Jump to the steps
By CalMax Systems Security Research, founder · Updated November 15, 2026 · Based on BeyondTrust, Mandiant, CISA and the research sources below

Run BeyondTrust Remote Support yourself?

Do the vendor steps on this page first. Then you can secure the appliance itself with our Secure BeyondTrust playbook, the step-by-step method we built on our own ScreenConnect server and applied to BeyondTrust. It adds to the vendor steps. It does not replace them.

See the self-hosted security playbook

Research cutoff: November 15, 2026. The February and October incidents have different advisories and response thresholds. Check both.

What happened with BeyondTrust Remote Support in 2026?

Attackers exploited two separate critical flaws. CVE-2026-1731 was patched in February, and reporting tied it to ransomware activity. CVE-2026-102764 was disclosed in October after a suspected espionage group used it from late August, left persistence on appliances and ran downstream sessions with stolen credentials. Each has its own advisory, so check both.

  • February: Microsoft lists CVE-2026-1731 among the vulnerabilities Storm-1175 exploited in Medusa ransomware operations. Other groups may be behind other February intrusions.
  • Late August onward: Mandiant attributes the October-disclosed exploitation to ARMORY CASTLE, formerly UNC5221, a suspected PRC-nexus espionage actor. BeyondTrust dates exploitation against one hosted and one self-hosted instance to August 29.
  • October findings: Mandiant observed SAWFLY webshells, root escalation, attempted Vault credential extraction and log deletion. Compromised Administrator credentials and raised Jump Item/Team permissions enabled downstream sessions and document theft.

What is CVE-2026-102764, or BT26-05?

CVE-2026-102764 is a critical origin-validation flaw in an internal Remote Support messaging component that allows remote file operations. BeyondTrust rates it CVSS v4.0 9.3. Unremediated RS versions 26.2.3 and earlier are affected. Install BT26-05-RS on supported older releases or upgrade to RS 26.3.1 or later.

BT26-05 was issued October 15 and updated November 4. Its patch covers RS 24.3.1 through 26.2.3; earlier installations must upgrade first. CISA added it to the Known Exploited Vulnerabilities catalog on October 16, with an October 19 due date, and flags it for forensic triage.

What is CVE-2026-1731, and which versions fix it?

CVE-2026-1731 is a critical flaw in Remote Support and Privileged Remote Access that lets an attacker run operating-system commands as the site user without logging in. BeyondTrust rates it CVSS v4.0 9.9. For RS, install BT26-02-RS on versions 21.3 through 25.3.1, or upgrade to RS 25.3.2 or later.

BT26-02 lists affected PRA versions as 24.3.4 and earlier. Its fixed-version matrix lists BT26-02-PRA for 22.1 through 24.x, or PRA 25.1 and greater. CISA added CVE-2026-1731 on February 13; its ransomware campaign field is marked Known.

What should self-hosted customers do now?

Check your version and installed patches, then install the updates you are missing from the appliance interface. Look closely at any period when the appliance was online and unpatched. Open a Severity 1 case if a vendor threshold below applies to you. If you suspect compromise, preserve evidence and rotate the credentials the appliance holds.

  1. Check the application: open /login > Status > Information. Record Product Version, Product Build and Installed patches. The Base software version under /appliance > Status > Basics is a separate appliance-layer value.
  2. Install updates: go to /appliance > Updates > Check for updates, then select Install This Update. Follow prerequisite Base and product packages in sequence. Verify installation even if automatic updates are enabled.
  3. Use manual installation when needed: generate an Appliance Download Key, obtain the packages from another system, then use Manual Installation > Update Software. Follow the vendor procedure linked below.
  4. Escalate historical February exposure: if your internet-facing instance remained unpatched as of February 9, patch and open a Severity 1 ticket citing BT26-02.
  5. Escalate suspected October compromise: preserve evidence before rebuilding and open a Sev 1 request citing BT26-05. Rotate credentials stored in or injected through the appliance.
  6. Plan recovery with your responders: Mandiant recommends clean redeployment for confirmed or unknown compromise because host persistence can survive a reset. Customers cannot audit the host filesystem themselves.
Patching is not cleanup. Follow the compromise checks and scope downstream access before closing the incident.

Is BeyondTrust Remote Support safe to use?

It depends on your own appliance. Fixes exist for both vulnerabilities, so a fully patched appliance with a clean investigation is in a much better place. Patching won’t tell you whether someone got in earlier and left persistence or took credentials. If you find suspicious activity, bring in BeyondTrust support and your responders before you rely on it again.

What changes for SaaS versus self-hosted customers?

BeyondTrust patched its SaaS service for both flaws. If you host the appliance yourself, you install the updates or confirm automatic updates actually ran. A virtual appliance in your own AWS or Azure account counts as self-hosted. Either way, the date the fix landed matters, because exploitation started before each patch was released.

Check the timeline for your deployment

February SaaS patching completed February 2. For October, BeyondTrust’s timeline gives October 8 for patch release and SaaS patching; Mandiant gives October 9 for SaaS tenants. Check your own update history to see when your appliance got each fix.

Was my BeyondTrust appliance compromised? Quick checks

Start with privileged sessions you can’t explain and changes nobody on your team made. BeyondTrust and Mandiant both say to review the appliance configuration and session records, including the endpoints those sessions reached. Get BeyondTrust’s hunting package from its trust portal. Finding nothing in a first pass doesn’t mean the appliance is clean.

  • Sessions and transfers: review /login > Reports > Support, report type Session. Examine unexpected privileged access and file transfers involving affected endpoints.
  • Configuration changes: compare users, roles, API accounts, security providers, Jump Items/Jumpoints, policies and logging destinations against your baseline. Check Team permissions too.
  • Missing evidence: investigate forwarding gaps that align with sessions. BeyondTrust also calls out unfamiliar scripts and web-service shells.
  • October artifacts: Mandiant publishes hashes and YARA rules, with artifacts including mangoapi.php, ingredi_ws and /usr/bin/dbus-authd. Coordinate host-level checks with BeyondTrust and responders.
  • February endpoint activity: Arctic Wolf reported suspected exploitation involving renamed SimpleHelp executables under C:\ProgramData, including remote access.exe. It also saw new domain accounts added to Domain Admins and Enterprise Admins.

How can I secure my self-hosted appliance after the vendor steps?

Patch, investigate, then secure the appliance itself. Our Secure BeyondTrust playbook is a $79 one-time PDF for self-hosted RS and PRA with step-by-step instructions, testing and rollback. You get free email support at support@threatlistpro.com and updates through the same download link. There are no refunds, so check the product page first.

We built this method on our own ScreenConnect server after we found rogue sessions on it. This edition applies the same method to BeyondTrust appliances. We have not tested it on BeyondTrust.

Secure your appliance with the step-by-step PDF

BeyondTrust Remote Support attack FAQs

Which versions fix CVE-2026-102764?

For BeyondTrust Remote Support, install BT26-05-RS on versions 24.3.1 through 26.2.3, or upgrade to 26.3.1 or later. Releases older than 24.3.1 must upgrade before applying the patch. Check Product Version and Installed patches under /login > Status > Information; the Base software version is a separate appliance-layer value.

Does CVE-2026-1731 still need attention?

Yes, if you have not verified its remediation or investigated past exposure. BeyondTrust lists BT26-02-RS for Remote Support 21.3 through 25.3.1, or version 25.3.2 and later. Customers whose internet-facing appliances remained unpatched as of February 9 should patch and open a Severity 1 ticket citing BT26-02.

Is BeyondTrust Remote Support safe after patching?

Patching addresses the documented vulnerabilities, but it cannot tell you whether an attacker established access earlier. BeyondTrust and Mandiant recommend investigating suspicious sessions and configuration changes. If compromise is confirmed or unknown, Mandiant recommends clean redeployment because host persistence can survive a reset. Preserve evidence before rebuilding.

Are SaaS customers affected by the 2026 vulnerabilities?

BeyondTrust patched its SaaS customers for both vulnerabilities. That does not mean SaaS was never attacked: BeyondTrust reports August 29 exploitation against one hosted and one self-hosted Remote Support instance. Self-hosted customers must install or verify their own updates, including appliances deployed in their own cloud accounts.

How can I check whether my appliance was compromised?

Review unexplained privileged sessions, unauthorized account or permission changes, and gaps in forwarded records during sessions. Compare configuration with your baseline and review session and file-transfer reports for affected endpoints. BeyondTrust provides a hunting package through its trust portal. A clean initial check does not rule out compromise.

When should I open a Severity 1 support ticket?

For suspected compromise associated with the October incident, BeyondTrust directs customers to open a Sev 1 request citing BT26-05 and preserve evidence before rebuilding. Separately, customers with internet-exposed appliances unpatched as of February 9 should patch and open a Severity 1 ticket citing BT26-02, following the February advisory.

Does BT26-05 also affect Privileged Remote Access?

BeyondTrust says Privileged Remote Access shares affected code, but its testing found no exploitation path. It released a precautionary PRA patch and recommends immediate installation. The version table in BT26-05 is for Remote Support, so don't use it for PRA. Ask BeyondTrust support which patch fits your PRA version.

Sources

Research cutoff: November 15, 2026.

Related resources

ScreenConnect incident guidance and self-hosted security.

SimpleHelp attacks, 2026: what to do now N-central attacks, 2026: what to do now ScreenConnect attacks, November 2026: what to do now Secure ScreenConnect playbook