Exploited CVEs / CVE-2026-1731

CVE-2026-1731

BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA) OS Command Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted, and the vulnerability is known to be used in ransomware campaigns. Federal agencies were required to remediate by 2026-02-16 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

CriticalCISA KEVRansomware
9.8
CVSS base
88%
EPSS exploit probability
Critical
Severity
2026-02-13
Added to KEV
2026-02-16 (past due)
CISA due date

Actively exploited BeyondTrust Remote Support (RS) and Privileged Remote Access (PRA) vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2026-02-13.

Senserva AI read on CVE-2026-1731CISA required actionOfficial fix for CVE-2026-1731Admin questions#18 hottest CVE right now

Senserva AI Opinion for CVE-2026-1731

This is an unauthenticated OS command injection flaw in BeyondTrust Remote Support and Privileged Remote Access, tools that by design grant remote access into your environment, so a compromise hands attackers a direct foothold. It carries Severity Critical (CVSS 9.8) with an 87 percent EPSS score, is confirmed in CISA KEV as of 2026-02-13, and is already being used in ransomware campaigns. Because these products are internet-facing and hold privileged sessions, exploitation puts your entire remote access chain at risk.

Do this: Apply BeyondTrust's fixed release for RS and PRA immediately, and if you cannot patch today restrict internet exposure of these appliances and review session logs for unauthorized command execution.

AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-1731

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch immediately
Exploited in the wild and used in ransomware campaigns.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Move this ahead of everything else in the queue, then verify the fix actually landed on every exposed device.

Updated August 15, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-1731

Published
2026-02-13
Last revised
2026-02-13
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when
0%25%50%75%100%CISA KEVCISA KEV on 2026-02-132026-07-17: EPSS 88%2026-07-17: EPSS 88%2026-07-24: EPSS 87%2026-07-24: EPSS 87%2026-08-02: EPSS 88%2026-08-02: EPSS 88%2026-08-13: EPSS 88%EPSS 88%2026-02-132026-08-13

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-02-13 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 9.8; EPSS first scored at 88.1%
  • 2026-07-24 EPSS 88.1% to 87.2%
  • 2026-08-02 EPSS 87.2% to 88.1%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-02-16 (past due).

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

Official fix for CVE-2026-1731

Check the vendor's security advisory channel for the patched Remote Support (RS) and Privileged Remote Access (PRA) versions and workarounds.

Common questions about CVE-2026-1731

Is CVE-2026-1731 actively exploited?

Yes. CVE-2026-1731 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-02-13, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 88%. CISA also reports it is known to be used in ransomware campaigns.

What is the CISA deadline and required action for CVE-2026-1731?

CISA set the federal (BOD 22-01) remediation due date at 2026-02-16, which has passed; treat any unremediated system as overdue. The verbatim 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.

What fixes CVE-2026-1731?

Check the vendor's security advisory for the patched Remote Support (RS) and Privileged Remote Access (PRA) versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-1731?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-1731's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited BeyondTrust CVEs
Authoritative references

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.