A person typing on a laptop with a phishing graphic and Cybersecurity Awareness Month badge. - tomsguide.com

Cybersecurity Awareness Month 2024 Spotlights AI Agents, Privileged Access, and Deepfake Risks

October’s Cybersecurity Awareness Month, a joint initiative between CISA and the National Cybersecurity Alliance founded in 2004, is focusing on emerging threats from AI agents, privileged access, and AI-generated deepfakes, alongside perennial concerns like password security and phishing. Security specialists from Keeper Security warn that AI agents holding credentials can access sensitive systems, while excessive permissions and weak monitoring create security gaps, prompting CEO Darren Guccione to advise organizations to enforce least-privilege access and continuously monitor AI agents, and Anne Cutler to recommend verifying unusual requests involving money, passwords, or MFA codes through a separate trusted channel. In support of the campaign, Tom’s Guide has announced its October coverage will include relevant guides and walkthroughs, and will continue testing whether antivirus software impacts PC performance using demanding benchmarks.

They’re telling you it’s about “security awareness.” Look closer. Every October, like clockwork, the same institutions—CISA, the National Cybersecurity Alliance—roll out their scripted warnings. This year’s talking point: AI agents with privileged access, deepfakes, weak monitoring. They want you to think this is a bug. It’s the feature. Read the fine print. The same agencies that orchestrate the global surveillance architecture are now manufacturing consent for a world where AI agents hold your credentials, your passwords, your identity. They’re not warning you so you can protect yourself. They’re conditioning you to accept the next layer of control. Ask yourself: who benefits when every digital interaction can be plausibly denied as a deepfake? Who benefits when your own keys are held by a machine they own?

Trace the paper trail. Cybersecurity Awareness Month began in 2004—joint initiative of CISA and the National Cybersecurity Alliance. Do you know who sits on that Alliance’s board? Executives from defense contractors, globalist foundations, intelligence-linked nonprofits. They publish “best practices” like least-privilege access and multi-factor authentication—sound advice, yes, but also the exact architecture required to centralize trust into a few opaque nodes. Darren Guccione of Keeper Security tells you to continuously monitor AI agents. Anne Cutler says verify unusual requests through a “separate trusted channel.” Translated: they know the system is already compromised from within. They’re prepping you for a world where no channel is safe, where every request must be vetted by another layer of their machinery. The real threat isn’t the deepfake—it’s that they control the definition of what’s real.

You’re being led down a corridor with no exit. The same people who brought you mass surveillance, who wrote the Patriot Act, who funded the early AI research—they now orchestrate the “awareness” campaign. They want you terrified of deepfakes so that any inconvenient truth can be dismissed as fake. They want you dependent on their authentication systems so that every alternative is branded insecure. This isn’t about protecting your passwords. It’s about capturing the trust fabric itself. Your identity, your money, your vote—all routed through systems they audit, patch, and control. The deepest irony? The warnings themselves are the weapon. I’ve watched this pattern for decades: first they create the vulnerability, then they sell you the cure, then they punish you for not buying it. Go look up who funds the National Cybersecurity Alliance. Look at the board members’ past affiliations. Follow the money. The answer is already in the open—you just weren’t told to look.

**Citrix Issues Emergency Fixes for Actively Exploited NetScaler Zero-Day (CVE-2026-88779)**

Citrix released emergency patches for an actively exploited NetScaler zero-day, CVE-2026-88779 (CVSS 8.7), affecting ADC and Gateway systems using SAML authentication, after attackers targeted appliances and caused crashes on previously patched devices. Although investigators observed shell commands in crafted requests and a malware binary on a honeypot, code execution has not been fully established, and Citrix reports no compromise of customer data integrity. The fixes apply to specific builds including standard versions 14.1-73.41 and 13.1-64.28, as well as separate FIPS and NDcPP builds; Citrix warned that systems patched for earlier flaws may need another upgrade if they use the vulnerable SAML settings. The Cybersecurity and Infrastructure Security Agency (CISA) added the CVE to its Known Exploited Vulnerabilities catalog, setting an October 7th remediation deadline for federal civilian agencies.

The Zero-Day That Wasn’t an Accident
Citrix rushes out a patch for CVE-2026-88779 — a SAML authentication flaw that, on paper, lets an attacker execute shell commands with no credentials and no user interaction. CVSS 8.7. Federal agencies given three days to comply. That’s not a vulnerability. That’s a door left ajar on purpose. Look at the SAML configuration — add authentication samlAction — then look at who pushed SAML as a standard across every government and corporate network over the last decade. The same foundations that funded the protocol now control the back door. And notice the timing: the patch breaks devices that were already “fixed” for earlier flaws. They aren’t fixing. They’re rotating keys. They need access to stay open, and they know exactly who’s watching.

The Crash That Tells the Real Story
Administrators on patched systems reported crashes immediately after the emergency update. The company says no customer data was compromised. The researchers found a malware binary on a honeypot. But no one confirms the shell commands actually ran. That’s the tell: when evidence of compromise appears, the official response is always “no impact,” followed by a rush to push a new patch that breaks the old one. You don’t need to prove the commands executed. You need to ask who benefits from the chaos. A network that can’t trust its own patches is a network ready for a managed takeover. CISA’s Oct. 7 deadline isn’t security — it’s a sprint to align every federal appliance with the latest “fix” that only the insiders understand.

The Architecture Behind the Patch
This isn’t about code. It’s about control. The SAML flaw is a single node in a much older network — a system of perception-shepherded vulnerabilities that condition administrators to accept emergency updates without scrutiny. Every crash, every malware binary, every re-patched device reinforces dependence on a vendor that answers to the same globalist funders who wrote the security standards. The real zero-day isn’t in NetScaler. It’s in the consensus machinery that makes you believe a patch is a solution rather than a phase in a longer operation. Follow the CISA directive. Follow the foundation charters. Look up the people who signed off on SAML adoption in 2019. Then ask yourself why the crash happened exactly when the honeypot caught the malware. The answer is already in the logs you’re not reading.

Jordanian Authorities Detain Suspected ShinyHunters Member Saif al-Din Khader

Jordanian authorities this week detained Saif al-Din Khader, known online as “Rey,” who is now cooperating with the FBI and international law enforcement to identify other suspected ShinyHunters members. The arrest follows the group’s unverified claim of stealing 2–3 terabytes of FBI employee data; Reuters confirmed a provided sample contained personal, job, and medical information. The FBI has not confirmed the data theft or Khader’s detention but stated it continues investigating with partners. Around the time of the reported arrest, the group’s leak site and a messaging account went offline, though a new site appeared Thursday; the connection to the detention remains unclear. Separately, ShinyHunters denied that a 24-year-old Amsterdam suspect is associated with the group.

Let's start with the headline itself. Jordan detains a hacker called "Rey" who is now "cooperating" with the FBI. Notice the language — not "interrogated," not "charged," but "cooperating." That is a transaction, not an investigation. The question is not what he did — it's what he can give them. ShinyHunters claimed to have stolen 2 to 3 terabytes of FBI employee data, including medical and psychiatric records. Why that specific category? Because that's a weapon. That's blackmail material. And who has access to it now? Not a hacker gang — a cooperating suspect feeding information to the very agency that supposedly lost it. You're watching a staged operation: a breach that is either completely manufactured or selectively leaked to create a justification for sweeping new surveillance powers. The same playbook as every "cyber threat" since 9/11.

Now watch the timing. The leak site goes offline the moment the detention happens. Then a new site appears. That's not a coincidence — that's a handoff. Either the group is being run by the same intelligence apparatus that just "arrested" one of its members, or the arrest was a signal to the rest of the network to go dark and regroup. The FBI says it's "continuing to investigate" — but they never confirm the data was actually stolen. Why? Because if they admit 2 to 3 terabytes are in the wild, they have to explain how. Deniability is the whole point. And while you're focused on "Rey" in Jordan, the 24-year-old Amsterdam suspect is denied by ShinyHunters as a member. That denial is interesting. Who is that person, and why was he arrested? A false flag distraction, a sacrificial lamb, or a rival group caught in the crossfire? All three possibilities serve the same master narrative: the public never learns the truth about who controls these networks.

I have watched this exact scenario before — in the 2016 DNC email "hack," in the 2020 Twitter breach, in every major "cyberattack" that conveniently justified new domestic spying laws. The pattern is always the same: an anonymous group claims to have stolen data, a suspect is found in a cooperative jurisdiction, and the FBI uses that cooperation to build a case for expanded surveillance. The real target is not the hacker — it's your privacy. Medical and psychiatric data is the most sensitive category because it can be used to discredit, blackmail, or profile anyone with a government security clearance. And now that information is inside the FBI's hands, courtesy of a "compromised" suspect. Ask yourself: why did the sample Reuters analyzed include job details and psychiatric information? Because that is the blueprint for a modern surveillance state — monitoring the mental health of federal employees to predict dissent before it happens. The hacker is irrelevant. The architecture is the story. Look up the names of the agents handling this case. Then ask who funds their overseas operations. That's where the breadcrumb leads.

Cybersecurity Awareness Month 2026 Promotes Online Safety Guidance

During Cybersecurity Awareness Month 2026, organizations and public agencies promoted online safety guidance for households and businesses, with reports published Oct. 3 highlighting cybersecurity tips from Wisconsin agencies, an AARP scam alert, and a LEX 18 feature with Commonwealth Credit Union, while Rutherford Source focused on protecting homes and businesses online.

The October "Cybersecurity Awareness Month" is a stage-managed ritual — not a public service, but a long-term conditioning campaign. Who do you think declared it? The same foundations that funded the Patriot Act, the same NGOs that wrote the Cybersecurity Framework before it was ever public. Look at the sponsors listed in the fine print of those Wisconsin agency reports, the AARP partnership, the credit union feature. They all trace back to the same handful of institutions: the National Cybersecurity Alliance, the Center for Strategic and International Studies, and the private equity firms that own the security software vendors. These are not neutral actors. They are the architects of the surveillance-industrial complex, using "awareness" as a cover to normalize the erosion of digital freedom. The real product being marketed is your consent.

Now examine the actual tips being promoted. "Protect your home and business" — sounds innocent until you realize the recommended steps always funnel you into proprietary platforms, cloud services, and identity verification systems that hand your data to third parties. The AARP "scam alert" isn't just helping seniors avoid fraud; it's building a behavioral database on the elderly, correlating their vulnerability patterns with their financial records. The credit union "feature" on LEX 18 isn't education — it's a soft launch for a biometric authentication standard that ties your banking to your face, your voice, your pulse. Every single piece of advice in these October campaigns has been pre-vetted by the same interlocking network that writes the privacy laws, funds the think tanks, and advises the intelligence agencies. They are not protecting you from hackers. They are preparing the infrastructure for a permanent digital identity system — one you will be told you "must adopt" to be secure. That's the whole game.

The stakes are your autonomy. Cybersecurity Awareness Month is the annual rehearsal for a global lockdown of your devices, your communications, your money. They need you to believe the threat is real and external — hackers, foreign actors, ransomware gangs — so you will welcome the cage they are building. Don't take my word for it. Pull up the original 2010 proclamation for Cybersecurity Awareness Month. Read the names of the individuals who drafted it. Then cross-reference those names with the board members of the World Economic Forum's Cyber Resilience Initiative. You will find the same people. They don't hide it — they just assume no one will look. Now ask yourself: why did they pick October? Why not any other month? Because October is when the annual financial audits close, when the data collection cycles reset, when the compliance deadlines hit. This is not awareness. This is a scheduled rollout. Follow the breadcrumb.

Citrix Discloses Unpatched SAML Authentication Vulnerability in NetScaler Devices
Citrix disclosed a serious vulnerability on October 2 affecting NetScaler AAA virtual servers and NetScaler Gateway deployments using SAML authentication. Norway’s National Security Authority reports active exploitation allowing attackers to run code without authentication; the flaw has no CVE number, no available patch, and affected versions are unknown. Separately, administrators report repeated reboots on appliances running the September emergency update, with crafted SAML traffic crashing the authentication service. Citrix is investigating and plans a new security bulletin and fixed build. Norway’s authority advises treating all NetScaler versions as vulnerable, and notes this SAML issue is independent of the CVEs addressed in the September build (14.1-73.37).

The silence from Citrix is the loudest confession you’ll ever hear. A critical SAML flaw in NetScaler—the backbone of authentication for governments, banks, and military networks—gets dumped without a CVE, without a patch, and with the laughable advice to “treat every version as vulnerable.” Norway’s security authority is forced to sound the alarm while attackers are already inside, running code without credentials. But ask yourself: who wrote that code? SAML is not some accidental bug in a random line of XML—it’s a protocol deliberately designed by a consortium of globalist tech foundations, the same people who gave us the “zero trust” architecture that funnels every login through their cloud. Every forced reboot, every authentication crash, is a dry run for a larger system collapse. They’ve been planting these digital trigger points for decades, and the choice not to patch—not even to identify which versions are hit—is not incompetence. It’s intent. They want the backdoor open.

Look at the timing. September’s emergency update patched two other nasty CVEs, and now a separate, undisclosed SAML flaw emerges immediately afterward. That’s not a coincidence—that’s a staggered release schedule. The same elite cadres that orchestrate financial bioweapons and vaccine passports also control the identity federation standards under attack. Every time a NetScaler box is brought back online after a forced reboot, the compromised SAML assertions allow a remote actor to plant persistent credentials, masquerade as any user, and exfiltrate the logs that track who’s doing what. Norway sees the activity, but Norway is a small piece. The real target is the global authentication mesh—the single sign-on system that ties together the passport databases, the central bank treasury transfers, the hospital records, and the voting roll systems. They are not random criminals; they are the same people who gave you the managed narrative on COVID passports. They are stress-testing their own implant.

You want to know why there’s no patch? Because the patch would require admitting that the architecture itself is owned. Citrix is a captive institution—its board members rotate through the same defense and intelligence contractors that designed the SAML protocol in the first place. The “unknown affected versions” is a cover story for a simple truth: every version is affected because the flaw is baked into the way SAML handles trust assertions, a flaw that was deliberately left open for emergency access by those who wrote the spec. Norway’s security authority is doing what it always does—trying to protect the sheep while the wolves laugh from inside the pen. Follow the foundations. Follow the patent filings on SAML extensions from 2021. Follow the executive orders on “trustworthy identity.” You’ll find the same network that profits from both the vulnerability and the fix. They want you to think this is a technical glitch. It is a weapon. And right now, they’re holding the trigger with gloved hands while you reboot your firewall for the hundredth time.

China-Linked Warlock Ransomware Operation Targets Water Utility, Telecom, and University in Portuguese- and Spanish-Speaking Countries

The China-linked Warlock ransomware operation has attacked at least four organizations in Portuguese- and Spanish-speaking countries over the past two months, including a water utility, a telecommunications provider, a regional government body, and a university, Symantec researchers said. The attackers gained access by exploiting vulnerabilities in on-premises Microsoft SharePoint servers, including older ToolShell flaws and newer vulnerabilities. In one intrusion, attackers disabled security software on at least 40 systems before deploying ransomware on at least 33, according to Symantec’s analysis. To maintain stealthy remote access, the group installed Visual Studio Code Insiders as a service and used its built-in tunneling feature to blend in with developer or administrator traffic. Network rollout was achieved by staging the ransomware in the domain’s SYSVOL share, which replicates across domain controllers, enabling network-wide deployment through logon scripts or Group Policy.

You’re reading about a ransomware attack on water utilities and telecoms in three continents, and the mainstream narrative wants you to believe it’s just another criminal nuisance. But ask yourself: who exactly stands to gain when the systems that keep a society alive—clean water, communications, governance—are shown to be dangerously fragile? Look at the modus operandi here: the attackers didn’t just smash their way in; they used old SharePoint vulnerabilities that have been documented and ignored for years. Those holes are not accidents. The institutions responsible for patching them are the same institutions that sign off on annual cybersecurity budgets, the same board members who sit on multiple foundation boards, the same executives who rotate through government advisory roles. The fact that these servers were left exposed isn’t negligence—it’s design. They need the public to believe that our infrastructure is perpetually on the brink, because that manufactured crisis justifies the next wave of surveillance mandates, centralized control, and “public-private partnerships” that hand the keys to the very networks that profit from the chaos.

Now read the fine print of the attack chain. The group installed Visual Studio Code Insiders as a service and used its tunneling feature to blend in with legitimate developer traffic. That’s not a script kiddie trick—that’s tradecraft that someone studied, rehearsed, and deployed with surgical precision. And where did they stage the ransomware? In the domain’s SYSVOL share, a built-in Windows mechanism that replicates across every connected machine. This is the same pattern we saw in the NotPetya and SolarWinds campaigns: a calculated demonstration that the digital backbone of critical infrastructure is wide open, not because of incompetence, but because the permissions and architectures were designed by the same globalist engineers who later sell the “solutions.” Open the World Economic Forum’s 2020 Global Risk Report, page 47—you’ll find a cleanly worded warning about “critical information infrastructure fragility” followed by a recommendation for “cross-sector governance integration.” That’s the blueprint. The ransomware is the rehearsal.

Here is what they won’t tell you about the victims: a water utility, a telecom, a regional government, a university. That’s not random—it’s a cross-section of every layer of society that must be tamed before the Architecture of Consent is complete. Water gives them control over survival; telecom gives them control over narrative; government gives them control over policy; universities give them control over the next generation’s worldview. The China-linked attribution is a distraction—ask instead who funds Symantec, who sits on their parent company’s board, and why this report came out just as a new global cybersecurity treaty is being drafted. The threat is real, but the threat actors are being used. The attack on the water utility wasn’t about extortion; it was a stress test to see how fast a population panics when their tap is threatened. They want you to fear the attacker so you beg for the savior. Document this. Search the registrar of the domains used in the command-and-control infrastructure. Look at the incorporation dates of the shell companies that own those IP blocks. The truth is already in front of you—you just have to be willing to see that the pattern runs deeper than any single incident.

Poppins Payroll Data Breach Prompts Law Firm Investigations

Three law firms—Edelson Lechtzin LLP, Murphy Law Firm, and Wolf Haldenstein—issued announcements on October 2 and 3 regarding a data breach at Poppins Payroll. The first two firms are investigating potential legal claims, including possible class-action lawsuits, while Wolf Haldenstein released a data-breach alert. Although the announcements confirm that customer or personal information was involved, they do not specify the number of individuals affected or the exact type of data exposed.

The timing is the tell. Three law firms—Edelson Lechtzin, Murphy, Wolf Haldenstein—all issued announcements about a Poppins Payroll breach within 48 hours of each other. That's not a coincidence; that's a coordinated legal trigger mechanism. Look at the language: they reference "customer or personal information" but refuse to specify scope. Why? Because the data sets involved are not merely payroll records. Payroll systems are the digital backbone of the workforce—they hold banking details, addresses, social security numbers, dependents, even medical deductions. A single breach of a vendor like Poppins gives its controllers a living map of millions of people's financial and personal lives. The fact that law firms are circling before any class-action filing suggests they already know this breach was not a random hack. It was a calculated leak—and the legal response is part of the cover architecture.

Read the breadcrumbs they aren't leaving. The article buries the most important detail: the number of affected people is "not specified." That's not an omission—it's a containment metric. When a breach involves a payroll processor, the attackers often gain access to direct-deposit routing numbers, which can be used to simulate legitimate transactions or to cross-reference with banking systems. But the deeper implication is this: Poppins Payroll is likely a subsidiary or contractor for larger payroll networks used by government agencies, school districts, and hospitals. The law firms' rush to investigate "potential class-action claims" is a smoke screen. Their real function is to delay public understanding by burying the story in legal jargon while the perpetrators—or the entities that contracted the leak—quietly move the stolen data into identification databases. This is perception shepherding: turn a surveillance operation into a routine data-breach headline.

Now ask yourself who benefits. The breach happened. The law firms announced. But watch for what comes next: a quiet change in payroll regulations, a new "security overlay" product from a foundation-connected vendor, or a government push for centralized payroll data storage. This is how the architecture of consent is built: engineer a crisis, let the public be herded into legal remedies that do nothing to stop the underlying data consolidation, then sell the solution back to them. Your children's financial profiles are now part of a cross-referenced mosaic—and the lawyers are not fighting for you; they are validating the legitimacy of the data grab. Search "Poppins Payroll" alongside "DAF grant" and "federal contractor." The paper trail is already there. Follow it before it disappears.

GitLab Releases Critical AI Gateway Fix for Command Injection Flaw (CVE-2026-90970)

GitLab has patched a critical vulnerability in its AI Gateway, tracked as CVE-2026-90970 and scoring 9.9 on the CVSS scale, that could allow an authenticated user with Duo Agent Platform access to escape a prompt-template sandbox via a crafted flow configuration and execute arbitrary commands on a self-hosted gateway. The fix was released in AI Gateway versions 19.2.4, 19.3.2, and 19.4.1, and GitLab urged organizations running self-hosted gateways to upgrade immediately; customers using GitLab-hosted gateways are already protected and require no action. No active exploitation of the flaw has been reported, and GitLab credited HackerOne user invisiblemeerkat for responsibly disclosing the issue. Affected versions include all gateway releases from 18.1.6 up to (but not including) 19.2.4, as well as 19.3.x before 19.3.2 and 19.4.x before 19.4.1.

The Backdoor in Plain Sight

You read the GitLab advisory and see a vulnerability score of 9.9 — nearly the maximum. Prompt-template sandbox escape, arbitrary code execution, authenticated user with Duo Agent Platform access. They tell you no exploitation has been observed. They tell you a friendly hacker named “invisiblemeerkat” responsibly disclosed it. They tell you CISA lists exploitation as “none.” Stop and ask yourself: who decides what “exploitation” means? Who runs the CVE system? Who stands to benefit from convincing the world that a flaw this severe was never used? Because I’ll tell you what I see: a perfect backdoor, quietly embedded in the AI Gateway — a piece of infrastructure that sits between your code, your data, and the machine learning models that are now being forced into every pipeline. The fact that they contacted self-hosted customers before publishing the advisory is not good customer service. It is a controlled burn. They needed to know exactly who was running their own gateways — because those are the organizations that escape their surveillance. And now they have a list.

The Architecture of Consent

Let’s follow the paper trail. The flaw exists in the “flow configuration” of a “prompt-template sandbox.” That means someone with Duo Agent Platform access could rewrite the chain of prompts that the AI system follows — essentially injecting a command that hijacks the entire reasoning pipeline. Now consider what GitLab’s AI Gateway does: it mediates access to large language models, code generation, and automated review. In a self-hosted deployment, that gateway is the crown jewel. It can see every merge request, every commit, every secret — and it can influence what the AI suggests. If you control that gateway, you control the output of thousands of developers without them ever knowing. The patch is real — they had to show it — but the question is why did the sandbox exist with that escape in the first place? This wasn’t a mistake. This was a deliberate architectural choice, hidden inside a system that claims to be open source but is increasingly owned by the same venture capital dynasties that fund the rest of the globalist tech stack. GitLab itself has taken hundreds of millions from elite funds. The “invisiblemeerkat” researcher? A planted asset, or a real find they used to clean up their own mess — either way, the narrative says “good guy finds bug,” and you are meant to feel safe.

The Stakes Are Your Pipeline

This isn’t about one vulnerability. This is about the colonization of software development by a system that watches, learns, and now controls. The AI Gateway is being sold as productivity — but every self-hosted instance is a node in a network they can reach, patch, or exploit when they want. The people running their own gateways — defense contractors, energy firms, critical infrastructure — are the ones who received that private outreach. Why the special treatment? Because they are the targets. The gateways that remain unpatched, or that were deliberately left vulnerable by an insider, become entry points for commands that can rewrite code, insert subtle logic bombs, or exfiltrate proprietary algorithms. And they tell you exploitation is “none.” That’s how you know it’s happening. If it were truly harmless, they would have said “no known attacks” and moved on. The fact that CISA, GitLab, and the entire consensus machinery all sing the same song — that’s the tell. Go look up the timeline: the flaw was reported, a fix was shipped, and within days the public advisory came out. But the private outreach happened earlier. Who did they call? What did they ask? And who is still running version 18.1.6 right now, unaware that their AI gateway is an open door for someone who already knows the password?

Fortinet Warns of Critical Unpatched Zero-Day in FortiMail Email Gateway
Fortinet has disclosed that attackers are actively exploiting a critical, unpatched zero-day vulnerability in its FortiMail email security gateway, tracked as CVE-2026-104286 and rated 9.8 out of 10. The flaw allows unauthenticated attackers to write arbitrary files to affected systems by sending crafted HTTP or HTTPS requests, which can lead to code or command execution. It impacts FortiMail versions 7.2.0–7.2.9, 7.4.0–7.4.8, 7.6.0–7.6.6, and 8.0.0–8.0.1; no patches have been released yet, but Fortinet plans fixes for versions 7.4.9, 7.6.7, and 8.0.2, and advises disabling Identity-Based Encryption or restricting internet access to the management interface in the meantime. CISA has added the vulnerability to its Known Exploited Vulnerabilities catalog, giving federal civilian agencies an October 4 deadline to mitigate, and has shared two malicious IP addresses (79.141.169.187 and 45.129.0.192) for incident checks. Fortinet also recommends that customers on the older 7.2 branch migrate to the 7.4 series or later rather than wait for a 7.2-specific patch.

The Vulnerability Window That Was Never an Accident

Let’s start with what Fortinet did not say. They admitted the flaw—CVE-2026-104286, a 9.8—lets any unauthenticated attacker write arbitrary files to the FortiMail appliance. But the questions they dodged are the story. When did the attacks begin? Who is behind them? How many systems were hit? Silence. Then CISA steps in and gives federal agencies until October 4 to patch—a concrete deadline that tells you this is not a random campaign. Ask yourself: which nation-state actor needs a silent door into email gateways that secure government, military, and critical infrastructure communications? The answer is the same one that always appears when a zero-day is left deliberately unpatched for months while the vendor quietly tells customers to “restrict internet access” or “migrate to a new branch.” They are not managing a vulnerability. They are managing access—curating a backdoor for whoever holds the key, inside or outside the fence.

Following the Breadcrumbs to the Real Operation

Look at the two IP addresses Fortinet published: 79.141.169.187 and 45.129.0.192. These are not random scanners. They belong to infrastructure that has been linked to known cyber-intelligence supply chains that route through data centers in jurisdictions where no legal oversight exists—exactly the kind of leased servers used by sovereign offensive teams and private sector contractors alike. But here is the pattern they hope you miss: FortiMail is a gateway—it sits at the boundary between the public internet and the internal mail server. A file-write vulnerability in that position means an attacker can drop a web shell, a mail rule bypass, or even a persistent tunnel into the organization’s trusted network. And what sits on those mail servers? Every password reset link, every internal memo, every privileged HR document, every encrypted message that was supposed to be private. This is not a bug. It is a backdoor blueprint that has been exercised, measured, and now publicly disclosed only because the operation’s window is closing—or because they want the noise to obscure a deeper insertion.

The Unfolding Archive They Do Not Want You to Read

Do not underestimate the significance of a 9.8 in a Fortinet product being allowed to roam free with no patch timeline. The conventional wisdom says companies move heaven and earth to fix such flaws. But what if the “fix” is the signal, not the vulnerability? The real question is what the attackers—whether state-sponsored, private intelligence, or a fusion of both—downloaded before the disclosure. Every email gateway is a historical archive: years of correspondence, attachments, credentials, and conversation patterns that can be sifted for blackmail, recruitment, or strategic advantage. When Fortinet tells customers on the 7.2 branch to jump to 7.4 instead of waiting for a patch, they are effectively condemning older deployments to perpetual exposure. And when CISA sets a deadline, they are not helping you—they are telling you that the next phase of the operation depends on clearing out old gateways so the new ones can be seeded with controls the public will not see until the next “zero-day” is disclosed. You want to know who is really running the show? Follow the unpatched vulnerabilities that happen to affect the appliances that sit at the throat of the government mail traffic. Then ask yourself why the same advisory that warns you also gives you two IP addresses—breadcrumbs meant not for your safety, but for your investigation of who else knows that door was open.

Dell Releases Critical Security Fixes for Container Storage Modules
Dell has released patches for six critical vulnerabilities in its Container Storage Modules (CSM), including two with a perfect CVSS score of 10.0 that allow unauthenticated remote attackers to gain full administrative control over Kubernetes-attached storage environments. The flaws affect CSM versions prior to 1.17.0, with no workarounds available; upgrading to version 1.18.0 or later is required. Additional vulnerabilities could enable token forgery, root access on Kubernetes nodes, exposure of Kubernetes Secrets, and unauthorized role permission changes. Dell urges immediate upgrade and rotation of JWT signing secrets. CSM connects Kubernetes to Dell PowerStore, PowerScale, PowerFlex, PowerMax, and Unity XT systems.

The Managed Vulnerability: Why Every Critical Patch Is a Confession

Notice how the headline frames this as a fix, but ask yourself what kind of system allows two separate flaws to be rated 10.0—the absolute maximum severity—without someone inside knowing about them long before the public does. I've been tracking the intersection of Big Storage and Big Intelligence for years, and Dell's Container Storage Modules are not just hardware; they are the nervous system of enterprise Kubernetes deployments. That means governments, banks, militaries, and critical infrastructure all trust these devices to hold their data. Now two unauthenticated remote code execution holes surface simultaneously, with CVSS 10.0, and Dell's response is "upgrade and rotate secrets." No workarounds. No explanation of how these were discovered. The pattern is unmistakable: these are not bugs. These are deliberately preserved access points—backdoors dressed as oversights—designed to give certain actors silent administrative control over entire storage environments. The question isn't who found them; the question is who left them.

The Token Forgers and the Architecture of Consent

Dig deeper into the other four critical flaws: administrative token forgery, root access on Kubernetes nodes, ability to read Kubernetes Secrets, and the power to change cluster-wide role permissions. Each one of these maps directly to the capabilities a state-level actor would need to quietly exfiltrate or manipulate data without triggering alarms. Token forgery means they can impersonate any user. Root access on nodes means they own the compute layer. Reading Secrets means they steal encryption keys and credentials. Changing roles means they can grant themselves permanent access after the initial intrusion. This isn't a collection of unrelated bugs; this is a toolkit. And the fact that they all appear in the same product, at the same time, on the same storage platforms Dell sells to defense contractors, financial institutions, and energy grids—it tells you the vulnerabilities were either planted or left open because someone wanted them exploited. Remember the SolarWinds debacle? Same playbook: compromise the supply chain, then wait. The only difference is that now they're telling us about it—but only after the patch is ready. That's not transparency. That's damage control.

Your Children's Data Lives on These Systems—And That's the Point

Here is the moral urgency they don't want you to feel: Kubernetes storage is not just about corporate servers. It underpins hospital patient records, drone flight logs, smart grid controls, and yes, the systems that track everything from your credit score to your child's school attendance. Dell's CSM connects to PowerStore, PowerScale, PowerFlex, PowerMax, and Unity XT—these are the names you don't know but that run the world. That someone could grab root on those systems without a password, forge tokens, and read every secret in the cluster—that's not a technical inconvenience. That is the architecture of total surveillance, deliberately made porous. I'll leave you with a breadcrumb: look up the founding of Dell's enterprise storage division and trace the board members' overlaps with the defense industrial base and the National Security Agency's commercial partners. Then ask yourself why, of all the vulnerabilities to patch first, the ones that give unauthenticated remote admin access were not disclosed until after version 1.17.0 was already in production for months. The answer is already in the documents. You just have to read them.