BeyondTrust Patches Four Critical Remote Support Flaws —…

July 7, 2026. BeyondTrust released fixes for four vulnerabilities in Remote Support and Privileged Remote Access, two rated CVSS 9.2. Cloud customers were silently patched on April 21, 2026; self-hosted instances remained vulnerable without warning for over two months until the BT26-03 advisory.

July 7, 2026

BeyondTrust has released updates for four vulnerabilities in its Remote Support (RS) and Privileged Remote Access (PRA) products, two of which carry a CVSS score of 9.2. The official disclosure, tracked as advisory BT26-03, arrived in July, but cloud customers had already been automatically patched on April 21, 2026 — a gap of more than two months that left on-premise installations exposed without awareness of the risk.

Key Takeaways

Four CVEs affect RS and PRA version 25.3.2 and earlier: two critical flaws rated CVSS 9.2 allow pre-authentication bypass with unauthorized access and elevated privileges
Exploitation requires a specific enabled authentication configuration but requires no user interaction for the two most severe vulnerabilities
BeyondTrust discovered the flaws internally with assistance from the Anthropic Claude Opus 4.8 AI model and proprietary tooling
Cloud customers were automatically patched starting April 21, 2026; self-hosted instances remain vulnerable until manually updated to version 25.3.3 or later

Authentication Bypass as the Primary Vector

The two highest-impact vulnerabilities, CVE-2026-40138 and CVE-2026-40139, reside in the RS and PRA authentication subsystem. According to The Hacker News, both allow an unauthenticated remote attacker to bypass access controls and gain unauthorized access to the appliance, including elevated privileges, when a specific authentication configuration is enabled.

Cyber Security News confirms that these two flaws require no user interaction, reducing the attack surface and increasing danger in automated scenarios. The technical mechanism, described in general terms by the sources, consists of improper validation of authentication data for CVE-2026-40138 and improper processing of authentication requests for CVE-2026-40139: both conditions manifest pre-authentication, before the attacker's identity is verified.

The other two vulnerabilities, CVE-2026-40140 (CVSS 8.7) and CVE-2026-40141 (CVSS 8.5), complete the picture. The first, in the network communication subsystem, stems from insufficient validation of client-supplied input and can trigger a denial-of-service condition. The second, in the RS and PRA web application component, allows an already-authenticated attacker with limited privileges to access resources or data beyond their authorized scope.

"The most severe vulnerabilities may allow an unauthenticated remote attacker to bypass access controls and gain unauthorized access to the appliance under specific configurations" — BeyondTrust, quoted by The Hacker News

Claude Opus 4.8 and the New Standard in Vulnerability Discovery

BeyondTrust stated it identified the four flaws through internal research assisted by the Anthropic Claude Opus 4.8 AI model, integrated with proprietary tooling. The decision to disclose the discovery method signals an operational shift: AI-assisted vulnerability research is becoming a declared practice, no longer experimental, for enterprise vendors.

The documentation provided does not specify the model's exact role in the process — whether semantic fuzzing, guided static analysis, or assisted review of prior patches — but the explicit citation of the system (version 4.8) indicates BeyondTrust considers this approach part of its security lifecycle credibility narrative. For the enterprise reader, the implication is twofold: AI reduces internal discovery time, yet introduces a competitive dynamic where attackers also possess analogous tools for post-disclosure reverse engineering.

The sources do not document whether other remote-access vendors have adopted similar workflows, nor whether BeyondTrust has shared details of the prompting or fine-tuning applied.

The Discontinuity Between Cloud and Self-Hosted

The most significant finding from a risk-management perspective is the temporal discrepancy between cloud patching and public disclosure. Cyber Security News reports that cloud-hosted customers were automatically patched on April 21, 2026, while the BT26-03 advisory and patches for self-hosted instances were released on July 7, 2026 — an interval of nearly two and a half months.

During this window, on-premise installations remained vulnerable without their administrators having any awareness of the threat. The sources do not specify whether BeyondTrust delayed disclosure for internal coordination, regression verification, or other operational reasons. What emerges is an asymmetric risk pattern: the cloud offers implicit protection through vendor control, while self-management demands a reaction capacity that the information delay undermines.

The dossier does not quantify the number of self-hosted installations still unpatched, nor provide a geographic or sectoral distribution of affected systems.

Historical Context: BeyondTrust as a Recurring Target

The four CVEs fit a pattern of prior vulnerabilities that have already seen BeyondTrust software exploited in real operations. According to The Hacker News, CVE-2024-12356 and CVE-2026-1731 — both in RS and PRA — were repeatedly exploited to deploy web shells and backdoors.

This history modulates the current risk assessment: even absent confirmation of in-the-wild exploitation for the new CVEs, the product's track record shows attackers actively monitor the vendor and maintain ready-to-use toolchains. BeyondTrust has not declared active exploitation for CVE-2026-40138 and related flaws, but the lack of confirmation does not equal absence of risk, especially in remote-access software with elevated privileges that constitutes a high-value target by definition.

The BT26-03 advisory, with a maximum CVSS v4 score of 9.2, places the two critical flaws in the framework's highest severity tier.

Immediate Actions

For self-hosted deployments of Remote Support and Privileged Remote Access, the priority is updating to version 25.3.3 or later, identified by both primary sources as the release that fixes the four vulnerabilities. Versions 25.3.2 and earlier are confirmed affected.

Administrators must verify whether the specific authentication configuration required for exploitation of the two critical CVEs is active in their environment. The sources do not describe the technical details of this configuration, so consulting the BT26-03 advisory documentation directly is necessary.

For organizations with cloud deployments, the risk is mitigated by the automatic patching on April 21, 2026, but verifying the version actually running remains prudent absent direct confirmation from the tenant.

Given the history of exploitation of prior CVEs in the same software, monitoring for anomalous access and hunting for indicators of compromise tied to the techniques documented for CVE-2024-12356 and CVE-2026-1731 can provide a complementary detection layer, though the sources cite no specific indicators for the new flaws.

Why the Disclosure Delay Is a Market Problem

The BeyondTrust case exposes a structural tension in the enterprise security model: the ability to silently patch the cloud before public disclosure creates a protected class of customers and an exposed class, with no alert mechanism for the latter. If the vendor controls the infrastructure, the fix is invisible; if the customer controls it, information is the prerequisite for action, and that information arrived late.

AI as an internal discovery tool accelerates the remediation cycle, but does not solve the distribution phase. For security leaders, the lesson lies in comparing the two deployment models: the cloud offers a time advantage that self-hosted cannot replicate without proactive threat-intelligence processes independent of the vendor.

Why doesn't the CVSS 9.2 score translate to universal exploitation?: The two critical flaws require a specific authentication configuration to be enabled. They are not exploitable in all default conditions, though the lack of user interaction makes them dangerous once that condition is met.
What distinguishes this disclosure from previous BeyondTrust disclosures?: The notable novelty is the explicit disclosure of AI model use (Claude Opus 4.8) in the discovery process, signaling formalization of practices not previously made public, and the cloud-vs-self-hosted disclosure gap of over two months.
Are the April 21, 2026 patches the same as those released in July?: Sources indicate cloud customers were automatically patched from April 21, 2026, while self-hosted patches are available with the BT26-03 advisory dated July 7, 2026. It does not emerge whether these are the same package or different iterations.

Information verified against cited sources and current as of publication.

Sources

Sources and references