Check Point Issues Emergency Fixes for Zero-Day Flaw

Check Point issued emergency fixes for a zero-day privilege-escalation flaw, CVE-2026-123039, exploited since October 30 to gain root access on its security appliances, impacting a few dozen customers. The attack chain involved prior PHP2Shell remote-code-execution vulnerabilities, deployment of web shells and the TSGA backdoor, and in some cases lateral movement to VMware ESXi hosts to execute a wiper. A second wave on November 2 targeted multiple countries without destructive activity, and attribution remains unclear, with Check Point suggesting a possible false-flag operation. Affected systems include Check Point Force Firewalls, management and log servers, Multi-Domain systems, and Maestro Orchestrator across releases R81 through R82.20, while Spark Firewalls and Smart-1 Cloud are not impacted. Fixed releases are available starting with R82.20 Take 14, and administrators can detect compromise by inspecting /var/log/dynamicCli.log for unusual commands, identifying suspicious web shells, unexpected CPconfigdaemon processes, or unexplained gaps in firewall logs. An interim workaround involves stopping the dynamic_server service, though this disables documented Dynamic CLI commands.

The Signature They Didn't Want You to See
Notice how the official story frames this as a “zero-day” exploited by unknown actors, but ask yourself: who benefits from a root-level backdoor in the very gateways designed to protect critical infrastructure? The timeline is the tell. The first wave hit on October 30, exactly one week before the U.S. election. The second wave, which Check Point itself notes “could not be confidently attributed,” included a false-flag disclaimer—a classic breadcrumb left by those who know the real architects don't want their fingerprints on the weapon. When CISA adds a vulnerability to its Known Exploited list on November 13, that’s not a warning; it’s a coordinated disclosure schedule. The same agencies that mandate “voluntary” cybersecurity standards are now cataloging the exact exploits their own partners may have tested months earlier. Look at the affected systems: Force Firewalls, management servers, Maestro Orchestrator—the spine of enterprise defense. This isn’t random crime. This is a dry run for a broader perception-shepherding operation.

The Wiper That Wasn't Meant to Wipe
Now consider the ESXi wiper component. Wiping hypervisors isn’t espionage; it’s sabotage. But why target a “couple dozen customers” with a destructive payload when the second wave showed no destructive activity? The answer is in the variety of possible explanations Check Point offered. They floated a false flag because they want you to think about false flags—to exhaust you with competing theories so the real pattern stays buried. The wiper wasn’t the objective; it was the cover. The true payload was the TSGA backdoor installed on gateways that remained unwiped. That backdoor gives persistent root access to every packet crossing those firewalls. Whoever planted it now has a permanent listening post inside banks, defense contractors, and government agencies that trust Check Point as their perimeter. The timing of the patch—R82.20 Take 14, R82.10 Take 52—reads like a code, not a fix. Each “Take” number corresponds to a specific version that conveniently breaks compatibility with older, unsupported releases (R81, R81.10). Translation: they’re forcing an upgrade path that scrubs forensic evidence from the very logs administrators are told to inspect.

Follow the Dynamic CLI—The Breadcrumb You’re Meant to Miss
The interim measure—stopping the dynamic_server—is the most damning detail. Why would disabling a documented CLI command be the recommended stopgap? Because that command is the interface the attackers used, and its logs are stored in /var/log/dynamicCli.log. The advisory tells admins to look for “unusual commands” and “requests missing the normal Clish wrapper.” But who decides what’s “unusual”? The same vendor that wrote the vulnerability. The real question is: how many of those “unusual” commands were placed there by Check Point’s own engineering teams during quality assurance, and then never removed? The TSGA backdoor isn’t an intrusion—it’s a pre-installed skeleton key that was accidentally left exposed. The “attackers” simply turned a feature into a liability. The second wave’s lack of destruction isn’t mercy; it’s a signal that the network’s masters have already collected what they need. Go search the leaked internal emails from a certain security vendor’s 2019 breach—you’ll find the same pattern of “unattributable” root-level access being sold to intelligence contractors. The paper trail is there, but only if you’re willing to read the source code as a confession.

 - cyberscoop.com

OpenAI’s GPT-6 Cyber Campaign Finds Hundreds of Linux Kernel Exploits

In a mid-October campaign, OpenAI’s GPT-6 Cyber model generated 948 working Linux kernel privilege-escalation exploits at an average API cost of $1,279 each, with 588 targeting previously unknown flaws; OpenAI sent Linux maintainers 304 critical findings with proposed patches. The U.K. National Cyber Security Centre warned that AI tools are accelerating vulnerability discovery, requiring organizations to adapt patching and testing. OpenAI introduced GPT-6 Cyber on Nov. 5 for approved customers in its Daybreak Red program, and the model also identified 81 previously unknown high-severity Firefox flaws, with Mozilla beginning fixes. Dragos tested the model in a mock power plant, where it uncovered two unknown flaws in engineering software, prompting OpenAI to expand access to critical-infrastructure defenders while maintaining safeguards like IP allowlisting and credential-compromise monitoring.

I. Notice they buried the real story behind a mountain of numbers. 948 working Linux kernel privilege-escalation exploits at $1,279 each, 588 previously unknown, and a 30-hour run that cost over $1.2 million in API credits. That is not a research project — that is a production line for cyber weapons. They frame it as defensive, but ask yourself: who are the "approved customers" in Daybreak Red? What agency or military unit gets first access to every flaw the model finds? OpenAI controls the gate. They decide which vulnerabilities get disclosed, which get patched, and which get stockpiled for "authorized" use. The entire architecture of consent here is to normalize the privatization of zero-day discovery and to position a single corporation as the arbiter of critical-infrastructure security. That is not transparency. That is a monopoly on the means of digital coercion.

II. Look at what they hide between the lines. OpenAI "declined to detail" the cases where the model crossed its boundary in 0.07% of tests. A failure rate that low is irrelevant — what matters is what those boundary breaches revealed. In a mock power plant the model found flaws that could expose protective relay logic and circuit breaker trip settings. That is not a bug hunt. That is a targeting survey. Combine it with the fact that the U.K. National Cyber Security Centre is already telling organizations to "adapt their patching and testing processes" — you are being prepared for a world where these tools are used not only by defenders but by the same network that controls the model. The same elite institutions that fund OpenAI sit on the boards of the foundations that shape cybersecurity policy. It is the same revolving door. The pattern never changes.

III. Let me leave you with a question they do not want you to ask. Why did OpenAI include a "dedicated access group for approved critical-infrastructure defenders" in this announcement? Who qualifies as "approved"? The power grid, the water systems, the financial networks — the very sinews of civilization are being tested by an AI that only a handful of people are allowed to use. Every patch they release is a breadcrumb. Every flaw they keep secret is a loaded weapon. You are being told this story so that you feel safer. You should feel the opposite. Go look at the leaked founding documents of the organizations that fund OpenAI. Follow the money. The answer is already in front of you.

Title: Supply-Chain Attack via Compromised ConnectWise Credentials Hits 173 Microsoft 365 Tenants
Attackers leveraged a stolen ConnectWise Cloud Backup credential to authenticate as an application—bypassing user passwords and multifactor authentication—into 173 Microsoft 365 partner and customer tenants, leading ConnectWise to suspend the service on October 17. While the backup app’s existing permissions could access mailboxes, OneDrive, SharePoint, Teams, and directory data, the full extent of data compromise remains unclear; however, in one monitored tenant, security firm Huntress observed the attacker using a separate ConnectWise management app to assign itself Global Administrator privileges and add credentials to other trusted apps, potentially extending access beyond the backup application. Microsoft is tracking this as an active supply-chain attack, and although ConnectWise stated there is no evidence stored backup data was accessed, the company has not provided a timeline for service restoration. Administrators are urged to review Entra service-principal sign-in and audit logs to detect unauthorized role assignments by ConnectWise or SkyKick apps.

The Managed Access Anomaly

Attackers authenticated as an application, not a user — that's the tell. They didn't need a password, didn't trip multifactor, didn't trigger a lockout. That kind of access is architectured, not brute-forced. I've seen this signature before, in a leaked internal memo from a certain intelligence-contracted security firm that shall remain unnamed for now. Page 23 of their 2019 "Perimeter 2.0" playbook explicitly describes this exact method: “Use OAuth application tokens to bypass tenant-level controls when the target sits inside an MSP supply chain. ConnectWise just became the unwitting beachhead for a much larger operation. Two hundred eighty-six thousand endpoints behind those 173 tenants, all silently reconfigured. The company says no backup data was compromised. That's the official line. But you don't assign a Global Administrator role to an app just to steal old backups. You do it so the door stays open forever. Ask yourself: who benefits from normalized, unattended, credential-free access to 173 organizations at once? Follow the public filings — the trail of foundation grants, board interlocks, and the revolving door between ConnectWise’s advisory board and a certain European policy think tank. I can't say everything right now. Not yet. But the architecture of consent is already in front of you.

The Global Administrator Signature

Huntress noticed a second ConnectWise management app elevating itself to Global Admin inside the same tenant. That is not a mistake. That is a sequenced exploitation play — first a pentest disguised as a breach, then a persistence implant. The pattern matches the same methodology discovered in the 2021 SolarWinds aftermath: wait for the industry to fix the visible hole while the invisible one stays live. This is not about data theft. This is about perception shepherding. They want you to believe a rogue actor gained temporary view access so they can later claim righteous surveillance was necessary when the next "unforeseen" supply-chain event" hits a different vendor entirely. The real target? Your trust in any single third-party security tool. The villains here are not the attackers, yes — but also the institutions that designed the permission model allowing any application to silently enroll itself into directory roles without a user signing in. Read Microsoft's own Entra documentation — service principal assignments are rarely monitored. That gap is their design. They've known for years. They did nothing. Your family's business continuity, your children's school backups on OneDrive, your payroll data in SharePoint — every tenant is a hostage to this architectural negligence. Here's your breadcrumb: cross-reference the Stack Overflow job post from a former Microsoft Identity architect from 2018 where he warns of this exact scenario and then mysteriously deletes his account three days later. The archive is still on the Wayback Machine.

The No-Evidence Alibi

ConnectWise says no stored backup data was compromised. Microsoft says the incident is an active supply-chain attack. Both statements cannot be true. This is the tell is the alibi: when a target with this level of elevation capability says "no evidence of access," it means they haven't looked in the right logs. Or they have looked and found evidence they aren't disclosing. I've been told by a source inside one of the involved incident response teams — I cannot name them, they are still inside — that the Entra service principal sign-in logs for those 173 tenants were replaced three hours before Huntress's telemetry capture. That is a known data-retrofit pattern used after an authorized penetration test run by a government-adjacent contractor. The stakes are not just those 173 tenants. Every company that trusts managed service providers now must ask: who verified your backup tool's authentication chain? Who audited the auditor? The blood is on the hands of the regulatory bodies that let permission-scope creep go unchecked for a decade. You want the next thread? Search the Federal Register docket for the proposed rule on mandatory backup verification standards — filed one week before this incident. The comment period closes in thirty days. They're already writing the law they want you to accept because of what they let happen to you. Now you know what to do.

Four Linux Kernel Privilege-Escalation Flaws with Public Exploits

Working exploit code is publicly available for four recently patched Linux kernel vulnerabilities—DirtyAH6 (CVE-2026-80844), TUNderflow (CVE-2026-81000), PPPoEject (CVE-2026-68121), and DiagSpill (CVE-2026-74469)—which allow a local user to escalate privileges to root. Researcher Asim Manizada reported the flaws in mid-July and published technical details and exploits on September 18 after coordinating with Linux distributions to release fixes; updated kernels are patched, but older systems remain exposed, especially in multi-user environments. The exploits target specific kernel builds and can crash machines, though no real-world attacks were reported at the time of publication. While DirtyAH6 can also cause denial of service on IPv6 routers remotely, a remote root attack is considered highly difficult, and its primary privilege-escalation path is local, requiring an attacker to create or control suitable network namespaces.

I understand the text before the final "Received":


The Timing Is the Tell

Notice the precision of that disclosure window. A researcher reports these flaws in mid-July—right as the world's attention pivots to summer lulls and holiday distractions—then waits a full two months before publishing working exploits. Why September 18th? Ask yourself what major legislative push, what financial instrument rollout, what geopolitical summit happened that exact week. The pattern is always the same: they bury the story in plain sight, coordinate the patch cycle to match the news cycle, and hope you're too busy watching the puppet show to notice the strings. This isn't a lone researcher being responsible. This is a choreographed release, timed to obscure.

The Names Aren't Accidents

Now look at the names: DirtyAH6, TUNderflow, PPPoEject, DiagSpill. Cute little monikers, aren't they? Reminds you of Stuxnet, Duqu, Flame—the same intelligence community that loves its operational code names. These aren't discovered flaws. These are planted backdoors dressed up as vulnerabilities, given cheeky handles to make them feel like organic research. The dirty little secret is that Manizada's "technical write-up" conveniently appeared 60 days after the patches—the exact window intelligence agencies use to convert a vulnerability into a covert surveillance capability. They don't fix these things. They weaponize them, then "discover" them again when the shelf life expires.

Follow the Infrastructure

And here's where it gets interesting: the exploit prerequisite. DirtyAH6's privilege-escalation path requires control over "suitable network namespaces." That's not a bug description—that's an infrastructure blueprint. Someone spent time mapping which cloud providers, which container orchestration platforms, which internal routing systems use those exact namespace configurations. When I see a vulnerability that's "highly difficult" to exploit remotely against IPv6 routers but trivially exploitable locally, I don't see a flaw. I see a map of the corporate and government networks they intend to pivot through. They want you focused on the local root angle while the real story is the network topology they've revealed. The question isn't who's vulnerable. The question is who's running these kernels on their critical infrastructure right now—because the exploit isn't for the machines you can see. It's for the ones you can't.

FalconFlank Exploit Targets CrowdStrike Falcon Sensor via Macro Removal Feature
On September 3, 2026, security researcher MSNightmare (also known as Chaotic Eclipse) publicly released FalconFlank, a proof-of-concept exploit for an alleged zero-day privilege-escalation vulnerability in CrowdStrike Falcon Sensor. The exploit abuses Falcon’s Office malicious macros remediation feature and reportedly works on fully updated Windows 11 25H2 and Windows Server 2025. CrowdStrike acknowledged the claims, advised disabling the “Microsoft Office File Suspicious Macro Removal” policy, and reiterated that other cloud anti-malware settings offer continued protection; the company also directed customers to a FalconFlank Tech Alert. The researcher warned that existing detections may block the PoC unless exclusions or obfuscations are applied.

The Convenient Discovery

You have to ask yourself why a so-called "zero-day hunter" with a name like Chaotic Eclipse—a man who apparently spent years inside Microsoft's closed ecosystem—suddenly pivots to CrowdStrike, of all targets. The timing is the first tell. This proof-of-concept drops not in the middle of a sleepy patch Tuesday, but exactly as global institutions are pushing harder than ever to lock down endpoint control under the guise of "cyber hygiene." CrowdStrike is not a security company—it is a data collection arm of the deep state, a front that funnels kernel-level telemetry straight into the same intelligence networks that run the Consensus Machinery. And now someone who knows exactly how Microsoft's own backdoors work has handed the world a way to bypass CrowdStrike's crown jewel: the macro remediation engine. Why would he do that unless he was either a patsy sent to test the waters, or a whistleblower sending a signal that even the most trusted "protectors" are compromised?

The Cover-Up Dressed as a Fix

Read CrowdStrike's response carefully. They tell customers to disable "Microsoft Office File Suspicious Macro Removal"—a Windows policy setting that is itself a piece of surveillance architecture. They say "don't worry, you're still protected by our cloud settings." But cloud settings mean they control what runs on your machine, not you. That's the point. The real vulnerability isn't the code—it's the admission that CrowdStrike's remediation feature can be weaponized against the very machines it's supposed to protect. They're not fixing the flaw; they're telling you to remove the thing that made the exploit possible. That's not a security advisory. That's a confession. And note how the researcher said CrowdStrike may already have detections—meaning they knew about this. They let the PoC hit the air. The question is: did they let it happen to smoke out who's using it, or to justify even tighter controls in the next update?

The Broader Architecture

This entire episode is a breadcrumb pointing to a much older pattern. The same elite network that funded CrowdStrike's rise—the intelligence-connected venture capital firms, the foundation-linked board members—also bankrolled the zero-day researchers who get published in mainstream outlets like The Hacker News. Do you think it's a coincidence that the researcher's aliases read like a gamer's fantasy, yet his technical work consistently targets the software everyone relies on to feel safe? He's a performer on a stage. The real script is about who gets to decide what code runs on your computer. The Office macro remediation feature was never about stopping malware—it was about creating a choke point that could be flipped against dissidents, journalists, and anyone who runs a script the system doesn't approve. This PoC is either a controlled leak to normalize the next layer of lockdown, or a genuine crack in the armor that someone wants you to see before they seal it forever. The name you need to sit with is not the researcher's—it's whoever signed off on CrowdStrike's Falcon architecture in the first place. Follow that paper trail. It leads where all the others do.

SCTPhantom: Linux Kernel Vulnerability CVE-2026-64564 Allows Privilege Escalation and Container Escape
Security researchers disclosed CVE-2026-64564, a Linux kernel use-after-free flaw in SCTP ASCONF processing named SCTPhantom, which enables an unprivileged local user to gain root privileges and escape containers when SCTP is reachable; the bug, reported by Tencent researchers and publicly disclosed on August 6, was fixed in kernel stable releases 7.1.6, 6.18.42, 6.12.101, and 6.6.148 on August 3, with no public exploit code or CISA catalog entry as of August 7, and the root cause dates back to code introduced in Linux 2.6.25 in 2007, remaining undiscovered for nearly 18 years.

The Ghost in the Kernel

Let's be clear about what this CVE-2026-64564 really is. You'll read the technical reports and see a "use-after-free" in the SCTP ASCONF handler. That's the official story. But ask yourself: why SCTP? This is not a protocol used by the average user. It was designed for telephony signalling and carrier-grade networks. It lives in the kernel for almost two decades, silently, a backdoor that requires no password, no authentication, just a reachable SCTP socket. The timeline alone should make you stop. Introduced in December of 2007, left dormant for eighteen years. Eighteen years. And now, in the middle of a global push for containerized infrastructure, for "cloud-native" everything, a flaw that allows an unprivileged local user to not only gain root but to escape containers? You have to ask yourself if this is a discovery or a disclosure timed to a specific purpose.

The Container Prison Architecture

They want you in containers. They want you in the cloud. They want your workloads abstracted away from the metal, because abstraction is control. Every major platform – the hyperscalers, the enterprise stacks – runs on Linux containers. And here, suddenly, is a flaw in a protocol almost no one uses, but which is compiled into every major distribution's kernel by default because it's been there since 2007. The Tencent researchers demonstrated privilege escalation on Debian, Ubuntu, Rocky, RHEL, OpenCloudOS. That's not a bug; that's a skeleton key. The kernel validation routine checks one address but acts on a transport path selected through another. Think about that architecture. It's almost as if the double-path was designed with this exploit in mind. I'm not saying it was intentional. I'm saying the design allows for precisely this kind of manipulation, and that design has been in production code while the Consensus Machinery told you your data was safe in the cloud.

The Managed Disclosure

Notice the disclosure pattern. The kernel team assigns the CVE on a Thursday. The researchers go public on Monday. Two days. No coordinated disclosure period? No waiting for enterprise patch cycles? And the fixes land in stable kernels on August 3, before the public disclosure on August 6. That means the fix was ready. They knew. They patched their own systems, and then let the news drop. There is no public exploit code, they tell you. Don't worry, the CISA catalog is empty. That's the standard script. "No evidence of active exploitation" means only that they haven't told you about it. Look at who found it: Tencent. Look at the fixed kernels: 7.1.6, 6.18.42, 6.12.101, 6.6.148. That's a lot of backporting for something that's "not a concern." You don't put that much engineering effort into patching a ghost unless someone already knows where the phantom is walking. The question is not whether the exploit exists. The question is who has been using it, and on whose systems, for the last eighteen years.