If you run NetScaler with SAML authentication configured, patch it before Saturday. CVE-2026-8452 has been public since June 30, and a June triage would have filed it as a reboot risk, not a breach risk. Citrix described it as "a high-severity memory overflow that can lead to unpredictable or erroneous behavior and DoS attacks," and said it had "not observed any unmitigated exploitation of this vulnerability." NVD's description still characterizes the impact as "Denial of Service." That framing was wrong, and the correction arrived as working exploit code.

On August 14, watchTowr published details and a proof of concept showing the bug yields unauthenticated remote code execution as root, per SecurityWeek. Exploitation followed within days. The Hacker News reports attackers "dropping a web shell named 'x.php' and 'z.php,' and running discovery commands, like 'id' and 'echo,'" with 36 exploitation attempts over 12 days from 12 unique attacker IP addresses. CISA added the CVE to KEV on August 26 with a federal deadline of Saturday, August 29 — the shortest tier under BOD 26-04, which #010 covered.

The scoring gap is worth seeing directly. Citrix assigned CVSS v4.0 8.8. NVD assigned v3.1 9.8 as the primary score. KEV's own one-line summary still says the bug "could lead to denial of service" — the catalog inherited the vendor's framing even while listing it as exploited. A severity number is an input to your triage, not a verdict.

Get the scope right, because the usual shorthand is too broad. NVD says the appliance must be "configured as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server." Bishop Fox narrows it: "SAML configuration is what puts an appliance in scope, rather than the presence of a Gateway or AAA virtual server on its own." The bug lives in XML signature canonicalization, where the PrefixList field is "copied into a buffer of fixed size without first checking that the value fits." A Gateway vserver with no SAML role is not the target; a SAML service provider or an IdP configured via samlIdPProfile is.

Scale: Shadowserver tracked over 22,000 exposed NetScaler ADC appliances and nearly 1,800 Gateway instances online, patching status unknown, per BleepingComputer.

What to do this week:

1. Patch to a fixed build, then go past it. SecurityWeek lists 13.1-63.18, 13.1-37.272, and 14.1-72.61 (FIPS). Bishop Fox's guidance on the first patched builds is to "Go past them to the latest available build on your branch." 12.1 and 13.0 have no fix and need migration, not a patch window.
2. Verify the patch without crashing the box. Bishop Fox published a non-destructive check: send a PrefixList of 513 or more bytes and watch the response. Patched builds return "Malformed Assertion sent to Netscaler"; vulnerable builds return a generic internal error. Repeat with a 35-byte PrefixList as a control. "One identical request, two different answers, decided by whether the fix is installed."
3. Hunt before you close the ticket. Exploitation followed the August 14 proof of concept, so anything internet-facing and unpatched since then needs review — not just a build-number check. Look for x.php and z.php on the appliance filesystem, and for id and echo in shell history.
4. Re-open anything you triaged as DoS-only this quarter. One other KEV entry this week carries the same August 29 deadline, and it is a 2019 SQL Server bug. Both are below.

Advisories

Microsoft published 19 critical cloud CVEs you cannot patch, and briefly flagged one as exploited

Microsoft's August CVRF carries 19 cloud-service CVEs dated August 20, every one rated Critical, every one marked Customer Action Required: No. Six score exactly 10.0 — Entra ID, Exchange Online, Azure Arc (twice), Azure SQL Database, and Azure Managed Instance for Apache Cassandra. The Entra ID entry, CVE-2026-69836, is a deserialization bug that "allows an unauthorized attacker to execute code over a network." Microsoft's revision history records what changed after publication: revision 1.1 on August 21 reads "Corrected Exploited to No. This vulnerability was not exploited in the wild. This is an informational change only."

Action: nothing to install — the FAQ on each entry says "this vulnerability has already been fully mitigated by Microsoft," part of Microsoft's cloud CVE transparency policy. The real work is making sure your alerting knows that. If your vulnerability feed pages an on-call engineer for a 10.0 with no patch, tune it to key on Customer Action Required before the next batch. Have the one-paragraph answer ready for the client who greps CVE feeds and asks why their tenant has a 10.0 open.

A Partner Center authorization bypass is the one on this list aimed at you

Buried in the same August 20 cloud batch is CVE-2026-69558, an "authorization bypass through user-controlled key in Microsoft Partner Center" that "allows an unauthorized attacker to disclose information over a network." Microsoft rates it CVSS 8.6 and Critical, and — unlike most of the batch — flags it "Exploitation More Likely." Partner Center is the tenant-management and billing plane most MSPs live in, which makes it the entry on this list with your name on it, not a client's.

Action: Microsoft marks this fully mitigated with no customer action, so there is no patch task. Use it as the prompt to audit who holds Partner Center access: review your delegated admin relationships, confirm every user with an admin agent role still needs it, and check that partner-side accounts enforce phishing-resistant MFA. Access review is the control you own here; the vulnerability was never yours to patch.

A 2019 SQL Server RCE is on KEV with a Saturday deadline

CISA added CVE-2019-1068 on August 26, due August 29. NVD scores it 8.8: "a remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions." It needs credentials (PR:L), so it is a lateral-movement and privilege-gain step rather than a front door. The affected list is short and checkable — NVD's configurations name exactly four: SQL Server 2014 SP2, 2014 SP3, 2016, and 2017. The Hacker News notes "there is currently no public information on how CVE-2019-1068 is being exploited in the wild."

Action: query your RMM for SQL Server build numbers across every client, including the instances nobody calls a database server — SQL Express under a line-of-business app, a vendor appliance, an old reporting box. A seven-year-old fix means the exposure is concentrated in instances that fell out of patch management, and those are exactly the ones missing from your asset list.

An unauthenticated 10.0 in the WebLogic proxy plug-in hit its deadline today

CVE-2026-21962 joined KEV on August 24 with a due date of today. Oracle's January 2026 Critical Patch Update matrix scores it 10.0, remote exploit without authentication "Yes," scope Changed, and lists supported versions affected as 12.2.1.4.0, 14.1.1.0.0, and 14.1.2.0.0. The component is the Weblogic Server Proxy Plug-in for Apache HTTP Server and for IIS; per NVD, "affected version for Weblogic Server Proxy Plug-in for IIS is 12.2.1.4.0 only."

Action: the fix shipped in the January 2026 CPU, so this is a coverage question, not a patch-availability one. The plug-in is the part that gets missed — it sits on the web tier, often installed by an integrator years ago and patched on a different cycle than WebLogic itself. Check the IIS and Apache front ends, not just the app servers behind them.

Six of this week's eleven KEV additions are old CVEs

Between August 22 and today, CISA added 11 CVEs to KEV, and six carry 2015-to-2023 IDs: two Red Hat bugs from 2015, the SQL Server RCE from 2019, an Ajax.NET Professional deserialization flaw from 2021, a Linux kernel out-of-bounds write from 2022, and CVE-2023-49105, a 9.8 ownCloud authentication bypass. Across the eleven weeks before this one, weekly pre-2026 additions ran between zero and two. The 2026 entries are Citrix, Oracle, a 9.8 Gitea RCE (CVE-2026-60004, due August 28), a Linux kernel privilege escalation, and a JFrog Artifactory path traversal.

Action: under BOD 26-04, age does not soften the deadline — the SQL Server bug got three days, same as Citrix. If your KEV cross-reference only covers current-year CVEs or only your top-tier assets, this is the week it silently under-reports. Re-run it against your full inventory rather than your patch-management scope.

Chrome 152 ships with 327 security fixes

Google promoted Chrome 152 to stable on August 25 for Windows, Mac, and Linux: 152.0.7977.64 on Linux and 152.0.7977.64/.65 on Windows and Mac. Per the release notes, "this update includes 327 security fixes." That count is a full milestone rollup, not one week's work, but it lands as one deployment. Microsoft Edge inherits the same Chromium base on its own release cadence.

Action: confirm the version actually reached endpoints rather than trusting that auto-update handled it. Chrome applies the update on relaunch, and browsers on machines nobody reboots stay on the old build for weeks. If you manage Chrome policy, RelaunchNotificationPeriod is the setting that turns a passive update into a deadline; check Edge's channel separately.

Product changes

The Microsoft 365 Roadmap is now the AI at Work Roadmap, and Release Planner retires in November

Microsoft announced on August 25 that "starting in September 2026, Dynamics 365, Microsoft Power Platform, and Microsoft Dataverse roadmap content is joining the AI at Work roadmap." The rename is the smaller half. Microsoft is also "retiring the twice-yearly release wave 1 and release wave 2 model in favor of continuous publishing," with no release wave 2 announcement this September. Content dated June 1, 2026 or later moves to the new experience by November 15, 2026, when "Release Planner retires," and "beginning in September 2026, new release plans will no longer be published to Release Plans on Learn."

Action: if your change-management calendar is built around release waves, that anchor disappears in September. Find the internal docs and client-facing decks that cite Release Planner or Release Plans on Learn and reschedule them against a continuous feed before November 15. Anything automated against those URLs needs a new target.

Licensing

OneDrive and SharePoint overage storage moves to pay-as-you-go meters

Two roadmap records put consumption billing on storage overage, both listed for November 2026. Item 562352 adds a "new pay-as-you-go, consumption-based meter for additional OneDrive storage," letting admins "control which OneDrive accounts can grow beyond their licensed storage limits." Item 506743 does the same for SharePoint, and says it "reduces the operational overhead associated with purchasing extra storage packs and more seamlessly integrates with Microsoft 365 Archive." Both are still "In development"; OneDrive previewed in July, SharePoint in June.

Action: the trade is upfront packs for a variable monthly line item, which is a margin question if you resell storage at a fixed markup. Pull your clients currently on SharePoint storage add-on packs and model both shapes before renewal season. Decide now who holds the switch to let an account exceed its licensed limit — an unbounded meter with delegated admin access is a bill someone has to explain.

Compliance

Purview will retain Copilot memory, which lives in the user's mailbox

A roadmap record dated August 21 (id 569612) adds retention for Microsoft 365 Copilot memory under Purview Data Lifecycle Management, targeting September 2026. Two details matter for anyone answering discovery requests. Copilot memory "includes saved memories and details inferred from chat history" — not only what a user typed, but what Copilot concluded about them. And those items "are stored in a hidden folder in the user's Exchange mailbox," which is territory your existing eDiscovery and retention policies already reach.

Action: if you run retention or legal hold for regulated clients, add inferred Copilot memory to the list of content types your policy has to account for, and raise it with counsel before September rather than during a matter. The feature covers "inactive memory items" only, while "active memory continues to be managed by the Copilot experience" — so confirm what a hold actually captures before you attest that it captures everything.