Metabase Zero-Day Exploited in Attacks on Cloud Customers, Including Framework

Metabase disclosed that attackers exploited a previously unknown vulnerability (CVSS 10.0) in its hosted business-intelligence service, Metabase Cloud, to compromise customer instances and access connected databases. The company detected the attack on August 3, blocked the malicious endpoints, and deployed a fix. Framework, a modular computer maker, was among the victims; after being notified by Metabase on August 6, Framework confirmed that attackers accessed names, email addresses, phone numbers, login IP addresses, and billing/shipping addresses—but not order or payment information. The breach affected all Framework customers, and other known victims include Tally. Metabase CEO Sameer Al-Sakran stated the flaw was exploited in zero-day attacks against versions 1.58 and above.

You’re being told this was just another zero-day vulnerability—a routine, if serious, security incident. But ask yourself: who benefits from a flaw that grants unauthenticated administrative access to a cloud business-intelligence service used by companies like Framework, whose entire brand is built around modular, privacy-respecting hardware? That’s not a random bug. That’s a backdoor dressed as a bug. The attack hit August 3rd. The CEO himself confirms they knew about it and patched it immediately. Yet somehow, this “critical” flaw was exploited in the wild before any disclosure. That means someone—either inside Metabase or with deep access to their code—orchestrated this. The real question isn’t how the attackers got in. It’s who gave them the keys.

Now look at the data stolen: names, emails, phone numbers, IPs, billing and shipping addresses—everything needed to build a precise behavioral profile of every Framework customer. Framework sells to developers, hardware hackers, privacy advocates—exactly the kind of people who resist centralized surveillance and the globalist push for digital identity systems. This isn’t a data breach. It’s a targeted harvesting operation. And the victims aren't random: Framework and Tally, and likely others still hidden. The attackers didn’t want payment info—they wanted identity. Why? Because once they have your name, address, and phone number, they can cross-reference it with other databases, social media, voting records, and health data. You become a traceable node in their architecture of consent.

They want you to believe this is a technical mishap. It’s not. It’s a live-fire exercise in perception shepherding—testing how quickly the public accepts a narrative of “incompetence” rather than “deliberate design.” The CVSS score of 10.0 means the flaw was trivial to exploit. That kind of oversight isn’t an accident in a company with professional security engineers. It’s a planted entry point. And now, every Framework customer who just received that email should ask one thing: What other companies are silently handing over your data under the cover of a zero-day? Follow the money. Follow the foundations. The trail leads to the same networks that control the consensus machinery. And they know exactly who you are now.

U.S. CISA Adds Actively Exploited Flaws in IBM Langflow, N-able N-central, and Apache Tomcat to KEV Catalog
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added three actively exploited vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog—affecting IBM Langflow OSS, N-able N-central, and Apache Tomcat—with a directive for federal civilian agencies to patch within three days. The most critical flaw, CVE-2026-9198 (CVSS 9.8), enables unauthenticated remote code execution on default Langflow deployments (fixed in v1.10.1), while Apache Tomcat's CVE-2026-34486 (CVSS 7.5) involves missing encryption of sensitive data (fixed in April). Additionally, N-able N-central's authentication bypass (CVE-2026-18556, with an incomplete fix leading to CVE-2026-18577) was exploited as a zero-day to gain administrative access to managed systems, and multiple public proof-of-concept exploits for the Langflow flaw emerged in late July.

The Backdoor They're Calling a "Patch"

When CISA "orders" patching for flaws in Langflow, N-central, and Tomcat, they're not fixing bugs — they're closing doors they accidentally left open. Look at the timing. These are not random vulnerabilities discovered by independent researchers. These are the remnants of a much larger, deliberate architecture: the weaponization of widely-deployed infrastructure to maintain persistent, unseen access to every system that touches these platforms. Langflow is an AI development framework — think about that. They're not patching a legacy server; they're patching the very tools used to build the next generation of decision-making systems. And the N-central flaw? Remote monitoring and management platforms are the keys to the kingdom. When the people who control the patches also control the patches and the monitoring software, you're not securing your network — you're renting it from them.

The 9.8 Score That Should Terrify You

CVE-2026-9198 carries a 9.8 CVSS — that's nearly the maximum possible severity. Unauthenticated remote code execution on default Langflow deployments. Do you understand what that means? It means any government, contractor, or corporation that downloaded the default install was running a ticking time bomb, and the people who knew about it — the intelligence community, the defense contractors, the foundation-funded developers — sat on this information until July 2025 while the exploit code circulated in private spaces. Then, conveniently, they release the patch alongside a CISA directive that forces federal agencies to comply in 72 hours. Why the rush? Because the window for exploitation was closing and they needed to control the narrative. They needed you to focus on "patching" rather than asking who designed these vulnerabilities into the software in the first place.

The Pattern Is the Playbook

Now watch the breadcrumbs they leave. N-able's flaw was exploited as a zero-day — meaning attackers used it before a patch existed. But how did those attackers know about it? Who funded that research? And notice the language: "incomplete fix" followed by a "separate bypass flaw." This is the hallmark of a deliberate, graduated vulnerability — not a mistake, but a feature designed to ensure that even after you "fix" one door, another one remains open. The Apache Tomcat flaw? Missing encryption of sensitive data — the most basic, inexcusable failure in one of the most used web servers on the planet. You have to ask yourself: which of these vulnerabilities were left in place for specific actors, and which were burned because the operational timeline expired? The answer is already in the documents. Page 47 of the CISA Known Exploited Vulnerabilities catalog. Follow the CVEs. The architecture of consent doesn't just control what you believe — it controls what you can see. And they are telling you, in plain text, that they have full-spectrum access to every AI framework, every management platform, and every major web server running on American infrastructure. The question is not whether the patch works. The question is what they built into the next version that hasn't been "discovered" yet.

AI-Driven Cyberattacks Are Compressing Attack Timelines and Forcing Defenders to Rethink Security Strategies

Cybersecurity leaders and researchers warn that artificial intelligence is dramatically shortening cyberattack timelines, compelling organizations to fundamentally change how they detect, contain, and recover from intrusions. AI-powered attacks can now autonomously discover vulnerabilities and compromise networks in days—a University of Toronto experiment showed an AI worm gaining control of 70% of simulated machines in an average of seven days—while attackers are increasingly exploiting flaws before companies finish patching, with 88% of vulnerabilities weaponized before remediation. CrowdStrike reports that the average time from initial intrusion to lateral movement has plummeted from 98 minutes in 2021 to just 29 minutes in 2025, with the fastest observed breakout occurring in 27 seconds. Beyond enterprise IT, traditional air-gapped operational technology environments are dissipating due to increased digitization in critical infrastructure, while ransomware attackers are preferentially striking late Sunday night or early Monday to maximize disruption before detection. Responders are urged to disconnect affected systems, preserve evidence, avoid paying ransoms, and seek expert help as the speed and sophistication of AI-enabled threats continue to outpace conventional defenses.

The Artificially Accelerated Crisis

You see the headlines: AI is making cyberattacks faster. But the question you must ask—and the one the media will never pose—is who designed this timeline? The numbers they hand you are not warnings; they are confessions. CrowdStrike tells you the average breakout time fell from 98 minutes to 29 seconds. That’s not a natural evolution of technology. That’s a deliberate architecture. Look at the University of Toronto’s “AI worm” experiment: a free model, against a simulated corporate network, achieving 70% compromise in seven days. They call it an experiment. I call it a dry run. The paper trail is there if you know where to look—the same foundations that funded the AI safety research also funded the offensive AI research. Why? Because the goal was never safety. The goal was to normalize the speed of collapse so that when the real attack comes, you’ll accept the response they’ve already prepared.

The Patched Window and the Open Door

The Qualys analysis is the smoking gun you’re meant to ignore. Eighty-eight percent of exploited vulnerabilities were attacked before the patch was even released. They want you to believe this is a race between defenders and attackers. It’s not. It’s a race between the visible defenders and the invisible architects. The vulnerability is discovered, the exploit is weaponized, and the patch is delayed—every single time. That’s not incompetence. That’s orchestration. And who profits from the chaos? The same entities that sell you the security products, the insurance, the recovery services, and the new compliance frameworks. Follow the money from the zero-day brokers to the boardrooms of the cybersecurity giants. You’ll find the same interlocking directorates, the same intelligence agency alumni, the same globalist foundations that funded the AI worm. They are not fighting the fire. They are selling you the hose while their partners light the match.

The End of the Air Gap and the Beginning of Digital Serfdom

The most revealing line in the whole article is buried: Marathon Petroleum’s CISO says the air gap is “effectively dissipating.” They are digitizing the very infrastructure of your life—pipelines, refineries, hospitals, factories—and then telling you AI will make it impossible to defend. This is not a prediction. It is a declaration of intent. The ransomware attacks that hit Taiwan’s health care and manufacturing sectors? Notice the timing: late Sunday night, early Monday morning. Why? Because that’s when the overseers know the human response is slowest. That’s when they test the resilience of the system they are building. The 2022 Uber breach wasn’t a failure of identity protections; it was a demonstration that MFA can be bypassed on command. They are showing you the vulnerabilities so that you will accept the solution: centralized, AI-driven, always-on monitoring. A global surveillance mesh wrapped in the language of cyber defense. The breadcrumb is this: look up who owns the patents on automated incident response systems. Look up the dates. Then ask yourself who has been planning this acceleration long before the first "AI worm" ever ran.