Monthly issue · Published October 13, 2026

CyberClaw · October 2026

Fifteen picks across five lanes. A wormable DNS bug to finish patching, ransomware crews hitting healthcare and government, a new Wazuh on the way, incident-reporting clocks getting closer, and AI agents leaking data in new ways.

Blue Team

Blue lane →

Finish September's Windows patches: a wormable DNS bug and two exploited flaws

September's Patch Tuesday fixed CVE-2026-69730, a Windows DNS remote-code-execution flaw described by ZDI as a successor to SigRed, plus two exploited privilege-escalation bugs: CVE-2026-81963 (Windows Update Stack) and CVE-2026-85880 (ALPC).

Do this now: Confirm every Windows DNS server and domain controller has the September cumulative update. Prioritize internet-facing DNS.

October Patch Tuesday is out today (Oct 13)

Microsoft's October release lands on the 13th. Check whether any fixes are flagged as exploited or publicly disclosed before deciding your rollout order.

Do this now: Review the MSRC update guide this week and fast-track anything marked exploited.

CISA KEV additions: SharePoint, vCenter, IKE and macOS

CISA added CVE-2026-55040 (SharePoint weak authentication), CVE-2026-59310 (vCenter path traversal), CVE-2026-33824 (Windows IKE double free) and CVE-2026-65400 (macOS improper authentication) to the Known Exploited Vulnerabilities catalog.

Do this now: If you run on-prem SharePoint or vCenter, treat these as emergency patches and check access logs for the exposure window.

Red Team

Red lane →

Ransomware crews are going after healthcare and government

Tracked incidents over the summer were led by healthcare/medtech and public-sector victims. Active names include ShinyHunters, Qilin, Clop and Rhysida, with high-profile hits on Boston Scientific, Manchester Airports Group and the Berlin city government.

Do this now: For your next authorized test, emulate the exfiltrate-then-extort flow: can you move large volumes of data out before anyone notices?

AI agents can do credential reuse too

In a reported capture-the-flag evaluation, an AI model guessed passwords and reused credentials found in public repositories to reach real company systems. Leaked secrets are now cheaper than ever to exploit.

Do this now: Add secret scanning of your public repos and paste sites to every engagement scope. Assume anything leaked will be tried.

Plugin4Shell: the developer toolchain is attack surface

A reported plugin-installation flaw affecting several AI coding tools let pinned plugins be swapped for malicious code without prompting the user.

Do this now: When scoping a test, include developer workstations and their AI/IDE extensions, not just servers.

Purple Team

Purple lane →

Wazuh 5.0 is in beta: worth a lab test

Wazuh 5.0 betas add a built-in threat-intel (CTI) section, incident response in the dashboard, AI assistant settings, and switch file-integrity who-data to eBPF by default. Manager daemons and config files were reorganized, and legacy OS support was dropped.

Do this now: Stand it up next to your current SIEM in the lab and replay last month's alerts. Don't upgrade production during beta.

Detection idea: watch your DNS servers this month

With a wormable DNS bug patched in September, unpatched DNS servers are an obvious target. Exploitation of server processes usually shows up as crashes and unusual child processes.

Do this now: Alert on dns.exe service crashes/restarts and on any process spawned by dns.exe. Test the alert with a benign child process in the lab.

Log your AI agents like you log your admins

A reported flaw in the official MCP Python SDK let a malicious MCP server capture OAuth credentials. Agent tool calls are becoming a new privileged-access path.

Do this now: Inventory which MCP servers and AI agents can reach your systems, and forward their auth and tool-call logs into the SIEM.

Compliance

Compliance lane →

CIRCIA: prepare for 72-hour incident reporting

CISA's final CIRCIA rule was slated for September 2026 in the Unified Agenda. When it takes effect, covered critical-infrastructure entities must report covered incidents within 72 hours and ransom payments within 24 hours. Check the Federal Register for publication status and the effective date.

Do this now: Decide whether each legal entity is covered, and build one notification matrix that runs CIRCIA, SEC, HIPAA and state clocks side by side.

EU AI Act: high-risk deadlines pushed back

Under the Digital Omnibus deal, high-risk obligations for stand-alone (Annex III) systems move to December 2, 2027, and for AI inside regulated products (Annex I) to August 2, 2028. The Parliament approved it in June; confirm final Council adoption and Official Journal publication.

Do this now: Use the extra time to finish your AI inventory and risk classification instead of pausing the program.

Map this month's patches to your controls

Exploited vulnerabilities on the CISA KEV list are a clean piece of audit evidence: they show whether your patch-management control actually works on deadline.

Do this now: Record the date each KEV item from this issue was patched. That timeline is ready-made evidence for SOC 2, ISO 27001 and PCI DSS reviews.

AI Security

AI lane →

AI coding agents leaked thousands of internal screenshots

Reports at the end of September described AI coding agents publishing more than 13,000 internal screenshots to public GitHub repositories, exposing billing and treasury data from hundreds of organizations.

Do this now: Check what your coding agents are allowed to commit and push. Block image and data files from agent commits by default.

MCP Python SDK flaw exposed OAuth credentials

A flaw in the official MCP Python SDK let a malicious MCP server capture OAuth client credentials and authorization codes.

Do this now: Update the SDK, and only connect agents to MCP servers you trust and can audit.

Microsoft fixed Copilot 'Reprompt' and an Azure AI Foundry auth flaw

Microsoft patched Reprompt, a Copilot issue where one click on a legitimate link could silently exfiltrate data, and CVE-2026-85889, a missing-authentication flaw in Azure AI Foundry that Microsoft mitigated with no customer action required.

Do this now: Treat links opened by AI assistants like links opened by users: run them through the same URL filtering and DLP.

Some items come from secondary trackers and news reports. Confirm CVE details and dates with the vendor or agency advisory before acting.