CVE Intelligence
Skip to main content
CISA KEVRansomwarecriticalRemote Code Execpublic exploit

CVE-2026-1731

CVE-2026-1731 — Remote code execution vulnerability in BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA)

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.

Published Updated Sources: NVD, BeyondTrust (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Feb 13, 2026

EPSS

90%

ahead of 99.8% of scored CVEs

Affects

BeyondTrust

2 products listed

CVSS base

9.8

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Remote Support(RS) & Privileged Remote Access(PRA) to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Feb 16, 2026 — passed 220 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Treat as emergency remediation because CISA KEV status is present.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
BeyondTrustRemote Support(RS) & Privileged Remote Access(PRA)0Vulnerable
BeyondTrustRemote Support(RS) & Privileged Remote Access(PRA)0Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
9.8CVSS 3.1critical3.95.9NVD, GHSA
9.9CVSS 4.0critical——BeyondTrust (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

  • Execute Unauthorized Code or Commands
  • DoS: Crash, Exit, or Restart
  • Read Files or Directories
  • Modify Files or Directories

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

Weakness & attack patterns

  • CWE-78OS Command Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-15 · Command DelimitersCAPEC-88 · OS Command InjectionCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-108 · Command Line Execution through SQL InjectionCAPEC-6 · Argument Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

Listed

Feb 13, 2026

Federal deadline

Feb 16, 2026

passed 220 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

70

1 of the 5 sampled are weaponized

Exploit entries

2

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Remote Support(RS) & Privileged Remote Access(PRA).
  • Monitor for scanner or exploit-pattern traffic after 72 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

UNC215BRONZE SPRINGTA428Iron GroupAPT-C-27
SOCRadar10 more threat groups on this CVEShowing 5 of 15 · Attribution, campaigns and the malware each one runsUnlock free
  • ip110.39.231.3647

    GreyList · Nov 29, 2025

  • ip112.198.238.3045

    Maltiverse IP List · May 4, 2025

  • ip110.39.228.7862

    AbuseIPDB Hourly Update · Feb 2, 2026

  • ip110.36.86.8355

    AbuseIPDB Hourly Update · Jan 29, 2026

  • ip196.189.96.5945

    Abuse.ch-Urlhaus-C&Cs · Dec 24, 2024

SOCRadar5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 9.8 (AV:N)

    Jun 17, 2026 · NVD

  3. Added to CISA KEV catalog

    Feb 13, 2026 · CISA

  4. Added · GHSA-p5wr-5p37-2wm6 published (critical)

    Feb 7, 2026 · GitHub Security Advisory

  5. Initial · CVE published

    Feb 6, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

  • 26×SVRS was changedApr 14, 2026 – Jun 22, 2026 · SOCRadar CTI
  • 12×TweetsApr 19, 2026 – Aug 21, 2026 · SOCRadar CTI
  • 1×Github_Repos · Github repository created, ridhinva/CVE-2026-1731-BeyondTrust-RCEMay 22, 2026 · SOCRadar CTI

References

8 on the record

Coverage

20 stories from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-1731 is Remote code execution vulnerability in BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA), a critical vulnerability affecting Remote Support(RS) & Privileged Remote Access(PRA) from BeyondTrust. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 72 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 90% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.