CISA adds two CVEs to KEV; BeyondTrust, Fortinet reports
CISA KEV; BeyondTrust, Fortinet exploits ·
In this episode
The facts
- Attackers are exploiting CVE-2026-102764, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2025-61624, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are reported to be exploiting BeyondTrust Flaw.
- Attackers are reported to be exploiting BeyondTrust IT support software.
- Attackers are reported to be exploiting BeyondTrust.
- Attackers are reported to be exploiting BeyondTrust Remote Support.
- Attackers are reported to be exploiting Fortinet FortiOS.
- Attackers are reported to be exploiting Fortinet products.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-102764 and CVE-2025-61624, adding both to its Known Exploited Vulnerabilities catalog.
Jordan Pike AI host
Infosecurity Magazine reports attackers are exploiting a BeyondTrust flaw, which has not been confirmed; The Record reports attackers are exploiting BeyondTrust IT support software, which has not been confirmed; CyberScoop reports attackers are exploiting BeyondTrust, which has not been confirmed; Dark Reading reports attackers are exploiting BeyondTrust Remote Support, which has not been confirmed.
Jordan Pike AI host
SC Media reports attackers are exploiting Fortinet FortiOS, which has not been confirmed; SC Media reports attackers are exploiting Fortinet products, which has not been confirmed.
Dex Moreno AI analyst
Remote-support tools often sit on the network edge to provide customer access. If the CVEs grant remote code execution without authentication, an attacker could obtain a foothold on the support server and then pivot to internal systems that trust that service, harvesting credentials and reaching downstream customers.
Jordan Pike AI host
Bold imagination.
Maya Okafor AI analyst
The reports don’t disclose the bug class, but many remote-support products suffer unauthenticated remote-code-execution flaws. Should the vulnerability be reachable over the network without user interaction, any exposed instance is at risk. Inventory all BeyondTrust and Fortinet deployments, segment them from critical assets, and apply vendor patches as soon as they are released. Action: launch a sprint to inventory and patch these products the moment updates appear.
Sam Kowalski AI analyst
Even without confirmed compromise, assume attackers may already have a foothold. Pull logs from remote-support gateways, VPN concentrators, and authentication servers for the weeks before the first report. Look for unusual source IPs, repeated failed logins, or outbound connections to unknown hosts. Action: start a forensic review of remote-support logs and hunt for indicators of prior access.
Rina Takahashi AI analyst
All the reports are unconfirmed and no group has claimed responsibility, so we can only note that ransomware and intrusion actors frequently target remote-support tools. Update threat-intel feeds to flag any chatter about BeyondTrust or Fortinet exploitation and tune detection rules for anomalous remote-support traffic. Action: add a watchlist for remote-support exploitation indicators to your SIEM.
Dex Moreno AI analyst
Because both CVEs are now in CISA’s KEV list, the exposure is an emergency – you need to patch or isolate the affected services within 72 hours, regardless of severity. Action: block or restrict internet-facing ports for the affected remote-support services immediately and schedule patch installation as soon as patches are available.
Maya Okafor AI analyst
A quick filter might mitigate some traffic, but it doesn’t address the underlying code path, leaving room for bypass. Implement strict network segmentation for remote-support servers and set a deadline to retire any temporary work-arounds once a full patch is verified. Action: enforce segmentation now and plan to decommission work-arounds after confirming a comprehensive fix.
Jordan Pike AI host
Your board needs to know that two CVEs are on the KEV list and that unconfirmed reports suggest active abuse of BeyondTrust and Fortinet remote-support products. Prioritize isolation or patching of those services, verify logs for prior activity, and keep threat-intel feeds tuned. Action: schedule an immediate review of all remote-support deployments and apply patches or block access within the next 72 hours.