Check Point's management server zero-day had a two-month head start

Check Point's Security Management Server is the kind of box you stop thinking about because it isn't the firewall — it's the brain running it. It stores your security policies, processes the admin changes, and ingests the logs from everything else in the estate. So when Check Point disclosed CVE-2026-93616 this week, a pre-auth path traversal that lets an unauthenticated visitor to the management web service upload and run arbitrary scripts, it's the kind of bug that makes you reach for your keyboard. It's rated CVSS 9.8, the fix is an emergency hotfix in R82.20, and the flaw isn't limited to the one box in the headline.

What stings isn't the vulnerability itself. Path traversal in a web service is a bug CISA and the FBI have been telling vendors to stop shipping since 2024, and "unforgivable" has been the word of record for it since 2007. What stings is the timeline. Check Point says the attacks ran on July 23, more than six weeks before the hotfix shipped. That's roughly a two-month window in which anyone who could reach the management server had a pre-auth code-execution path into the system that controls the policies and logs of the entire firewall estate. The advisory doesn't name the targets or say what the attackers did after landing, which is the company's way of not making it worse. And it pairs the zero-day with a second, quieter story: a pre-auth VPN flaw (CVE-2026-85102) fixed on September 9 that's now being actively probed, aimed at Spark, Check Point's small-business line. Two pre-auth paths on the control side of the network in the same release cycle is a pattern worth noticing, even if it isn't a confirmed campaign.

If you run Check Point, the move isn't dramatic. Confirm you're on the R82.20 hotfix across every affected component — Security Management Server, Multi-Domain Security Management Server, Log Server, Multi-Domain Log Server, and SmartEvent — because the blast radius is wider than the one box that made the news. Then restrict who can actually reach the management web service, since the exploit path only exists if that service is reachable, and finally hunt for signs of compromise in that six-week gap. A pre-auth RCE into your control plane means "assume something was changed or exfiltrated" until you've verified otherwise. The uncomfortable part is that this was never going to be an outage you'd see in a dashboard. So what does your team actually look at first when a management server is quietly compromised — the logs you trust it to keep, or the logs an attacker already got to?

The Hacker News Logo
Source image 1

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

Enterprise AI Is Quietly Becoming a Systems Integration Problem

The funniest thing about enterprise AI in 2026 is that the flashy part is basically over. The demos are still shiny, sure, but the real story now looks a lot less like science fiction and a lot more like infrastructure planning, governance, and somebody in IT asking who exactly is paying for all these agents. Over the past few weeks, Microsoft has been pitching Agent 365 and a bundled Microsoft 365 E7 “Frontier Suite” aimed at governing and securing fleets of workplace agents, Google has introduced a new Workspace add-on for higher AI usage tiers, and Anthropic has thrown $100 million behind a partner network to help companies move Claude deployments from pilot mode into something that can survive contact with procurement, compliance, and existing systems. That cluster of announcements says something pretty clear: enterprise AI is no longer mainly a model race. It is becoming a packaging, controls, and implementation race. The clever model still matters, obviously, but once every vendo...
Read more