Digest · Thursday

Security digest: October 15, 2026

2 editorial briefs, 1 known exploited (cisa kev) addition and 6 critical advisories.

All digests · RSS · Markdown

Take stock

  • Act now: BeyondTrust Remote Support CVE-2026-102764 Zero-Day. Organizations running self-hosted BeyondTrust Remote Support (any version through 26.2.3), and self-hosted Privileged Remote Access as a precaution.
  • Check exposure: Siemens Software Center DLL Flaw Abused in ClickFix Attacks. Security teams with Windows endpoints, since attackers bring the vulnerable signed program themselves, and organizations that run Siemens Software Center for Siemens engineering software.
  • Do you run any of these? Atlassian Multiple Products. They are being exploited in the wild (CISA KEV). Patch or mitigate if you do; CISA’s federal deadline is 2026-10-18.
  • Go: 5 critical advisories (vitess.io/vitess, github.com/dgraph-io/dgraph/v25, github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd/v3, github.com/kedacore/keda, github.com/kedacore/keda/v2, github.com/containers/podman, go.podman.io/podman/v6). Check with govulncheck ./....
  • npm: 1 critical advisory (@tanstack/start-server-core, @tanstack/react-start, @tanstack/solid-start, @tanstack/vue-start). Check with npm audit (or: npm ls <package>).
  • None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.

Editorial briefs

Act now

· Vulnerability · CVE-2026-102764

BeyondTrust Remote Support CVE-2026-102764 Zero-Day

If you run a self-hosted BeyondTrust Remote Support appliance, patch it today and assume it may already be compromised; an espionage group used this as a zero-day for about seven weeks.

Must act: Organizations running self-hosted BeyondTrust Remote Support (any version through 26.2.3), and self-hosted Privileged Remote Access as a precaution.

Can relax: Teams that do not use BeyondTrust; SaaS customers need no patch (BeyondTrust patched them by October 9) but should still review admin changes and stored credentials.

  1. Inventory every Remote Support and Privileged Remote Access deployment, whether it is SaaS or self-hosted, and its version.
  2. Apply BT26-05-RS to self-hosted Remote Support today (upgrade to 24.3.1 or later first if older), and confirm it in the /appliance interface.
  3. Preserve logs and a snapshot before patching or rebooting any appliance that was internet-reachable while unpatched.

Read the brief →

Check exposure

· Vulnerability · CVE-2026-110936

Siemens Software Center DLL Flaw Abused in ClickFix Attacks

Siemens users get the fix automatically, but the real threat is attackers shipping their own signed, older copy as a malware loader, so Windows defenders should block the indicators and hunt rather than rely on patching.

Must act: Security teams with Windows endpoints, since attackers bring the vulnerable signed program themselves, and organizations that run Siemens Software Center for Siemens engineering software.

Can relax: Teams with no Windows endpoints; Siemens Software Center users whose installs have updated to 4.0.9.8 or later and whose hunts find none of the indicators.

  1. Start Siemens Software Center on every machine that has it so it auto-updates to 4.0.9.8 or later, and confirm the version.
  2. Block 96.62.218[.]59, wizardexpensive[.]com and 2.27.248[.]127 on firewalls, proxies and DNS resolvers.
  3. Hunt for SiemensSoftwareCenter.exe running from AppData\Local\Programs or launched by msiexec, and for Siemens Software Center startup entries on PCs that never had it.

Read the brief →

Known exploited (CISA KEV) 1

Added to CISA’s catalog on this day: confirmed exploitation in the wild. Due date = CISA’s deadline for US federal agencies.

CVEProduct and flawCISA due
CVE-2026-21589Atlassian Multiple Products
Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability
2026-10-18

Critical advisories by ecosystem 6

GitHub-reviewed advisories rated critical, published this day (Pacific time).

Go 5

Check: govulncheck ./...

npm 1

Check: npm audit (or: npm ls <package>)