dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 16 Feb 2026. Known ransomware use
Privileged Remote AccessApplication · Beyondtrust

CVE-2026-1731

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to 25.1 / 25.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

BeyondTrust Remote Support and older versions of Privileged Remote Access contain a critical pre-authentication remote code execution vulnerability. An unauthenticated remote attacker can send specially crafted requests to execute operating system commands in the context of the site user. This is a critical RCE affecting the core authentication mechanism.

MitigationApply the latest BeyondTrust patches or upgrades to a supported version. If immediate patching is not possible, restrict network access to the BeyondTrust services via firewall rules or network segmentation to reduce exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Privileged Remote AccessApplication
Affected:< 25.1
Remote SupportApplication
Affected:< 25.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed BeyondTrust product and version
    Check the web interface login page for version information, or check installed software on the server (Windows: Programs and Features, Linux: dpkg -l or rpm -qa | grep -i beyond)
    Affected if The installed version is PRA < 25.1 or RS < 25.3.2
  2. Determine if BeyondTrust web services are internet-facing
    Scan network boundaries or review firewall rules to see if ports used by the product (typically 443, 8443 for HTTPS) are exposed to untrusted networks
    Affected if The web interface is directly accessible from untrusted networks without VPN or network segmentation
  3. Check for unusual HTTP requests in logs
    Review web server logs (typically in /var/log/ or within the product's log directory) for malformed or suspicious HTTP requests, especially those containing shell metacharacters or unusual path patterns
    Affected if Logs show suspicious HTTP requests that may indicate exploitation attempts
  4. Verify product configuration for unauthenticated access
    Check the product's administrative interface for settings related to unauthenticated access or API exposure
    Affected if Unauthenticated endpoints are enabled or the product accepts connections without requiring authentication

A user is affected if their BeyondTrust installation is version PRA < 25.1 or RS < 25.3.2 AND the web interface is network-accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 25.1 / 25.3.2 or later
Fixed in 25.125.3.2
Interim mitigation

Apply the latest BeyondTrust patches or upgrades to a supported version. If immediate patching is not possible, restrict network access to the BeyondTrust services via firewall rules or network segmentation to reduce exposure.

Recommended fix High confidence

Privileged Remote Access 25.1+ or Remote Support 25.3.2+

  1. Identify which BeyondTrust product is deployed: Privileged Remote Access (PRA) or Remote Support (RS)
  2. Check the currently installed version of the product
  3. If using Privileged Remote Access and version is lower than 25.1, upgrade to version 25.1 or later
  4. If using Remote Support and version is lower than 25.3.2, upgrade to version 25.3.2 or later
  5. After upgrading, verify the new version is correctly installed and the vulnerability is no longer present

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Privileged Remote Access Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1731 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data