CVE-2026-1731 BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA) OS Command Injection Vulnerability
BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA)contain an OS command injection vulnerability. Successful exploitation could allow an unauthenticated remote attacker to execute operating system commands in the context of the site user. Successful exploitation requires no authentication or user interaction and may lead to system compromise, including unauthorized access, data exfiltration, and service disruption.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 13 Feb 2026.
- CISA lists it as known to be used in ransomware campaigns.
- Rated Critical severity (CVSS 9.9, scored by Vendor).
- This product type is often exposed to the internet, which is where attackers scan for it first.
- Named in Cybergen threat actor reporting: Medusa.
- It has been in the catalogue for 266 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
BeyondTrust Remote Support (RS) and certain older versions of Privileged Remote Access (PRA) contain a critical pre-authentication remote code execution vulnerability. By sending specially crafted requests, an unauthenticated remote attacker may be able to execute operating system commands in the context of the site user.
Affected Versions
| Product | Versions |
|---|---|
| BeyondTrust Remote Support(RS) & Privileged Remote Access(PRA) | RS 25.3.1 and earlier PRA 24.3.4 and earlier |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA). Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
Vendor Advisories
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2026-1731 and every other exploited flaw on the list.