Hello and welcome to the Thursday, November 12, 2026 edition of the SANS Internet Storm Center's Stormcast. My name is Johannes Ullrich. We're recording today from Jacksonville, Florida. And this episode is brought to you by the SANS.edu Graduate Certificate Program in Cybersecurity Engineering. And as so often after a Patch Tuesday, we have a bit of a cleanup episode here today covering issues that we may have missed. Apache, for example, today released an update fixing a critical vulnerability in mod_http2. The vulnerability allows for remote code execution. The problem here is that during stream processing, the assign_headers function is used to assign request headers to specific streams. That's where a heap overflow happens. And well, that of course, then could potentially be used to trigger remote code execution. No working exploit has been made public yet. Disabling HTTP/2 can be used to mitigate the issue. Of course, you may run into other issues. If you, for example, have proxies translating to HTTP/2, you have always to be careful with HTTP request smuggling in this case. And Fortinet published 89 different advisories addressing more than 100 different vulnerabilities across its product portfolio. 17 of these vulnerabilities are considered critical, FortiMail being sort of the product with the most critical vulnerabilities being addressed in this update. Now, several of the critical issues may lead to arbitrary code execution without authentication. Too many vulnerabilities really to talk in detail on about each particular vulnerability. But well, if you have Fortinet products in your environment, there's probably a patch that you must apply. And now for these product. And as listeners probably expect when they hear about that many vulnerabilities all of a sudden popping up. Yes, AI took a part in discovering these vulnerabilities. And Ivanti also released its November 2026 security update. Now in this update, there is one patch for another SQL injection vulnerability, in Endpoint Manager. This SQL injection vulnerability may be leveraged to accomplish remote code execution. And then we also have a vulnerability in Ivanti CSA that allowed altering trusted EPM Core certificates without authentication. And then we got another, well, Saturday, Wednesday after patch Tuesday, thanks to Nightmare Eclipse. Nightmare Eclipse released what they're calling SignDrop. SignDrop is a privilege escalation vulnerability in the Windows Common Log File System. What makes this kind of interesting is that about a year ago, Microsoft added HMAC based authentication to CLFS log files to make it harder to abuse them in response to some of the vulnerabilities in this overall system. While SignDrop abuses exactly that new feature with some symlink and timing tricks, a regular user can escalate to system on Windows 11, 26H2 and Windows Server 2025. A proof of concept exploit has been posted to GitHub. So far, Microsoft has not confirmed the issue. There is no CVE number. I have not seen any reports of it being exploited. And as tempting as it may be, disabling CLFS log authentication is probably not a good workaround. Again, that was specifically established to prevent other security issues. It would bring back some of these older CLFS attacks that before that feature was introduced. And a quick follow up to the N-able N-central story from earlier this week. N-able has now released the 2026.4 hotfix 2 for N-central. And with that release notes explaining what they're fixing here. They're identifying three different CVE numbers that are addressed in this update. Now, if you remember N-able shut down actually its own sort of cloud -based infrastructure in response to these vulnerabilities being reported to N-able. And yes, now we get the patch for it. The initial news release, I think, talked about like 30 vulnerabilities. So not sure if these are just the sort of the critical ones they're patching here. They're actually being exploited right now. Or if they sort of consolidated some of these vulnerabilities. There are some reports that attackers are already probing for vulnerable paths that were leaked. Of course, there have been a lot of issues with N-able N-central in the past. This could be also some older stuff. The good news, many of you appear to have listened. Shadowserver's count of exposed N-central servers dropped from about 1,338 to around 148. So almost like a factor of nine or 10 here. If you run N-central on premise, apply the hotfix before you bring the server back online. And probably still avoid exposing it if you can help it. Well, and that's it for today. Thanks for listening. Thanks for liking. Thanks for subscribing. And talk to you again tomorrow. Bye. You