SEC595: Applied Data Science and AI/Machine Learning for Cybersecurity Professionals


Experience SANS training through course previews.
Learn MoreLet us help.
Contact usBecome a member for instant access to our free resources.
Sign UpWe're here to help.
Contact UsTheori has disclosed and published a proof-of-concept exploit for a high-severity flaw in the Linux kernel affecting most distributions of Linux released since 2017. CVE-2026-31431, CVSS score 7.8, allows an unprivileged local attacker to elevate privileges to root by using a ten-line Python script to "trigger a deterministic, controlled 4-byte write into the page cache of any readable file on the system," which could include modifying a setuid binary. Researcher Taeyang Lee discovered this vulnerability with assistance from Theori's Xint Code AI tool, while "studying how the Linux crypto subsystem interacts with page-cache-backed data." Theori disclosed the vulnerability to the Linux kernel security team on March 23, 2026, and patches were committed to the mainline kernel by April 1. However, Will Dormann, Senior Principal Vulnerability Analyst at Tharros Labs, has criticized the researchers for not coordinating with maintainers of major Linux distributions before disclosure, meaning the exploit was public before many distributions could address the flaw; several major distributions do not have patches available at the time of this writing. Users should consult their distribution's advisories to determine if they are affected, and apply kernel updates once available, "prioritizing Kubernetes nodes and CI/CD runners." CERT-EU offers temporary mitigation recommendations to take while awaiting a kernel patch: "Disable the algif_aead kernel module persistently on all affected systems" and "[block] AF_ALG socket creation via seccomp policies on all containerised workloads and pipelines, regardless of patch status."

Even though researchers focused on the Linux 6.17 and 6.18 kernel version, AF_ALG support was introduced in the Linux 2.6.38 kernel; in this case, if you're running kernel version 4.14, November 2017, or higher, you need to take action. The trouble here is that the kernel updates aren't out yet, so you just can't apply the update _yet._ The first thing is to see if you're running the algif_aead module; if not, the mitigation, which unloads and blocks the module loading, isn't going to impact you but will prevent the module from being loaded nefariously. After disabling the module, block AF_ALG socket creation via seccomp policy. You can detect exposure by checking for connections to the AF_ALG socket.
Copy Fail
CERT-EU
Jorijn Schrijvershof
Ars Technica
The Register
BleepingComputer
Mastodon
Web hosting control panel provider cPanel has disclosed and issued patches for a critical flaw affecting all currently supported versions of cPanel and its WebHost Manager (WHM) administrative interface application. CVE-2026-41940, CVSS score 9.8, allows a remote unauthenticated attacker to gain access to the control panel by using carriage return line feed (CRLF) injection to bypass authentication in cPanel and WHM 11.40 and later. The flaw also affects WP Squared, a platform offering cPanel management of WordPress hosting. Watchtowr estimates that cPanel and WHM are in use for over 70 million domains; Rapid7's Shodan scan indicates about 1.5 million vulnerable cPanel instances are exposed to the internet. The flaw was added to the US Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog (CISA KEV) on April 30, with a mitigation deadline of May 3. Domain name registrar Namecheap responded by immediately "appl[ying] a firewall rule to block access to TCP ports 2083 and 2087," and has applied the fix to all servers as of 2:42 UTC on April 28. cPanel's advisory gives instructions to users to upgrade to fixed cPanel and WHM versions 11.86.0.41, 11.110.0.97, 11.118.0.63, 11.126.0.54, 11.130.0.19, 11.132.0.29, 11.136.0.5, and 11.134.0.20, and to WP Squared version 136.1.7. If updates cannot be applied, cPanel recommends mitigation by blocking ports 2083, 2087, 2095, and 2096 at the firewall, or by stopping cpsrvd and cpdavd. cPanel has also provided a detection script to check for indicators of compromise.

CVE-2026-41940 was added to the CISA KEV on April 30 with a due date of May 3. The good news is, patches are out. Odds are you're interreacting with cPanel and WHM through a hosted service provider rather than on-premises infrastructure. In this case, you should have regular updates for cPanel and WHM client components on hosted servers. Verify out the processes as well as the guidance from your hosting provider to ensure you're all on the updated versions.
A vulnerability with a CVSS score of 9.8, remote code execution, affecting every version of the vendors, and a possible target space of 70 million domains, isn’t good. Couple that with it already making its way onto the KEV catalog, and it’s a train-wreck in the making. Any sysadmins supporting cPanel or WHM need to get patching ASAP.
cPanel
Watchtowr
CyberScoop
TechCrunch
SecurityWeek
The Register
The Hacker News
Google has patched a maximum-severity flaw in Gemini CLI and the run-gemini-cli GitHub action. Novee Security, who disclosed the issue to Google, states that the vulnerability allows a remote attacker to trigger command execution on the host system by planting a malicious configuration in a repository's workspace, taking advantage of Gemini CLI's automatic trust of the current workspace folder when running in headless mode. The agent would act on the file "without review, sandboxing, or human approval." A CVE has not yet been assigned at the time of this writing. Google's fix is to require explicit trust of folders before configuration files are processed, which means that pipelines including GitHub actions "will fail to load workspace-specific settings until they are updated to use explicit trust mechanisms." Users whose workflows run on trusted inputs should set GEMINI_TRUST_WORKSPACE to 'true', and users whose workflows run on untrusted inputs should review Google's guidance for hardening against malicious content and setting the environment variable. Gemini CLI versions 0.39.1 and 0.40.0-preview.3 include folder trust and tool allowlisting, and the run-gemini-cli GitHub Action will automatically run the latest version unless a workflow specifies an older version.

This now requires explicit trust for folders containing configuration and environment variables in headless mode. This is consistent with the behavior in interactive mode. They have also changed the allowlisting under the CLI in --yolo mode, no longer ignoring any fine-grained controls in your .gemini/settigns.json file, as that could lead to RCE and other actions from untrusted input. Make sure you explicitly define trusted folder and tool use. Bottom line: if it works in interactive mode, you'll be fine in headless mode.

The phrase “automatic trust” should never be found when involving AI data ingestion or “learning.”
GitHub
Novee
SecurityWeek
The Register
The Hacker News
On Wednesday, April 29, 2026, SonicWall released firmware updates to address three vulnerabilities in SonicOS. CVE-2026-0204 is a high-severity improper access control vulnerability, CVE-2026-0205 is a medium-severity post-authentication path traversal vulnerability, and CVE-2026-0206 is a medium-severity post-authentication stack-based buffer overflow vulnerability. The flaws affect SonicWall's Gen6, Gen7, and Gen8 firewalls. If users are unable to apply the fixes immediately, SonicWall "strongly recommends that administrators fully disable HTTP/HTTPS-based firewall management and SSLVPN on all interfaces, and restrict management access to SSH only." SonicWall's security advisory credits the Advanced Research Team at CrowdStrike.

CVE-2026-0206 can be used to crash your firewall, CVE-2026-0204 can be used to bypass access controls and access management functions, and CVE-2026-0205 could be used to interact with restricted services. These are good arguments for not exposing the management interface to the Internet. While it's always challenging to get approval for downtime, I'm not sure that disabling the SSLVPN is a viable workaround; the downtime to apply the update will be of much lower impact and take less time than the meeting.
SonicWall is used heavily in the Small and Medium-sized Enterprise (SME) and Managed Service Provider (MSP) space. Organizations should prioritize the patches and follow SonicWall’s mitigation guidance. Don’t wait for it to find its way onto the KEV catalog.
An open-source tool built by the NSA for mapping the network architecture of industrial control systems (ICS) and supervisory control and data acquisition (SCADA) systems is vulnerable to information exposure, warns the US Cybersecurity and Infrastructure Security Agency (CISA). CVE-2026-6807, CVSS score 5.5, could allow an attacker to expose sensitive information by using crafted session data to trigger improper handling of XML input, due to insufficient hardening of the XML parsing process in GRASSMARLIN v3.2.1. This flaw will not be patched, because GRASSMARLIN reached end of life (EoL) status in 2017. CISA recommends users ensure control systems are not exposed to the internet; isolate control system networks and remote devices from business networks and protect them behind firewalls; use up-to-date VPNs for remote access, acknowledging that a VPN "is only as secure as the connected devices"; and follow best practices for defending ICS and protecting against social engineering. Rapid7 penetration tester Anna Quinn has published a proof-of-concept exploit and notes that the main vector of risk for exploitation is through phishing.

Make sure you are not running unsupported software in an environment that matters. End-of-life tools do not get fixes, so the only real control you have left is isolation and access discipline. GRASSMARLIN was a niche tool that provided passive ICS network mapping and visualization. It has not been supported since 2017 and there are other open source and commercial tools that can take its place. From an operational standpoint, you need to know where tools like this are running, who uses them, and how they connect to the rest of your environment. If you cannot patch it, you need to contain it or replace it. But first you have to identify where these tools are in your organization.

While the flaw itself is likely a low risk, requiring phishing to exploit, GrassMarlin is EoL (since 2017), so you really need to replace it. Nobody is working on it, and we probably all have that developer who says they can fix it, but the reality is we need to move to other actively supported solutions. When it was created, there were limited options in the OT/ICS space for this type of monitoring/situational awareness, now there are alternatives from Dragos, Armis, Nozomi, and more.
Given that the tool reached EoL and that other comparable open-source and commercial alternatives exist, simply move to another platform. In the meantime, CISA’s mitigation guidance should be followed. Bottom line: don’t expose your control systems to the internet if you don’t have to.
CISA
The Register
Microsoft has announced that it intends to fully deprecate support for legacy TLS versions (TLS 1.0 and TLS 1.1) for POP3 and IMAP4 connections to Exchange Online later this year. Microsoft ended support for TLS 1.0 and 1.1 in 2020 and began blocking older versions of TLS in early 2023 while allowing users to opt in to continue their use. Starting in July 2026, Microsoft will begin to completely block legacy versions of TLS. Microsoft expects that the July deadline will affect only users who have opted in to using legacy endpoints. Affected users are urged to ensure that their email clients, applications, and libraries support TLS 1.2 or later and are not using legacy endpoints to connect to Exchange Online. For reference, TLS 1.0 and 1.1 were introduced in 1999 and 2006, respectively.

While this particular change applies to email (POP/IMAP), we need to make sure we're not using TLS 1.0 and 1.1 versions across the board, because they have known vulnerabilities and use exploitable encryption mechanisms. In other words, they are cryptographically invalid or null. In most cases current versions of email clients support TLS 1.2 or higher seamlessly and you just have to orchestrate upgrades. Regardless of the user position — e.g., “you'll need to wrestle this out of my cold dying hands” — deprecating these TLS versions started in 2023. You've got until July to work to understand the use and find a functional alternative before you hit the hard block. I don't see any indications of a reprieve on this one.
By forcing users to opt in to continued use of vulnerable versions of TLS, Microsoft could gauge the impact to its install base. They now have the data they need. It’s simple, it’s time to fully deprecate and for users to move on to TLS 1.3.

There are probably not very many of you, and most of you know who you are.
The Register
BleepingComputer
Microsoft
Microsoft
On Tuesday, April 28, Google and Mozilla both released updates for their flagship browsers to address a variety of security issues. Google Chrome 147 includes fixes for 30 flaws, including four critical use-after-free vulnerabilities. Firefox 150.0.1 includes fixes for four security issues, including three critical and high-severity memory safety bugs and a high-severity information disclosure vulnerability.

We're so used to regular Chrome updates, it's easy to miss Mozilla/Firefox updates. Firefox is less obvious about a needed restart. If you're checking and restarting all browsers weekly, if not more often, you should be fine, but make sure you're not missing any. Don't wait for the restart needed prompt.

Just by accident, there must be periods when browsers are in a trustworthy state. One just cannot figure how to identify the period.
The US Federal Bureau of Investigation's (FBI's) Internet Crime Complaint Center (IC3) has published a PSA "to warn the public of cyber threat actors increasingly using sophisticated, cyber-enabled tactics to impersonate legitimate businesses to hijack freight, steal high-value shipments, and reroute deliveries, resulting in a surge of strategic cargo theft." Losses from cargo theft in the US and Canada last year were estimated to be nearly $725 million, a 60 percent increase over the figures for 2024. The threat actors start by compromising carrier brokers' load board accounts; a load board is an online marketplace where shippers can connect with carriers. Once threat actors have control of that account, they post fake loads online and respond to bidding carriers with malicious links that turn over control of the carriers' systems. They then bid on real loads and reroute them. The PSA includes a list of indicators of cyber-enabled cargo theft schemes as well as advice for shippers and carriers to protect their businesses.

While this sounds like a plot out of a movie, the actions are happening. Where supported, make sure that you're using MFA on shipping accounts. At a minimum, use strong passwords. Make sure that you validate messages from shippers, and that staff sent to pick up loads are legitimate. Make sure that you're using known validation (e.g., phone numbers) not information provided in the message, handed to you by the carrier, or painted on their vehicle. The FBI PSA is short: provide it to your shipping department to post and implement.
Given that pretty much everything these days has a cyber component, it’s only logical that evildoers would find a way to ply their trade. Credential compromise is now in the top three methods for enabling cyberattacks. If you haven’t already, move quickly to multi-factor authentication to better protect against credential compromise.
Researchers at the US Department of Energy's Oak Ridge National Laboratory in Tennessee have developed a new device that can detect both spoofing and jamming of GPS satellite signals. While there are commercial tools available to detect and mitigate GPS jamming, doing the same for spoofing has proven more complex. "The ORNL technology detects location, time, and data spoofing. It is effective regardless of whether the attacker is faking all satellite signals or only a few, and regardless of movement. Its most distinctive feature is the ability to distinguish spoofing, even when fake and real signals are equally strong, a functionality no other known systems possess." The ORNL team's focus for this project is trucking: GPS spoofing has been used to make it appear that goods are on their expected route, while they have actually been rerouted by thieves. The ORNL team is now working on making the device more affordable.

Think of this as a driver alert, like a carbon-monoxide detector, that there is a problem with your GPS signal. The ORNL team is using a software defined radio (SDR) and GPU coupled with mathematics applied to the radio signals received to detect spoofed location, time and data signals. Their solution is not dependent on a GPS receiver and not subject to GPS jamming (which causes failure by overwhelming that receiver). The next steps include creating an international standard for spoofing detection and threat assessment to drive production of commercial devices for deployment across the trucking industry.
Colorado legislators voted against a bill that would have dismantled parts of the state's right-to-repair law. That law, the Consumer Right to Repair Digital Electronic Equipment, was passed in 2024 and took effect in January 2026. The new bill would have exempted equipment designated as "critical infrastructure" from the right-to-repair protections. In early April, the bill passed a state Senate committee hearing unanimously and passed in the full state Senate on April 16. However, a lengthy hearing in the Colorado House’s State, Civic, Military, and Veterans Affairs Committee earlier this week resulted in the bill being voted down and indefinitely postponed. French law enforcement officials have detained a 15-year-old individual in connection with the cyberattack on France's National Agency for Secure Documents (ANTS), the country's agency that manages passports, driver's licenses, identification cards, and other secure documents. The suspect allegedly broke into ANTS systems, stole data, and tried to sell the data online.

The right to repair farm equipment is important. Consumer electronics, not so much. With the possible exception of batteries and power supplies, they are very reliable. They are often cheaper to replace than repair. (I just replaced a 32" smart TV for $75, plus tax and delivery; I can hardly imagine getting the old one repaired for that).

Due to French privacy laws, the name and pronouns of the detainee are being withheld. They were detected by the handle "breach3d" offering the exfiltrated records for sale. Prosecutors are seeking formal charges and judicial supervision — translation: they want to throw the book at this person, and each offense has a maximum of seven years prison and a $350,000 fine. As this is a minor, expect a lesser final sentence, but it’s still a message sent to would-be attackers.
Ars Technica
The Record
Reuters
The Register
SANS Internet Storm Center StormCast Friday, May 1, 2026
Libredtail; FreeBSD dhclient vuln; Linux Copy-Fail; @sans_edu Detecting AI Pickling
https://isc.sans.edu/podcastdetail/9914
Danger of Libredtail
https://isc.sans.edu/diary/Danger+of+Libredtail+Guest+Diary/32936
FreeBSD dhclient vulnerability
https://www.freebsd.org/security/advisories/FreeBSD-SA-26:12.dhclient.asc
Linux Copy-Fail Vulnerability CVE-2026-31431
Bryan Nice Research Paper
https://www.linkedin.com/in/bryannice/
https://www.sans.edu/cyber-research/detecting-ai-pickling
SANS Internet Storm Center StormCast Thursday, April 30, 2026
Odd Requests; MSFT LNK Bug Exploited; Secure Boot Fix; TLS Updates; SAP npm malware
https://isc.sans.edu/podcastdetail/9912
Today's Odd Web Requests
https://isc.sans.edu/diary/Todays+Odd+Web+Requests/32934
Incomplete Patch of APT28's Zero-Day Leads to CVE-2026-32202
Assess Secure Boot status with Microsoft Defender
Deprecating Legacy TLS and Endpoints for POP and IMAP in Exchange Online
SAP Related npm Packages Compromised
https://www.stepsecurity.io/blog/a-mini-shai-hulud-has-appeared
SANS Internet Storm Center StormCast Wednesday, April 29, 2026
Odd Vercel Header Usage; GitHub Vuln Patches; MSFT RDP Notification Bug
https://isc.sans.edu/podcastdetail/9910
HTTP Requests with X-Vercel-Set-Bypass-Cookie Header
https://isc.sans.edu/diary/HTTP+Requests+with+XVercelSetBypassCookie+Header/32930
GitHub Vulnerability CVE-2026-3854
https://www.wiz.io/blog/github-rce-vulnerability-cve-2026-3854
Microsoft RDP Notification Bug
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
AI adoption across tools, applications, and agents is outpacing governance. Teams must understand where AI introduces risk, how data is exposed, and how agentic behavior impacts control. Join Cato, Microsoft, Forrester, and Dayforce on 05/20 12p EST at SASEfy 2026, the virtual summit for SASE and AI, to identify risk, secure AI, and adapt Zero Trust.
2026 SANS Survey on Unstructured Data | Take this survey to benchmark your organization, share insights, and influence better tools, strategies, and security for unstructured data risks.
SANS 2026 Security Awareness Report® Survey is Now Open | Your perspective as someone leading security awareness is exactly what shapes it. Take 5 minutes to contribute to the most trusted benchmark in the industry and be entered into a prize draw to win a $500 Amazon gift card.
Webinar | SANS 2026 Cybersecurity Readiness in Government Survey Insights: Is the Public Sector Ready for the Next Cyber Threat? | Thursday, May 28 at 10:30AM ET.