Point hosts at BeyondTrust Remote Support and PRA and flag CVE-2026-1731 (OS command injection) from a version compare plus sleep-only confirm. Non-destructive.
Sleep-only check on the WebSocket version header. Advisory
Detect
Fingerprints BeyondTrust and flags CVE-2026-1731 by version.
Report
Counts checked, product, affected, and confirmed.
Targets
Hosts, IPs, or URLs, one per line. Empty input uses localhost.
Overview
This workflow finds BeyondTrust Remote Support and Privileged Remote Access and sorts each host by whether its version falls in the CVE-2026-1731 range. Remote Support and PRA are the jump boxes vendors use to reach your floor. CVE-2026-1731 is OS command injection on those products. CISA listed it on KEV. A forgotten appliance on a support subdomain is how an old advisory becomes a current incident. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on BeyondTrust), reads the version from /login with a fallback to the root body, and compares that number to the range table in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for exposure management. CVE-2026-1731 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only asks the WebSocket version header to sleep. It does not open a shell or run a command.
Run it on a schedule when the estate changes. New hosts and delayed patch windows are the reason the same check is worth more the second week than the first.
Pipeline
Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
Fingerprint each host as BeyondTrust Remote Support and Privileged Remote Access from the public page title, then GET /login and parse the version. A host counts as affected only when the fingerprint matches and the version is inside the encoded range.
Confirm only those flagged hosts with a sleep-only check on the WebSocket version header.
Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
Emit the summary counts: hosts checked, product hits, affected, confirmed, and errors.
Inputs
Target list. Hostnames, IP addresses, CIDR ranges, or URLs, one per line. JSONL with a url field also works. Point it at scope you are authorised to test. Fingerprint is read-only GET. Confirm is a sleep-only probe on the WebSocket version header, and only after the version flag.
Outputs
results.jsonl. One row per host: URL, whether BeyondTrust Remote Support and Privileged Remote Access was detected, the version read, the affected flag, and whether the sleep confirm succeeded.
summary.json. Counts across the list: targets, product hits, affected, and errors.
Integrations
HTTP. Unauthenticated GET to the product root and /login. Confirm is a sleep-only check on the WebSocket version header of flagged hosts.
Sample output
The records below are illustrative and do not come from a real run. They show one BeyondTrust Remote Support and Privileged Remote Access host inside the CVE-2026-1731 range, one patched host, and one host that is not the product.
Which BeyondTrust Remote Support and Privileged Remote Access versions does this flag?
Every build before 25.3.2. 25.3.2 and later is the floor the graph treats as not affected. The compare uses the version the product itself served.
Does a flagged host mean CVE-2026-1731 was exploited?
No. A flagged row is patch-lag against the range table. Confirm only asks the WebSocket version header to sleep. Treat a confirmed row as evidence the injection still answers, not as proof someone already used it.
Is this check safe on production?
Yes. Fingerprint is read-only GET. Confirm is a sleep-only probe, only on hosts already in range. It does not open a shell, run a command, or write files.
Does the check need credentials?
No. It fingerprints the public page and reads /login the way an external scanner would.
What is CVE-2026-1731?
OS command injection in BeyondTrust Remote Support and Privileged Remote Access. CISA listed it on KEV. This workflow flags by version, then confirms with a sleep-only check on the WebSocket version header.