0-Day - CVE-2026-102764 - Improper Origin Validation in BeyondTrust Remote Access Tool

Last Updated: 2026-10-16T16:45:08Z

What’s Happening

BeyondTrust publicly disclosed a CVSS 9.3 Improper Origin Validation leading to unauthorized file operations in both their SaaS and Self-Hosted Remote Access tools. Their synopsis:

BeyondTrust has remediated a critical vulnerability in Remote Support (RS) that could allow a remote attacker to perform file operations on an affected appliance.

The vulnerability exists within internal components of Remote Support. The components did not adequately validate the origin of the messages it received. Under the right conditions, this could be used to perform file operations on the appliance.

Affected customers were originally alerted on October 9, though no further details were given at that time. BeyondTrust publicly announced the CVE, Security Advisory, and blog on Thursday October 15.

Related Links:

CVE-2026-102764

BeyondTrust Security Advisory - BT26-05

Beyontrust Blog: ARMORY CASTLE and BT26-05: What Security Teams need to know

Mandiant - ARMORY CASTLE Exploits BeyondTrust

Actions

Affected Versions

Product Version
Remote Support All version <= 26.2.3

Patches have been automatically applied to anyone running the SaaS appliance. Anyone running a Self-Hosted appliance should apply patch BT26-05-RS immediately.

There are no workarounds for this vulnerability.

IoC’s

These IoC’s are taken from Mandiant’s blog about the compromise:

File Indicators Description SHA-256
app_84304470%2Ephp Staging Webshell N/A
mangoapi.php SAWFLY Webshell dc14e215269a93fdbc4c1a80b984c23faf7af0911c6dbb85309796a6f2ae95fb
ingredi_ws BARECLAW Tunneler 1f19b9a27d79c11bda00a1e8faf74a7fdd683d38ccef1b60df2fd0307e3aa462

YARA Rules

rule G_Hunting_Webshell_SAWFLY_1 {
  meta:
author = "Google Threat Intelligence Group"    
  strings:
    $b32 = "ABCDEFGHIJKLMNOPQRSTUVWXYZ234567" ascii wide
    $rc4 = "range(0,255)" ascii wide
    $pack = "pack('H*'," ascii wide
    $eval = "@eval(" ascii wide
    $code404 = "http_response_code(404)" ascii wide
  condition:
    filesize < 20KB and
    all of them
}
rule G_Hunting_Backdoor_BARECLAW_1 {
  meta:
    author = "Google Threat Intelligence Group"

  strings:
    $s1 = "[%s ws_socks5d] " ascii wide
    $s2 = "--obfs requires --token" ascii wide
    $s3 = "mux: %s (frame[%lu]: %s)" ascii wide
    $s4 = "cannot create stream pump/writer thread (stream %d)" ascii wide
    $s5 = "reject: bad or missing token from %s" ascii wide
    $s6 = "listening on %s path=%s (token=%s obfs=%s max_tunnels=%d threads=%d)" ascii wide
    $s7 = "--ws-path must start with '/'" ascii wide
    $b_xorshift = { 48 c1 e0 17 48 31 c1 48 89 f0 48 c1 e8 1a 48 31 f0 48 31 c8 48 c1 e9 11 48 31 c8 }
  condition:
    uint32(0) == 0x464c457f and (5 of ($s*)) or ($b_xorshift and (3 of ($s*)))
}

Notes

Companies really need to stop putting security advisories behind support portals that require logins. This 0-day has been known about for a week and public information about it is just released about it now. If you’ve had a vulnerable self-hosted appliance and either missed the alert on October 9, or simply were unable to patch because you couldn’t find anymore information, then that’s an extra week you’ve exposed yourself for for no reason.

4 Likes

Thank you so much for the fantastic writeup!

1 Like

No worries! I usually try to write up anything I come across but by the time I do usually someone else has already done it :laughing: This was the first one that I knew about that no one else was already looking into so figured I should share what I know to the community.

2 Likes

That’s what this is all about!

1 Like