Metabase CVSS 10.0 zero-day: unauthenticated SQL injection in the password-reset endpoint stole admin access and credentials for every connected database, no CVE assigned      OpenAI GPT-5.6-Cyber: purpose-trained offensive AI that completes 95% of exploit-development requests found two Chrome V8 zero-days now patched as CVE-2026-15903      Black Hat webmail chains: Outlook, Yahoo, Gmail, and Cowork sessions hijacked through CSS mutation bugs and paste races, live auth tokens exfiltrated with no malware      Metabase CVSS 10.0 zero-day: unauthenticated SQL injection in the password-reset endpoint stole admin access and credentials for every connected database, no CVE assigned      OpenAI GPT-5.6-Cyber: purpose-trained offensive AI that completes 95% of exploit-development requests found two Chrome V8 zero-days now patched as CVE-2026-15903      Black Hat webmail chains: Outlook, Yahoo, Gmail, and Cowork sessions hijacked through CSS mutation bugs and paste races, live auth tokens exfiltrated with no malware     
CyberSipTM
Intelligence without the noise
Issue No. 105
August 11, 2026
3 items · past 24h
<5 min read
Today's picture

A CVSS 10.0 zero-day in Metabase's password-reset API endpoint was actively exploited starting August 3, giving unauthenticated attackers full administrator access and the credentials for every database connected to compromised instances before Metabase knew the flaw existed. No CVE has been assigned, meaning scanners relying on NVD feeds will not flag exposed self-hosted deployments. OpenAI launched GPT-5.6-Cyber today through its Daybreak Red program, a purpose-trained offensive security model that completes 95 percent of advanced exploit-development requests that the standard guardrailed model handles at a rate of 1.5 percent, and disclosed that the model found a two-vulnerability Chrome V8 heap sandbox escape chain now tracked as CVE-2026-15903. And PortSwigger researcher Gareth Heyes presented three working webmail injection chains at Black Hat 2026 that steal live authentication tokens from active Outlook, Yahoo, Gmail, and Cowork sessions by combining CSS mutation bugs, paste races, and prompt injection, with public proofs of concept available as of August 8.

Today's intelligence
3 items
01 CriticalMetabaseZero-Day
A CVSS 10.0 Metabase zero-day gave unauthenticated attackers admin access and the credentials for every connected database before a patch existed
The flaw sits in the password-reset endpoint. No account required. An attacker who reached it could inject arbitrary SQL, escalate to administrator, reconfigure the application, and export stored credentials for every database Metabase had connected. Downstream victims include n8n, Framework, and Tally. No CVE has been assigned, which matters operationally.
Tracked asGHSA-vwf4-m7j8-wcjf
No CVE assigned
CVSS10.0 (maximum)
Exploited sinceAugust 3, 2026
(zero-day)
AffectedVersions 0.58
through 0.63
(self-hosted and
Cloud)
Known victimsn8n, Framework
Tally
Metabase disclosed on August 8, 2026 that its Cloud infrastructure was attacked starting around August 3 using a previously unknown vulnerability in versions 1.58 and above, spanning branches 0.58 through 0.63 of both the open-source and commercial editions. The vulnerability is an unauthenticated SQL injection in the publicly accessible POST /api/session/reset_password endpoint. A remote attacker with no account and no prior access can send a crafted request to that endpoint, inject arbitrary SQL commands into the Metabase application database, and escalate to administrator privileges. From that position, the attacker can alter application configuration, steal the stored credentials for every database connected to the Metabase instance, read any data accessible through those connections, and export data. Metabase blocked the affected endpoints immediately upon detecting the attack, identified the root cause, patched Cloud instances, and engaged a third-party forensics firm. Self-hosted users on affected versions must update manually. The vulnerability has been assigned a CVSS score of 10.0 by Metabase and tracked under GHSA-vwf4-m7j8-wcjf in the GitHub Advisory Database. No CVE identifier had been assigned as of August 11. Downstream impact is confirmed: n8n, a workflow automation platform, disclosed on August 8 that an attacker accessed 136 customer records including names, email addresses, and five bcrypt-hashed password hashes by exploiting the Metabase vulnerability against n8n's own analytics environment. Framework and Tally separately confirmed data access affecting customer information. Metabase's prior zero-day history is relevant context: CVE-2023-38646, a CVSS 9.8 pre-authentication remote code execution flaw, was disclosed in 2023 and exploited in the wild before organizations could patch.
Metabase sits at the center of many organizations' data infrastructure as the analytical layer connecting to production databases, data warehouses, and external services. Stored within a Metabase instance are the database credentials for every source it queries. An attacker who reaches administrator access in Metabase does not have access to Metabase's data alone. They have the credentials to reach every system Metabase was authorized to query. The blast radius of this attack scales directly with how broadly the compromised instance was connected. The absence of a CVE identifier creates a specific operational gap: vulnerability scanners, SIEM rules, and patch management systems that track CVE numbers will not surface this flaw unless they also ingest GitHub Security Advisories or Metabase's own advisory feed.
The no-CVE situation is not unusual for software that uses GitHub's advisory database as its primary disclosure mechanism, but it creates a real gap between the actual risk and what automated tooling reports. Any organization running Metabase should treat GHSA-vwf4-m7j8-wcjf with the same urgency as a named CVE carrying a CVSS 10.0, because it is one. Metabase Cloud instances were patched automatically. Self-hosted instances on any version in the 0.58 through 0.63 range require a manual update to the latest release. The Metabase team published the specific patched version string in its advisory. If a self-hosted instance was accessible over the internet during the August 3 to August 8 window, treat it as potentially compromised and rotate the credentials for every database it was connected to before investigating further.
  • Update all self-hosted Metabase instances to the latest patched version immediately. Check Metabase's August 2026 advisory for the specific version string. Metabase Cloud instances were patched automatically and require no action from administrators.
  • Rotate the database credentials stored in every Metabase connection that was active on an affected instance during the August 3 to August 8 window. Administrator access to Metabase gives an attacker direct read access to those credentials. Rotating them closes the downstream access path even if the Metabase instance has been patched.
  • Add GHSA-vwf4-m7j8-wcjf to your vulnerability tracking and monitoring tools manually if they do not ingest GitHub Security Advisories. CVE-based scanners alone will not surface this flaw, and the no-CVE gap is exploitable by any actor who knows the advisory exists.
No account. No CVE. One endpoint. Admin access to the analytics platform and credentials for every database it touched. Patch the Metabase instance, then rotate the credentials for every system it was connected to. Do not wait for a CVE number to appear before treating this as urgent.
02 HighOpenAI DaybreakAI Offensive
OpenAI launched a purpose-trained offensive AI model today that completed 95 percent of advanced exploit-development requests and found two Chrome zero-days
GPT-5.6-Cyber is available only through Daybreak Red, OpenAI's vetted access program requiring identity verification and legal attestations. The standard guardrailed model completes 1.5 percent of the same requests. The Chrome V8 chain it found was disclosed to Google and is now patched. OpenAI also disclosed the model found over 400 kernel privilege-escalation flaws.
ModelGPT-5.6-Cyber
(based on GPT-5.6 Sol)
AccessDaybreak Red only
Identity verified
Legal attestation
Chrome CVECVE-2026-15903
(V8 heap sandbox
escape chain, patched)
Capability ratingHigh (OpenAI
Preparedness
Framework)
OpenAI launched GPT-5.6-Cyber on August 10, 2026, through its expanded Daybreak cybersecurity program and published the announcement on August 11. The model is a fine-tuned version of GPT-5.6 Sol, specifically trained to improve performance on advanced cybersecurity tasks including zero-day vulnerability discovery, exploit chain development, authentication bypass research, and privilege escalation. Access requires identity verification, hardware security key enrollment from September 1, 2026, legal attestations about intended use, and placement in the Daybreak Red tier of the program. Daybreak Blue, the lower tier, gives approved defenders access to standard models with defensive-focused safety adjustments for tasks including secure code review, malware analysis, and incident response. OpenAI built an internal benchmark measuring model agreement rates on higher-risk dual-use security requests. GPT-5.6-Cyber completed 95 percent of those requests. The standard, fully guardrailed GPT-5.6 Sol completed 1.5 percent. Its predecessor GPT-5.5-Cyber completed 57 percent. In its announcement, OpenAI disclosed two real-world findings produced by the model. The first is CVE-2026-15903, a high-severity vulnerability in Chrome's V8 JavaScript engine where the optimizing compiler incorrectly skipped a safety check during integer-to-value conversion, allowing an array index to be treated as in-bounds when it is not, enabling out-of-bounds memory access inside Chrome's sandbox. GPT-5.6-Cyber found this flaw and also found the second vulnerability necessary to escape the V8 heap sandbox, completing a full two-step code execution chain. Both were disclosed to Google through coordinated disclosure and are now patched. OpenAI also disclosed the model identified five vulnerabilities in a major mobile operating system including a privilege escalation chain from untrusted applications, three critical remote code execution issues in a widely used database, and over 400 privilege-escalation flaws in a popular OS kernel. OpenAI rated GPT-5.6-Cyber as High under its Preparedness Framework, below the Critical threshold, and confirmed the model was not involved in the prior Hugging Face security incident.
The capability delta between the standard guardrailed model and the purpose-trained offensive model is the most significant figure in this announcement: 1.5 percent versus 95 percent completion on advanced exploit-development requests. That gap represents the difference between a model that can assist with security workflows and a model specifically engineered to conduct them. OpenAI's framing is that this capability should be in the hands of trusted defenders before attackers build equivalent systems. The practical reality is that the same capability threshold has already been reached by actors using accessible models through the Hermes Agent framework, as documented in Issue 102. The question OpenAI is implicitly answering is whether the defense side should have purpose-built access to offensive AI capability, or whether restricting it to safety-oriented models leaves defenders structurally outmatched.
OpenAI's announcement includes a detail that did not receive prominent coverage: GPT-5.6-Cyber underperformed GPT-5.6 Sol on vulnerability report writing, which OpenAI attributes to a tendency toward shorter responses. That tradeoff reveals something structurally important about how capability specialization works at this level. Tuning a model for offensive task completion apparently degrades its ability to communicate findings clearly. A model that is better at finding vulnerabilities but worse at writing the reports that make those findings actionable to human teams is not an unambiguous improvement for defensive security workflows. Organizations evaluating AI for security research should assess both the discovery capability and the communication quality before assuming that a higher task completion rate translates directly to better security outcomes.
  • Organizations with dedicated offensive security research programs should evaluate whether Daybreak Red access is appropriate for their workflows. The access requirements are substantive: identity verification, legal attestations, hardware security keys, and a defined use case. OpenAI's application process is on its Daybreak program page.
  • Security teams that use AI for code review, vulnerability scanning, or red-team assistance should note that Daybreak Blue covers defensive workflows with safety adjustments. The two tiers are intentionally separated, and the defensive tier does not require the same access controls as Daybreak Red.
The standard model handles 1.5 percent of advanced exploit requests. This one handles 95 percent. It found two Chrome zero-days and over 400 kernel privilege-escalation flaws before launch. OpenAI's argument is that defenders need this before attackers build the equivalent themselves. That argument arrived the same week that a Chinese actor demonstrated they already did.
03 HighWebmailBlack Hat
Three Black Hat webmail injection chains steal live authentication tokens from Outlook, Yahoo, Gmail, and Cowork with no malware installed
Gareth Heyes of PortSwigger presented chains that combine CSS mutation bugs, paste races, and prompt injection to take over active sessions. No phishing link required for two of the three. The Cowork chain exploits a Slack token after prompt injection. Public proofs of concept have been available since August 8.
ResearcherGareth Heyes
PortSwigger
PresentedBlack Hat USA 2026
TargetsOutlook, Firefox
Yahoo, AOL
Gmail, Cowork
PoC statusPublic since
August 8, 2026
FastmailFixed CSS mutation
bugs before disclosure
Gareth Heyes of PortSwigger Web Security Academy presented three webmail injection attack chains at Black Hat USA 2026, each targeting a different combination of webmail providers and browser environments. All three steal live authentication tokens from active user sessions without installing any software on the victim's machine. The first chain targets Outlook Web Access combined with the Firefox browser. It exploits a CSS mutation bug in how Firefox parses and normalizes certain CSS syntax to spoof a convincing Microsoft sign-in screen inside the victim's browser, capturing the password the user types into what appears to be a legitimate prompt. The second chain targets Yahoo Mail and AOL Mail and uses a paste race technique: the attacker crafts a payload that activates when a user pastes content into a message compose window, racing a malicious clipboard write against the paste event to inject attacker-controlled content into the email body. This chain can expose a Medium email-login token and allow the attacker to sign in as the victim. The third chain targets Gmail combined with Claude Code, referred to by Heyes as Cowork in the presentation. It uses prompt injection delivered through content the victim's browser renders to steal a Slack authentication token from the active session, requiring some user interaction but no installed software. All three chains were part of a coordinated disclosure process. Fastmail fixed two of the CSS mutation bugs before the presentation. The Proton Mail proxy bypass that Heyes documented stopped working before re-testing. Public proofs of concept for the remaining chains were available as of August 8. The researcher described the work as proof-of-concept research with no confirmed malicious exploitation at the time of the Black Hat presentation.
All three chains steal authentication tokens from active sessions rather than passwords, which means rotating a password after discovering one of these attacks does not remove the attacker's access. A stolen session token is valid until it expires or is explicitly revoked. The chains also operate entirely within the browser and the webmail application: no malware, no endpoint compromise, no persistence required. This class of attack is specifically difficult for endpoint detection and response tools to catch because the entire attack surface is the browser rendering web content, which is normal behavior. The Cowork chain is additionally notable because it demonstrates that AI-assisted coding environments with browser access create new token theft surfaces that did not exist before those products were deployed.
The research builds on a class of attack that has been maturing throughout 2025 and 2026. CSS injection as a side channel for data exfiltration has been documented in academic research for years. What Heyes demonstrated at Black Hat is that CSS mutation bugs in production browser implementations can be combined with social engineering and prompt injection into complete session-takeover chains against major webmail providers. The paste race technique is separately interesting because it targets a browser behavior rather than an application vulnerability: the attacker races a script against a user's clipboard paste event, which is a generic browser API that all webmail providers expose. Fixing the specific Outlook or Yahoo implementation does not eliminate the race condition surface in the browser itself.
  • For Outlook Web Access users on Firefox, verify that the Firefox version in use has received any patches addressing the CSS mutation bug disclosed by Heyes. Browser vendors typically ship security patches within days of a Black Hat presentation, but enterprise-managed Firefox deployments may lag behind if update cycles are controlled through group policy.
  • Security teams operating Gmail, Outlook, or similar webmail environments in enterprises should review their session token lifetime policies. Shorter token lifetimes reduce the window during which a stolen token remains useful. Enforcing token revocation on logout rather than allowing tokens to persist through browser sessions limits the attack surface for any session-hijacking technique.
  • Organizations using Cowork or similar AI-assisted browser agents should treat the Slack token theft chain as a live risk and audit whether those environments have access to authentication tokens for connected services. AI coding assistants with browser access and connected workspace integrations create token aggregation points that did not exist in prior threat models.
No malware. No phishing link for two of the three chains. Just the browser rendering web content and a CSS bug, a paste race, or a prompt injection. The result in all three cases is a live authentication token. Rotate the password after discovery and the attacker keeps access until the token expires.
Cross-source standouts
01
Metabase and the BI platform as a credential aggregator: why analytics tools carry a blast radius far beyond their own data
Business intelligence platforms are designed to be the analytical layer that connects to everything else. To do that job, they store credentials: database passwords, API keys, service account tokens, and connection strings for every source they query. A Metabase instance connected to a production PostgreSQL database, a Redshift warehouse, a Salesforce CRM, and a Stripe account holds the keys to all four. An attacker who gains administrator access to Metabase does not have access to Metabase's internal data. They have access to the authentication material that unlocks four separate production systems. This is the same structural property that makes RMM platforms like N-central (Issue 100) and CI/CD systems like TeamCity (Issue 102) such high-value targets: they are designed to aggregate access to many systems, which means compromising one gives access to many. Any tool that is authorized to connect to multiple production systems on behalf of the organization is by definition a higher-value target than any of the systems it connects to individually. Security reviews of data access should account for this: the BI platform is not just an analytics tool. It is a credential store for the production environment, and it should be secured accordingly.
02
GPT-5.6-Cyber, the DeepSeek campaign, and the arms race dynamic now visible in the same week
Issue 102 documented a Chinese-speaking actor using DeepSeek through the Hermes Agent framework to run an autonomous adaptive hacking campaign that breached 107 endpoints using publicly available exploit code and an open-source agent framework. Issue 105 documents OpenAI releasing a purpose-trained offensive AI model that found two Chrome zero-days and completed 95 percent of advanced exploit-development requests. Both events happened within the same week. OpenAI's framing for GPT-5.6-Cyber is explicit: defenders need access to this capability before attackers develop the equivalent. The DeepSeek campaign is evidence that motivated actors with available models and open-source tooling are already past the threshold where AI meaningfully accelerates offensive operations. The question the Daybreak Red announcement is implicitly trying to answer is whether gating powerful offensive AI behind identity verification and legal attestations creates a meaningful asymmetry in favor of defenders, or whether the underlying capability is already accessible enough that the gate mostly inconveniences legitimate security researchers. The answer is not settled, and the evidence from this week points in different directions simultaneously.
Still watching
Days 2–5
Progress LoadMaster CVE-2026-8037 (Issue 104 · CISA KEV, deadline passed August 10) — confirmed exploited over six weeks from 65 IPs. Update to GA 7.2.63.2 or LTSF 7.2.54.18. Follow CISA forensics triage guidance and review /accessv2 endpoint logs from June 29 onward. Deadline passed yesterday.
Day 2
WEL1DROPPER npm campaign (Issue 104 · ~800 packages, August 6 to 7) — cross-platform RAT and infostealer with DNS TXT fallback through wel1.ru. Audit lockfiles and build caches against Manifold's package list. Hunt DNS logs for TXT queries to wel1.ru subdomains. Removing the package starts the investigation; it does not end it.
Day 3
US water campaign, 12 states (Issue 103 · Iranian attribution preliminary) — investigation ongoing. Review CISA AA26-097A and CI Fortify guidance. Report any anomalous OT activity to the FBI and CISA. No public attribution confirmed as of today.
Day 5
LegacyHive (Issue 88 · Nightmare Eclipse, no patch) — Windows User Profile Service privilege escalation with working proof of concept on fully patched systems. No CVE, no fix. Now at Day 24. Three prior disclosures in this series were exploited before patches arrived.
Day 7+