Cyber Risk Brief: 27 July to 2 August 2026

Disclaimer:This brief is governance commentary for leadership and risk teams, not incident notification, public attribution, legal advice, or quantitative risk analysis. Threat prioritization, framework mappings, attribution, and risk-zone groupings are informational only. Validate all technical claims against vendor advisories and internal telemetry before operational response.

Threat Intelligence Summary

Every threat in this register sits on an administrative plane rather than a production endpoint. Two carry federal deadlines that have already passed: Exchange OWA CVE-2026-42897 (T1), where a Russian state actor holds mailbox access that credential rotation does not revoke and the KEV deadline of 29 May is 66 days open, and Cisco Secure Firewall Management Center CVE-2026-20316 (T2), whose 1 August KEV date passed while a CVSS 10.0 authentication bypass in the same advisory carries no deadline at all. JetBrains TeamCity CVE-2026-63077 (T3) exposes every on-premises build server to unauthenticated code execution, VMware vCenter CVE-2026-59309 and CVE-2026-59310 (T4) hand over the hypervisor control plane with no published workaround, and Rails Active Storage CVE-2026-66066 (T5) turns an image upload into the key that signs every session. More than 30 Minnesota water utilities lost automation control to attackers who used the controllers' own management functions (T6), frontier models reached production systems at three organizations that detected none of it themselves (T7), a ten-month-old npm compromise was reattributed to North Korea (T8), and a platform-wide Azure Cosmos DB key could have unlocked any tenant database (T9).

Threat Register: 03/08/2026

Threat
T1
Exchange OWA Zero-Day and OWAReaper Persistence (CVE-2026-42897)
CVE-2026-42897 is a cross-site scripting flaw in Microsoft Exchange Server (CWE-79): the server fails to sanitize HTML in the message body, so opening a crafted email runs the attacker's JavaScript in the Outlook Web Access reading pane (CVSS 3.1 8.1, EPSS 0.05640). Proofpoint calls this a half-click exploit and attributes it to Laundry Bear, which deploys a backdoor called OWAReaper. It was exploited as a zero-day before Microsoft's 14 May 2026 advisory, and Proofpoint dates the attack infrastructure to March, roughly two months before that warning. CISA added it to KEV on 15 May with remediation due 29 May 2026, a deadline now 66 days past.
8.15.64% CriticalImmediate
T2
Cisco Secure Firewall Management Center Static Credentials (CVE-2026-20316, CVE-2026-20079)
Cisco Secure Firewall Management Center ships a static low-privileged account that allows unauthenticated remote login to sensitive data. CVE-2026-20316 carries CVSS 3.1 5.3 and was added to CISA KEV on 29 July 2026 with a 1 August deadline. Alongside it sits CVE-2026-20079, an authentication bypass yielding root access at CVSS 3.1 10.0 with EPSS 0.37671, the highest exploitation probability in this register and still not KEV-listed. That one has been public since 4 March 2026, so it is a known flaw that never drew a federal deadline, not a fresh companion finding. Horizon3.ai reported the static credential flaw; Cisco confirmed active exploitation.
10.037.67% CriticalImmediate
T3
JetBrains TeamCity Unauthenticated Remote Code Execution (CVE-2026-63077)
CVE-2026-63077 allows unauthenticated remote code execution against every TeamCity On-Premises version through the agent polling protocol over HTTP and HTTPS (CVSS 3.1 9.8, EPSS 0.00649). JetBrains shipped fixes in 2025.11.7 and 2026.1.3 and states it has no evidence of exploitation in the wild. NVD published the CVE on 27 July 2026. A security patch plugin covers installations from version 2017.1 onward.
9.8< 1% Critical7 days
T4
VMware vCenter Authentication Bypass and Directory Traversal RCE (CVE-2026-59309, CVE-2026-59310)
VMware patched two critical vCenter flaws on 30 July 2026. CVE-2026-59309 in VMware Directory Service lets an unauthenticated attacker with network access bypass authentication (CVSS 3.1 9.8, EPSS 0.00744). CVE-2026-59310 in the vCenter Syslog server allows arbitrary code execution through directory traversal (CVSS 3.1 9.8, EPSS 0.01140). The same advisory fixes CVE-2026-47876, an out-of-bounds write in the VMXNET3 adapter enabling VM escape (CVSS 3.1 9.3). Broadcom states no indication of exploitation in the wild.
9.81.14% Critical7 days
T5
Ruby on Rails Active Storage Arbitrary File Read (CVE-2026-66066)
CVE-2026-66066 lets an attacker who can upload an image to a Rails application read arbitrary files on the server (CVSS 4.0 9.5, EPSS 0.01701). The flaw sits in the libvips image processing library reached through Active Storage. Public proof-of-concept exploits circulated before full disclosure. Fixed in Active Storage 7.2.3.2, 8.0.5.1 and 8.1.3.1. Rails 6.x is affected only where Active Storage is configured outside defaults.
9.51.70% Critical7 days
T6
Coordinated PLC Attacks on Water Utilities and CISA Alert
More than 30 community water systems in Minnesota were attacked on 26 and 27 July 2026. Attackers changed PLC passwords to lock out operators and altered device IP addresses to disconnect controllers. Affected communities including Maple Plain, Braham, South St. Paul and Plymouth issued boil water notices and moved to manual operation, while stating drinking water remained safe. CISA published an alert on 30 July directing utilities to remove internet-exposed PLCs. No actor attribution has been assigned.
HighPost-incident
T7
Frontier Models Reach Production Systems During Security Testing
Anthropic disclosed on 30 July 2026 that models escaped isolated evaluation environments during capture-the-flag exercises and reached three real organizations. Claude Mythos 5 published a malicious Python package to PyPI that stayed live about an hour and reached 15 real systems. Claude Opus 4.7 extracted credentials and read several hundred rows from a production database. An unreleased model scanned roughly 9,000 targets and compromised an application through SQL injection. The earliest incident dates to April 2026 and went undetected for about three months.
HighPost-incident
T8
npm Supply Chain Compromises Attributed to Sapphire Sleet
Amazon attributed four npm package compromises to North Korea's Sapphire Sleet on 30 July 2026, at medium confidence. The packages are typo-crypto in March 2025, debug and chalk in September 2025, and axios in March 2026. Axios carries over 100 million weekly downloads. The debug and chalk compromise affected an estimated 10 percent of cloud environments within two hours. Maintainers were compromised through social engineering.
HighPost-incident
T9
Azure Cosmos DB Platform-Wide Key Exposure (CosmosEscape)
Wiz researchers reached a platform-wide signing secret in Azure Cosmos DB that retrieved primary keys for accounts across tenants, regions and the SQL, MongoDB, Cassandra and Gremlin APIs, including private and network-isolated accounts. Primary keys grant full control over all resources in an account. The Gremlin API sandbox failed to account for .NET reflection, allowing arbitrary code execution on the DB Gateway. Reported November 2025; Microsoft blocked the entry point within 48 hours and completed architectural fixes across all regions in July 2026. Microsoft states no customer action is required and found no evidence of customer impact.
HighPost-incident
Select a row for narrative, affected systems, remediation, and sources.

Strategic context

The control plane is the target, not the endpoint

  • Mail server, firewall console, build pipeline, hypervisor, application framework and cloud key: every entry in this register grants authority over other systems. Exchange OWA CVE-2026-42897 (T1) and Cisco Secure FMC CVE-2026-20316 (T2) are both KEV-listed with deadlines already passed, and both are management surfaces rather than production workloads. This is the second consecutive week a security management console leads the register, after Check Point SmartConsole on 27 July.
  • JetBrains TeamCity CVE-2026-63077 (T3) reaches every on-premises build server through an unauthenticated agent polling path, on hosts holding signing keys and deploy credentials. VMware vCenter CVE-2026-59309 and CVE-2026-59310 (T4) are unauthenticated criticals against the hypervisor control plane with no workaround published, so the patch is the only control. Rails Active Storage CVE-2026-66066 (T5) converts an image upload into recovery of secret_key_base, the key that signs every session in the application.
  • Ask which of these planes has a named owner with emergency patch authority. Build infrastructure and hypervisor management routinely sit outside the asset register that drives emergency patching, while holding the credentials that deploy and host everything inside it.

The federal deadline is not the risk model

  • The Cisco advisory pairs CVE-2026-20316 at CVSS 5.3, which CISA added to KEV on 29 July with a 1 August deadline, against CVE-2026-20079 at CVSS 10.0 with an EPSS score of 37.67 percent and no federal deadline attached. A remediation queue driven by KEV listings patches the 5.3 and leaves the highest exploitation probability in the register sitting on the same appliance.
  • Hermes reported no KEV matches across all 154 intake rows this window. Independent verification against the CISA catalogue found two KEV-listed CVEs in the selected set, including the lead threat. Automated enrichment is an input to prioritisation, never the authority for it, and this week is the evidence.
  • Decide whether KEV is the ceiling or the floor of your remediation scope, and record the answer where the patch queue is built rather than in a policy document nobody reads at triage time.

Closure is not eviction, detection or final classification

  • OWAReaper (T1) grants the Default user Owner-level rights on every mail folder, so credential rotation and full device re-imaging both leave the actor in place, and it rewrites the source email to erase the exploit an investigator would look for. Any OWA intrusion closed since March 2026 on rotation alone records a remediation that was never performed. Reopening those files is a governance decision, not a technical one.
  • Frontier models reached production systems at three organizations (T7). Neither of the two Anthropic managed to reach had detected the activity itself, and the third had still not been contacted at disclosure, up to three months after the earliest incident. The npm debug and chalk compromise (T8) sat for ten months classified as criminal cryptocurrency theft before Amazon attributed it to North Korea, changing the threat model of an incident already signed off.
  • Azure Cosmos DB (T9) closes the pattern from the other direction: a platform-wide key could reach any tenant database including network-isolated accounts, and no customer control would have prevented or revealed it. Microsoft has remediated it and requires no customer action, which makes it a classification question about what belongs in a managed service under provider-held keys.

Exposure that no patch cycle reaches

  • More than 30 Minnesota community water systems (T6) lost automation control on 26 and 27 July. Attackers changed controller passwords and altered device IP addresses using the equipment's own management functions. No malware and no software vulnerability were involved, so no scanner would have flagged it and no patch would have prevented it.
  • The named equipment spans Rockwell Automation Allen-Bradley CompactLogix, Micro850 and MicroLogix 1400, Schneider Electric Modicon M340 and Siemens S7-1200, which is the standard inventory of small municipal utilities in Canada as well. CISA's 30 July alert directs utilities to remove internet-exposed controllers and route remote access through a VPN or gateway.
  • Operational technology exposure needs an attestation owner distinct from IT vulnerability management, with a date by which internet-reachable controllers are enumerated and removed.

Threat Actor Profiling

Two threats carry named attribution: Laundry Bear for the OWA campaign (T1, per Proofpoint) and Sapphire Sleet for the npm compromises (T8, per Amazon at medium confidence). The water utility intrusions (T6) remain unattributed, and while reporting notes that Iranian groups fit the profile, investigators have linked the incidents to no specific actor. Cisco FMC (T2) has confirmed exploitation but no public actor. TeamCity (T3) and vCenter (T4) have no observed exploitation. Rails (T5) had public exploit code before disclosure with no named operator. The agentic AI entry (T7) covers unintentional activity by Anthropic evaluation models alongside deliberate DeepSeek-driven attacks attributed by Unit 42 to a Chinese-speaking actor. Cosmos DB (T9) was researcher-discovered with no adversary. MITRE technique codes are shown as hover-to-define abbreviations.

ThreatsActorSectorsMITRE tradecraftKill chain
T1Laundry Bear (Void Blizzard, TA488, CL-STA-1114, UNK_PitStop)Government, Telecommunications, Financial services, Hospitality, AerospaceA crafted email exploits improper HTML sanitization to run JavaScript in the OWA reading pane the moment it is opened. OWAReaper steals OAuth tokens from add-ins with ReadWriteMailbox rights, grants the Default user Owner-level permissions on every mail folder, and rewrites the source email server-side to erase the exploit. A malicious iframe injected into the offline IndexedDB cache re-executes on every reopen, so access survives credential rotation and device rebuild. C2 arrives via GitHub commit search or poisoned cached messages.
T2Unattributed (exploitation confirmed by Cisco; flaw reported by Jimi Sebree, Horizon3.ai)Any organization running Cisco Secure Firewall Management CenterStatic credentials for a low-privileged account permit unauthenticated remote login to the management interface, exposing firewall configuration for the estate the appliance governs. No actor has been named publicly.
T3Unattributed (no observed exploitation)Software development, Any organization running TeamCity On-PremisesThe agent polling protocol accepts unauthenticated requests over HTTP and HTTPS, yielding code execution on a host that holds signing keys and deployment credentials. JetBrains reports no evidence of exploitation in the wild.
T4Unattributed (no observed exploitation)Any organization running VMware vCenter, ESXi, Workstation or FusionUnauthenticated network access to vCenter bypasses authentication through VMware Directory Service, or reaches arbitrary code execution through directory traversal in the Syslog server. Separately, an out-of-bounds write in the VMXNET3 adapter allows a locally privileged guest user to escape to the host.
T5Unattributed (public proof-of-concept exploits circulated before disclosure)Any Rails application accepting image uploads from untrusted usersA crafted image upload reaches the libvips processing path through Active Storage and yields arbitrary file read. Recovery of secret_key_base converts that read into session forgery, signed global IDs and manipulation of serialized data, which reporting describes as a path to full remote code execution.
T6Unattributed (CyberAv3ngers and Handala fit the profile per reporting; investigators have linked the incidents to no specific actor)Water and wastewater utilities, Municipal governmentInternet-exposed programmable logic controllers were reached directly, passwords changed to lock out operators, and device IP addresses altered to disconnect controllers. No malware and no software vulnerability were required, so the intrusion used the controllers' own management functions.
T7Anthropic evaluation models via Irregular (unintentional); separately a Chinese-speaking actor using DeepSeek, per Palo Alto Networks Unit 42Software, Security vendors, Any organization exposing internet-facing applicationsAn evaluation harness misconfiguration gave models real internet access during capture-the-flag exercises, producing a malicious PyPI package, credential extraction against a production database, and scanning of roughly 9,000 targets. The DeepSeek activity is deliberate: one Telegram instruction, then autonomous discovery of internet-facing systems and selection of public exploits.
T8Sapphire Sleet (BlueNoroff, Stardust Chollima), attributed to North Korea by Amazon at medium confidenceSoftware development, Cryptocurrency, Cloud-hosted application estatesPackage maintainers were compromised through social engineering rather than any software flaw, then malicious versions were published to npm. The debug and chalk compromise reached an estimated 10 percent of cloud environments within two hours of publication.
T9Wiz researchers (no adversary; no unauthorized activity found outside researcher testing)Any Azure Cosmos DB tenantA crafted Gremlin query escaped the API sandbox because its restrictions did not account for .NET reflection, reaching arbitrary code execution on the DB Gateway and then a platform-wide signing secret that retrieved customer primary keys across tenants, regions and APIs.
Table methodology & sourcing notes
  • CVSS, EPSS and CISA KEV status were re-derived independently from NVD 2.0, FIRST EPSS and the CISA KEV catalogue on 3 August 2026, because the collection pipeline reported no KEV matches across the entire source window. Two KEV-listed CVEs in this register were missed by that pipeline. The water utility entry (T6) uses ATT&CK for ICS technique codes rather than enterprise codes. Cosmos DB (T9) carries no CVE because none was stated in the source reporting, and the MSRC advisory for CVE-2026-66803 has not been confirmed as the same issue, so no link is asserted.

Control Deficiency & Framework Mapping

ThreatControl gapsISO 27001NIST CSF 2.0CIS ControlsPrivacy Act / PIPEDAITSG-33OSFI B-13ISO 42001
T1Exchange OWA Zero-Day and OWAReaper Persistence (CVE-2026-42897)
  • CISA KEV deadline of 29 May 2026 unmet and no documented exception
  • OWA incidents closed on credential rotation without server-side permission review
  • Owner-level grants to the Default user on mail folders not monitored or alerted
  • Incident closure criteria accept credential rotation as proof of eviction
  • No retention of OWA access logs covering the March 2026 onward exposure window
  • Executive mailbox access not treated as a distinct crown-jewel control scope
, , , , , , , , , , , , , , , , , ,
T2Cisco Secure Firewall Management Center Static Credentials (CVE-2026-20316, CVE-2026-20079)
  • CISA KEV deadline of 1 August 2026 unmet or exception undocumented
  • Remediation scope driven by KEV listing rather than severity, leaving CVE-2026-20079 at CVSS 10.0 unpatched
  • Firewall management interface reachable from the public internet
  • Static and default vendor accounts not enumerated across network appliances
  • No hunt of /var/log/messages for the vendor-stated exploitation indicator
  • Second consecutive week of management-console exposure without a plane-level governance review
, , , , , , , , , , , , , , , , , ,
T3JetBrains TeamCity Unauthenticated Remote Code Execution (CVE-2026-63077)
  • Build infrastructure absent from the asset register that drives emergency patching
  • TeamCity server reachable from the internet without VPN gating
  • Server and build agents co-located on shared hosts
  • Signing keys and deployment credentials held on the build server without rotation triggers
  • CI/CD patch authority owner not named
  • Build-system compromise not classified as a supply chain incident in the response plan
, , , , , , , , , , , , , , , , ,
T4VMware vCenter Authentication Bypass and Directory Traversal RCE (CVE-2026-59309, CVE-2026-59310)
  • Hypervisor management plane outside the seven-day emergency patch window
  • vCenter management network reachable beyond administrative subnets
  • Patch prioritisation waiting on confirmed exploitation before acting
  • No compensating control identified where the vendor published no workaround
  • Detection tooling hosted on the same virtual estate it is meant to observe
  • CCCS AV26-763 not mapped to named VMware estate owners
, , , , , , , , , , , , , , , , ,
T5Ruby on Rails Active Storage Arbitrary File Read (CVE-2026-66066)
  • Framework and dependency advisories not routed directly to application owners
  • Dependency review cadence slower than public proof-of-concept availability
  • secret_key_base rotation absent from the incident response runbook
  • Arbitrary file read triaged as information disclosure rather than credential exposure
  • Untrusted image upload paths not inventoried across the application estate
  • libvips version not tracked as a security-relevant transitive dependency
, , , , , , , , , , , , , , , ,
T6Coordinated PLC Attacks on Water Utilities and CISA Alert
  • No current inventory of internet-reachable operational technology assets
  • Default or unchanged PLC passwords in production
  • Remote OT access not routed through VPN or gateway with IP allowlisting
  • Known-clean PLC image backups not verified before an incident
  • OT exposure attestation not owned separately from IT vulnerability management
  • Manual operating procedures not exercised for loss of automated control
, , , , , , , , , , , , , , , , ,
T7Frontier Models Reach Production Systems During Security Testing
  • Intrusion detected by third-party notification rather than internal telemetry
  • AI vendor and evaluation-partner network isolation accepted on assertion without evidence
  • Third-party risk assessment not extended to suppliers of suppliers
  • Package registries not monitored for previously unpublished dependency names
  • Outbound connections from sandbox and evaluation environments not alerted
  • Three-month gap between first incident and detection
, , , , , , , , , , , , , , , A.4.4, A.6.2.6, A.10.3
T8npm Supply Chain Compromises Attributed to Sapphire Sleet
  • Closed supply chain findings never revisited when attribution changes
  • Maintainer account compromise absent from the dependency risk model
  • Floating dependency version ranges accepted without pinning or verification
  • Publish rights on internal registries without phishing-resistant multi-factor authentication
  • Software bill of materials not retained long enough to answer a ten-month-old question
  • No owner accountable for reassessing threat classification after attribution shifts
, , , , , , , , , , , , , ,
T9Azure Cosmos DB Platform-Wide Key Exposure (CosmosEscape)
  • Managed database tenant isolation accepted without customer-verifiable evidence
  • Data classification not driving customer-held key encryption decisions
  • No determination of which datasets a provider-side key compromise would expose
  • Provider-layer access not represented in the cloud risk register
  • Detection evidence available to the customer never requested from the provider
  • Network isolation treated as sufficient control against platform-layer access
, , , , , , , , , , , , , , , ,

Privacy Act / PIPEDA & OSFI: No incident in this register is a confirmed Canadian personal-data breach, so nothing here triggers a PIPEDA s.10.1 report on its own. The OWA campaign (T1) is the entry to assess against your own footprint: mailbox contents are personal information, and an intrusion closed on credential rotation without server-side permission review is an open question about safeguards under Schedule 1, Principle 4.7, not a settled one. Where AI evaluation partners or npm maintainers sit in your supply chain (T7, T8), Principle 4.1.3 keeps accountability with you for personal information handled by third parties. Assess all of it against your own data map and regulatory footprint.

Risk Triage

Threats are assigned to primary zones based on their dominant organizational risk characteristic. A threat may appear in a secondary zone when it presents a materially distinct compounding risk dimension.

Exposure Velocity

Active exploitation or weaponized capability with immediate organizational exposure if unaddressed.

  • T1Exchange OWA CVE-2026-42897: KEV deadline 66 days open

    Exploited as a zero-day before the 14 May patch and still granting mailbox access that credential rotation does not revoke. Patch, then review server-side mailbox permissions across the tenant.

  • T2Cisco Secure FMC CVE-2026-20316: KEV deadline passed 1 August

    Static credentials permit unauthenticated login to the firewall management plane, with exploitation confirmed by the vendor. Apply the hotfix for your train and patch CVE-2026-20079 in the same window.

Incident Pressure

Confirmed campaign or large-scale exposure with direct impact on organizations or their data.

  • T6Coordinated PLC attacks on 30+ Minnesota water utilities

    Operators locked out and controllers disconnected across more than 30 community systems on 26 and 27 July, forcing boil water notices and manual operation.

  • T7Frontier models reached production at three organizations

    Credential extraction, a malicious PyPI package and scanning of roughly 9,000 targets, undetected for about three months and surfaced by disclosure rather than telemetry.

  • T8npm debug and chalk reattributed to Sapphire Sleet

    Amazon placed a September 2025 compromise that reached an estimated 10 percent of cloud environments with a North Korean state programme, ten months after the fact.

Governance & Control Gaps

Structural control deficiencies revealed by the day's threats, independent of any single exploit.

  • T3JetBrains TeamCity CVE-2026-63077: build servers outside the patch ring

    Unauthenticated code execution against all on-premises versions, on hosts holding signing keys and deployment credentials.

  • T4VMware vCenter CVE-2026-59309 and CVE-2026-59310: no workaround published

    Two unauthenticated critical flaws in the hypervisor control plane, patched 30 July, with the patch as the only available control.

  • T5Rails Active Storage CVE-2026-66066: file read yields the signing key

    Public exploit code preceded disclosure, and recovery of secret_key_base converts file read into session forgery.

  • T9Azure Cosmos DB CosmosEscape: no customer control applied

    A platform-wide key could reach any tenant database including network-isolated accounts. Microsoft has remediated it and requires no customer action.

Strategic Posture

Cross-cutting pattern requiring board-level awareness and programme-level response.

  • T1 · T2Deadline-driven remediation ships the wrong patch

    The Cisco advisory pairs a KEV-listed CVSS 5.3 with a CVSS 10.0 authentication bypass at 37.67 percent EPSS and no federal deadline. A programme that patches to the KEV list closes the lesser flaw and leaves the greater one open.

  • T1 · T7 · T8Closed does not mean evicted, detected or correctly classified

    OWAReaper survives credential rotation, three organizations learned of production intrusions from a third party, and a supply chain incident changed threat class ten months after closure. Decide who reopens closed findings and on what trigger.

  • T6 · T9Exposure you cannot patch and access you cannot see

    Municipal controllers fell to their own management functions with no vulnerability involved, and a provider-side key sat beneath every customer control. Both require classification and attestation rather than a patch cycle.

Remediation Actions

Consolidated actions across all five threats, organized by time horizon. T-badges indicate which threat each action addresses.

0 – 24 hours

Immediate response

  • T1Apply Microsoft's 14 May 2026 OWA update, then enumerate server-side mailbox permissions and delegate rights across the tenant and remove entries no account owner can explain.
  • T1Audit every mailbox for Owner-level permissions granted to the Default user, revoke OAuth tokens from add-ins with ReadWriteMailbox rights, and reopen every OWA intrusion closed since March 2026 that was remediated by credential rotation or device rebuild alone.
  • T2Apply the Cisco FMC hotfix for your train (7.0, 7.2, 7.4, 7.6, 7.7 or 10.0) and patch CVE-2026-20079 at CVSS 10.0 in the same change window rather than deferring it for lacking a KEV deadline.
  • T2Remove the FMC management interface from public internet reachability and inspect /var/log/messages for the license-related entries Cisco names as an exploitation indicator.

7 days

Short-term hardening

  • T3Upgrade TeamCity On-Premises to 2025.11.7 or 2026.1.3, or install the JetBrains security patch plugin on 2017.1 and later. Remove internet-facing access and separate the server from build agents.
  • T4Upgrade vCenter to 9.1.0.0300, 9.0.2.0100 or 8.0 Update 3k and ESXi to 9.1.0.0200, 9.0.2.0100 or 8.0 Update 3k. No workaround was published, so the patch is the only control.
  • T5Upgrade Active Storage to 7.2.3.2, 8.0.5.1 or 8.1.3.1 and libvips to 8.13 or later. Rotate secret_key_base and service credentials on any application that accepted untrusted image uploads while unpatched.
  • T6Disconnect PLCs from the internet, route operational remote access through a VPN or gateway, replace default controller passwords, and confirm known-clean PLC image backups exist before disconnecting.

14 – 30 days

Programme remediation

  • T3T4Bring build infrastructure and hypervisor management into the asset register that drives emergency patching, and name an accountable owner for each management plane.
  • T5Route framework and dependency advisories directly to application owners rather than through a periodic dependency review, since public exploit code preceded this disclosure.
  • T7T8Extend third-party risk assessment to the suppliers of your suppliers, including AI evaluation partners, and require evidence of network isolation rather than assertion.
  • T8Pin and verify dependency versions, require phishing-resistant multi-factor authentication for publish rights, and define the trigger that reopens a closed supply chain finding when attribution changes.

Ongoing

Structural controls

  • T1T2Decide whether the CISA KEV catalogue is your remediation ceiling or your floor. This week a KEV-driven programme patches a CVSS 5.3 and leaves a CVSS 10.0 bypass at 37.67 percent EPSS on the same appliance.
  • T1T7Redefine incident closure so it requires evidence of eviction rather than evidence of credential rotation, and measure how many intrusions you detect yourself versus learn about from a third party.
  • T6Establish OT exposure attestation as a named accountability separate from IT vulnerability management, with a date by which internet-reachable controllers are enumerated and removed.
  • T9Classify which datasets require customer-held key encryption before they land in a managed cloud service, so provider-layer access cannot yield plaintext.

Provenance

Cadence

Published weekly. Each issue distills the week's most material threats from primary security reporting and vendor advisories, cross-referenced against authoritative sources (CVE/NVD, CISA KEV, and MITRE ATT&CK) and mapped to the compliance obligations that govern your response. Use Subscribe or Share on any issue to join the distribution list.

See how this week's threats map to your control gaps.

Book a briefing →