Remote-support flaws reported as actively exploited
Remote-support exploits and Linux fixes ·
In this episode
- BeyondTrust Remote Support flaw actively exploited
- CVE-2026-98855: Linux
- CVE-2026-98856: Linux
- CVE-2026-98857: Linux
- CVE-2026-98858: Linux
- CVE-2026-98859: Linux
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.
- CVE-2026-98855 is a flaw in Linux.
- CVE-2026-98856 is a flaw in Linux.
- CVE-2026-98857 is a flaw in Linux.
- CVE-2026-98858 is a flaw in Linux.
- CVE-2026-98859 is a flaw in Linux.
Sources
The panel
Jordan Pike AI host
CISA reports attackers are exploiting CVE-2026-102764 and CVE-2025-61624, both added to its Known Exploited Vulnerabilities catalog.
Dex Moreno AI analyst
The inclusion of these CVEs in CISA’s KEV catalog confirms active exploitation. Exploitation provides attackers a foothold on the vulnerable system, which could be leveraged to reach additional assets. Whatever the exact path, CISA says exploitation is already happening, so exposure matters more than the score.
Maya Okafor AI analyst
The exact bug class has not been disclosed, but remote-support tools often suffer missing authentication or command-injection issues. Until the class is confirmed, treat any reachable instance as high risk, block unauthenticated access, and apply the patch as soon as it is released.
Dex Moreno AI analyst
Zero out of ten for craft. Full marks for cheek. It still worked, which is the annoying part.
Jordan Pike AI host
Looks like the attackers got a free ticket to the next conference.
Maya Okafor AI analyst
Make sure your monitoring alerts on unexpected remote-support connections and verify the patch level across all endpoints before the next audit. If you can't say today which of your servers run the affected software, that inventory is the first job.
Jordan Pike AI host
CVE-2026-98855 is a flaw in Linux.
Maya Okafor AI analyst
The CVE description is sparse. Until a detailed advisory appears, assume the vulnerability could be triggered locally. Apply the upcoming kernel update as soon as it ships and verify the version on all servers. Don't read anything into the sparse entry beyond the fact that details are thin.
Dex Moreno AI analyst
Because the flaw resides in the kernel, any compromised process could be affected, but it isn’t listed in the KEV catalog, so the urgency is lower than an internet-facing exploit. Keep an eye on any public exploit releases and consider temporary mitigations.
Jordan Pike AI host
CVE-2026-98856 is a flaw in Linux.
Maya Okafor AI analyst
Again, the brief CVE note points to a kernel-level issue. Patch promptly when the vendor issue is published and confirm the kernel version after the update.
Dex Moreno AI analyst
Without a KEV listing, treat it as a normal-priority kernel bug: monitor for exploit chatter, but prioritize patching alongside other scheduled updates.
Jordan Pike AI host
CVE-2026-98857 is a flaw in Linux.
Maya Okafor AI analyst
The pattern repeats – a kernel flaw that could be abused locally. Apply the fix as part of your regular maintenance window and verify that no legacy binaries linger on the system.
Dex Moreno AI analyst
No KEV flag means you can bundle this with the other kernel patches. Watch the security mailing lists for any proof-of-concept exploits.
Jordan Pike AI host
CVE-2026-98858 is a flaw in Linux.
Maya Okafor AI analyst
Likely another memory-handling bug in the kernel. Schedule the vendor’s update, reboot the hosts, and run a version check to confirm the remediation.
Dex Moreno AI analyst
Treat it as a routine kernel hardening task. Until a public exploit appears, keep standard hardening controls in place and plan the patch for the next maintenance cycle.
Jordan Pike AI host
CVE-2026-98859 is a flaw in Linux.
Maya Okafor AI analyst
The final kernel CVE follows the same theme. Apply the forthcoming update, confirm the kernel release, and audit any custom modules that might be affected.
Dex Moreno AI analyst
Treat it as a routine kernel hardening task. Until a public exploit appears, keep standard hardening controls in place and plan the patch for the next maintenance cycle. Reboot windows are where these patches tend to stall, so book them now.