How to fix CVE-2026-102764: BeyondTrust Remote Support (exploited in the wild)

The vulnerability exists within internal components of BeyondTrust’s Remote Support product. The components did not adequately validate the origin of the messages it received. Under the right conditions, this could allow an attacker to perform file operations on the appliance.

• Severity: CRITICAL (CVSS 4.0 9.3, vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N).
• Weakness: CWE-290.
• NVD published 2026-10-15, status Analyzed.

Anyone running BeyondTrust Remote Support in the version ranges below. Internet-facing instances are the priority.

• beyondtrust remote support: up to and including 26.2.3.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-10-16; federal remediation due date 2026-10-19.
• Public proof-of-concept code: 3 GitHub repositories from 3 accounts, the first on 2026-10-16.

• EPSS (probability of exploitation activity in the next 30 days): 1.18%, higher than 67% of all scored CVEs (as of 2026-10-24).
• CVERadar threat level: 62/100 (see methodology).
• Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1078 Valid Accounts (inferred).

1. Find every instance. List where BeyondTrust Remote Support runs, including test, DR and forgotten internet-facing systems, and record the installed version.
2. Apply the latest vendor update. NVD does not list a fixed version, so follow the vendor advisory for the patched release.
3. If you can't patch today, follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build. Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to Remote Support (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-10-15.
• T1078 Valid Accounts: Check for logins from new sources or accounts you did not create.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-102764 nvd.nist.gov/vuln/detail/CVE-2026-102764
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-102764
• Vendor link from CISA KEV www.beyondtrust.com/trust-center/security-advisories/bt26-05
• Vendor Advisory www.beyondtrust.com/blog/entry/bt26-05
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (2026-10-24) api.first.org/data/v1/epss?cve=CVE-2026-102764