BeyondTrust Vulnerability Targeted by Hackers Within 24 Hours of PoC Release
Source SecurityWeek
Exploited in the wild · KEV due 16 Feb 2026 · public exploit available (Metasploit) : apply the vendor's fix or mitigations to Remote Support(RS) & Privileged Remote Access(PRA) now.
Data as of 16 Feb 2026, 13:39 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else.
Exploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 6 Feb 2026
Detectable: evidence found.
nuclei template: BeyondTrust Remote Support - Unauthenticated WebSocket RCE
Weaponised: evidence found.
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 7 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by BT
, 6 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 11 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed · ransomware use known
, 7 days after disclosure
KEV remediation due
US federal deadline
, 10 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BeyondTrustRemote Support(RS) & Privileged Remote Access(PRA) | Affected
| Fixed in– |
AI-suggested
1. Immediately implement network-level access controls to restrict exposure of BeyondTrust Remote Support services to trusted internal networks only, blocking all unnecessary inbound traffic from the internet. 2. Monitor network traffic and system logs for indicators of compromise or unusual activity related to BeyondTrust Remote Support, including unexpected connections or command execution attempts. 3. Apply any available vendor patches or security updates as soon as they are released by BeyondTrust. 4. If patches are not yet available, consider temporarily disabling or uninstalling BeyondTrust Remote Support or replacing it with alternative secure remote support solutions. 5. Employ application-layer firewalls or intrusion prevention systems (IPS) with signatures targeting exploitation attempts of CVE-2026-1731. 6. Conduct thorough asset inventory to identify all instances of BeyondTrust Remote Support within the organization. 7. Educate IT and security teams about the vulnerability and the importance of rapid response. 8. Implement strict segmentation between remote support tools and critical infrastructure to limit lateral movement in case of compromise. 9. Regularly back up critical data and verify restoration procedures to minimize impact from potential ransomware or destructive attacks following exploitation.
Description
Exploitation attempts target CVE-2026-1731, a critical unauthenticated remote code execution flaw in BeyondTrust Remote Support. The post BeyondTrust Vulnerability Targeted by Hackers Within 24 Hours of PoC Release appeared first on SecurityWeek .