This week’s urgent stories look unrelated: government files on a leak site, an exploited VPN gateway, a browser zero-day, an AI-assisted intrusion, fraudulent bank transfers, and a PostgreSQL privilege boundary. The common problem is inherited trust.
Attackers do not need to break every control when they can take over a system, credential, certificate, or process that the next control already accepts.
TL;DR
- Berlin: published stolen data creates new credential, impersonation, and safety risks after network containment.
- SonicWall: patch SMA1000 appliances, then assess compromise; rebuild and reset credentials if indicators are found.
- Chrome: deploy the CVE-2026-85046 fix and prove browsers restarted into the fixed build.
- AI-assisted intrusion: automation compressed a multi-control-plane attack into under ten hours, according to Unit 42.
- BREEZE COMET and PostGREShell: trusted payment identities and replication roles can cross into financial fraud or host code execution.
1. Berlin: The Data Has Left the Network
Berlin says stolen administration data was published after the Rhysida extortion deadline expired. The group claimed 5.7 terabytes, but the state was still examining the dataset and had not verified a complete inventory.
The priority is to find reusable trust inside the exposed material: passwords, tokens, certificates, internal contacts, supplier relationships, network details, and authentic context for phishing. Revoke secrets and sessions before waiting for a perfect victim list. Notify people according to credible harm rather than sending one generic message to everyone.
Decision: Who owns the exposure inventory, and can that team trigger credential rotation without waiting for the entire archive to be classified?
2. SonicWall: An Edge Patch With an Incident-Response Clause
SonicWall confirmed active exploitation of CVE-2026-83548 and CVE-2026-83549 in SMA1000 appliances. The flaws combine a pre-authentication SSRF path with post-authentication command injection. Fixed hotfix builds are 12.4.3-03526 and 12.5.0-02952.
CISA added both CVEs to its Known Exploited Vulnerabilities catalog on September 2, according to the Canadian Centre for Cyber Security’s updated advisory.
The vendor tells customers to review for indicators of compromise. If found, it recommends re-imaging or redeploying the appliance, changing user and administrator passwords, and resetting TOTP tokens. That language should keep the ticket out of the routine patch queue.
Decision: Can you prove every SMA1000 instance, including standby systems, is fixed and reconcile its recent administrative and remote-access activity?
3. Chrome: Installed Is Not Running
Google says an exploit for CVE-2026-85046, a V8 type-confusion vulnerability, exists in the wild. Desktop Chrome 152.0.7977.82/.83 contains the fix.
Fleet reporting must distinguish an downloaded package from a running process. Long-lived browser sessions, unmanaged devices, virtual desktops, and other Chromium-based browsers create the gap between deployment percentage and actual exposure.
Decision: What percentage of endpoints is running the fixed browser process, and which users still reach company data from browsers outside management?
4. AI-Assisted Intrusion: Detection Windows Are Shrinking
Unit 42 reports that a human attacker used AI agents to move from a public API endpoint across source code, secrets, cloud, identity, CI/CD, containers, SaaS, and AI infrastructure in less than ten hours. The operation used familiar weaknesses rather than a new zero-day.
The public evidence supports AI-assisted acceleration, although the exact models and division of human-versus-agent decisions were not disclosed. The practical lesson survives that uncertainty: separate alert queues for cloud, identity, source control, and endpoints cannot contain a chain that crosses all four before a shift changes.
Decision: Can one responder revoke an identity’s sessions, cloud tokens, repository access, pipeline credentials, and endpoint access through a coordinated procedure?
5. BREEZE COMET: Valid Payments Can Still Be Fraudulent
Mandiant describes BREEZE COMET compromising Brazilian organizations that can issue transactions through Pix, STR, boleto, and related banking systems. The actor seeks directory and cloud accounts, mTLS credentials, segmented network access, and knowledge of payment procedures.
Once a trusted application sends a malicious request with valid credentials, authentication alone has done its job and still failed the business. Transaction monitoring must bind the payment to workload, operator, beneficiary, device, velocity, and change history.
Decision: Can the same technical identity define a beneficiary, request authorization, and submit a high-value payment without independent approval?
6. PostGREShell: A Database Role Crosses Into the Host
CVE-2026-6471 lets a PostgreSQL role with REPLICATION privilege cause the server to load an arbitrary visible logical-decoding library. Code then runs as the PostgreSQL operating-system account. Supported fixed versions are 18.6, 17.11, 16.15, 15.19, and 14.24.
PostgreSQL rates the flaw CVSS 7.2. It is not an unauthenticated internet RCE, and current public evidence does not establish active exploitation. Patch it, minimize replication roles, restrict their source networks, and allowlist required output plugins.
Decision: Can every replication-capable role be tied to an owner, expected client, network path, and recent legitimate use?
The Week’s Defensive Queue
Prioritize observed exploitation and irreversible exposure first. Each item needs an owner and a closure condition; “team notified” is neither.
| Priority and owner | Do this | Because | Close only when |
|---|---|---|---|
| 1 — Network and IR | Patch every SMA1000 instance, preserve pre-patch evidence, and investigate access from appliance management addresses and VPN pools. | Both CVEs are in CISA KEV. Patching stops new exploitation but cannot remove prior access or copied credentials. | Every instance runs the fixed full build, historical privileged activity is explained, and compromised trust has been reset. |
| 2 — Endpoint engineering | Deploy the Chrome fix, enforce relaunch, and inventory other Chromium-based products separately. | The vulnerable process can remain alive after the update downloads, and another unmanaged browser can preserve exposure. | No in-scope endpoint is running a vendor-identified vulnerable browser process. |
| 3 — IAM and privacy | Turn the Berlin exposure inventory into secret revocation, session invalidation, harm-based notification, and monitoring for impersonation. | Published information can drive new attacks after the original intruder is gone. Accurate internal context makes credential reuse and phishing harder to distinguish from normal access. | Old secrets and sessions fail, high-risk people have a case owner, and reuse detections have passed controlled tests. |
| 4 — SOC and platform teams | Correlate API, repository, secrets, token, pipeline, cloud, and SaaS activity by identity inside a short window. Prepare a cross-domain kill switch. | AI-assisted execution converts separate low-confidence alerts into a completed intrusion before serial escalation finishes. | A purple-team sequence produces one ordered incident and the kill switch revokes access across every control plane within the target time. |
| 5 — Payment security | Separate beneficiary creation, transaction approval, signing, and release; bind certificates to expected workloads and detect abnormal transaction context. | BREEZE COMET can use valid technical identities. Authentication alone cannot tell whether a trusted application is submitting an unauthorized payment. | One test identity cannot complete the full transaction chain, and an anomalous batch is held before settlement. |
| 6 — Database and network teams | Upgrade PostgreSQL, minimize replication roles, allowlist output plugins, and restrict replication sources and database-host egress. | PostGREShell requires replication privilege and a loadable library path. Each restriction removes part of that prerequisite chain. | The fixed version is running, approved replication passes, and an unapproved role, source, plugin, and outbound destination all fail. |
The shared lesson is not “patch faster,” although several teams must. It is to know where trust accumulates and how to revoke it quickly. A gateway, browser session, build identity, payment certificate, or replication role becomes dangerous when the environment keeps accepting it after its original assumptions have failed.
This Week’s Deep Dives
- Rhysida Published Berlin’s Stolen Data. The Incident Is Only Starting
- SonicWall SMA1000 Zero-Day Chain: Patch It, Then Assume It Was Breached
- Chrome CVE-2026-85046: Updating Is Easy. Proving Every Browser Updated Is Not
- AI Compressed an Enterprise Intrusion Into Ten Hours. Speed Was the Weapon
- BREEZE COMET Did Not Steal Card Numbers. It Manipulated the Payment System
- PostGREShell CVE-2026-6471: When Replication Privilege Becomes Server Code Execution
Sources
- State of Berlin - Published Data: State Plans to Contact Those Affected
- SonicWall - SMA1000 Multiple Vulnerabilities, SNWLID-2026-0016
- Canadian Centre for Cyber Security - SonicWall Security Advisory AV26-872, Update 1
- Google Chrome Releases - Stable Channel Update for Desktop, September 3, 2026
- Unit 42 - An AI-Assisted Cyber Attack: Inside a Unit 42 Investigation
- Google Threat Intelligence Group and Mandiant - BREEZE COMET Targets Brazil
- PostgreSQL - CVE-2026-6471 Security Advisory