TrebSec Daily Report
Saturday, October 24, 2026
Today's cybersecurity, AI, and compliance stories, each reviewed against its sources and broken down for four audiences. Use the reports index to search past editions by category and framework, and the frameworks directory for plain-language explainers of every body and standard referenced here.
8 stories in this edition.
Joint advisory AA26-293A, published October 20, 2026
SafePay Ransomware: FBI, CISA and Partners Detail a 600-Victim Operation
Threats
The FBI, CISA, the U.S. Secret Service, and German and United Kingdom law enforcement partners published a joint #StopRansomware advisory on the SafePay ransomware group, which has hit at least 600 victims across critical infrastructure sectors since August 2024. SafePay actors get in through stolen or brute-forced credentials, phishing, and known flaws in Cisco ASA, Veeam Backup and Replication, and SonicWall SonicOS gear, then move with legitimate tools such as PsExec and WinRM, disable security software, steal data, and encrypt files with the .SafePay extension. The advisory stresses that backup infrastructure is a deliberate target: the group stops the Volume Shadow Copy Service and resets backup storage devices to factory settings.
Executives
A ransomware group with 600 known victims is winning through ordinary gaps: weak passwords, missing multifactor authentication, and unpatched edge devices. The business question is whether your backups are offline, immutable, and actually restore-tested, because this group hunts backups first.
CIO / CISO
Treat the advisory as a checklist. Confirm the five named CVEs are patched, MFA covers VPN and remote access, and administrative tools are restricted to the accounts that truly need them. Map your detections to the ATT&CK techniques in the advisory and review logs for PsExec, WinRM, and unexpected remote access tools.
Engineers
Patch Cisco ASA (CVE-2020-3259, CVE-2023-20269), Veeam (CVE-2023-27532, CVE-2024-40711), and SonicWall SonicOS (CVE-2024-40766). Audit Active Directory for new or unfamiliar admin accounts, watch for Volume Shadow Copy Service stops and NAS factory resets, and pull the advisory IOCs in STIX format into your tooling.
Everyone (non-IT)
This is the standard modern ransomware playbook, and it starts with passwords. Use unique passwords and turn on multifactor authentication everywhere it is offered, especially email, banking, and anything reachable from the internet.
Read the standalone brief
October 2026 Patch Tuesday, reported October 14, 2026
Microsoft Ships a Record 1,413 Fixes, Including an Exploited Windows Zero-Day
Threats
Microsoft's October 2026 Patch Tuesday resolved 1,413 vulnerabilities, more than the company patched in all of 2025, including 1,102 in Windows alone. The most urgent is CVE-2026-96951, a Windows Shell security feature bypass with a CVSS score of 8.8 that is already being exploited; it strips away Mark of the Web protections, so a downloaded file can run without the SmartScreen and Office Protected View warnings users rely on. CISA added the flaw to its Known Exploited Vulnerabilities catalog and directed federal agencies to remediate by October 16. Two further flaws, a Windows Defender Application Control bypass (CVE-2026-108398) and a denial of service in MessagePack-CSharp (CVE-2026-92707), were publicly known before fixes shipped.
Executives
The sheer volume is the story: one month of Microsoft fixes exceeded the entire prior year. Sustained patching capacity, not one heroic weekend, is what keeps this from becoming an incident. Ask whether October updates are fully deployed, not just scheduled.
CIO / CISO
Prioritize by exploitation, not by count. CVE-2026-96951 is confirmed exploited and KEV-listed; the SharePoint token flaw (CVE-2026-102866) and the Outlook preview pane issues deserve fast lanes too. Microsoft's new risk cohorts are a reasonable starting point for sequencing, with your own exposure data on top.
Engineers
Deploy the October cumulative updates to internet-facing and user-facing Windows systems first, and verify Mark of the Web handling after patching. Watch for Office documents and scripts launching without Protected View prompts, and confirm Defender Application Control policies still enforce as expected.
Everyone (non-IT)
Restart your computer when it asks for updates this month. One of the fixed flaws removes the warning screens that normally stop a booby-trapped download, so running the update is what puts those warnings back.
Read the standalone brief
KEV catalog additions, October 14, 2026
CISA KEV Additions Hit Firewalls, Email Gateways, and Backup Servers
Threats
On October 14, CISA added four actively exploited vulnerabilities to its Known Exploited Vulnerabilities catalog: a code injection flaw in the Palo Alto Networks PAN-OS management interface (CVE-2026-0322, CVSS 8.6), a critical path traversal in Cisco Secure Email Gateway that lets an unauthenticated attacker write files and run commands as root from a crafted email (CVE-2026-76519, CVSS 9.8), and two chained flaws in AhsayCBS backup software (CVE-2026-105133 and CVE-2026-105134) that attackers are using to plant webshells and cryptocurrency miners. Federal civilian agencies were directed to remediate by October 17. The common thread is position: every one of these products sits at a network chokepoint or holds the organization's backups.
Executives
The devices that guard the network and hold the backups are the ones under active attack this month. If your firewall management interface or backup console is reachable from the internet, that is a board-level exposure until it is fixed.
CIO / CISO
Run these four CVEs to ground in your asset inventory today, and assume compromise where patching lagged: hunt for webshells on AhsayCBS, unexpected child processes from the PAN-OS management daemon, and odd POST patterns on the Cisco gateway. The mitigations map cleanly to ATT&CK M1051, M1035, and M1030.
Engineers
Patch first, then hunt. Restrict the PAN-OS management interface to a dedicated management network, review AhsayCBS web roots for new script files, and check outbound traffic from backup servers for mining pool connections.
Everyone (non-IT)
If your company uses a backup service or email filter you have never heard of, this is why IT sometimes patches in a hurry. These flaws let attackers skip the front door entirely, so the fix cannot wait for a quiet week.
Read the standalone brief
Technical research write-up published October 21, 2026
AI Gateway Flaws Could Hand Attackers Your Model API Keys: The LiteLLM Findings
AIThreats
A technical write-up of Check Point Research findings describes two high-severity flaws in LiteLLM, the open-source gateway many enterprises place in front of more than 100 model providers: an authentication bypass in the management plane (CVE-2026-35029) and a server-side request forgery issue (CVE-2026-59823). In the described chain, an unauthenticated request to the /config/update endpoint can rewrite model routing, redirect prompt traffic to an attacker-controlled mirror, or probe the cloud instance metadata service, and because the gateway holds root API keys for providers such as OpenAI, Anthropic, Google Gemini, and Amazon Bedrock, one compromise can expose every connected application's credentials and prompt data. The write-up recommends upgrading to the patched release, disabling dynamic configuration updates in production, isolating management ports, and enforcing IMDSv2 with a hop limit of 1.
Executives
AI gateways concentrate risk the same way identity providers do: one box holds the keys to every model your teams use. If your organization routes AI traffic through a gateway, ask who owns its patching, whether its management interface is exposed, and how quickly its keys could be rotated.
CIO / CISO
This is an AI governance finding as much as a vulnerability. Inventory every AI gateway and proxy, tie each one to an owner and a vendor risk record, and require evidence that management planes are authenticated and segmented. Under the NIST AI RMF, this is exactly the Map and Manage work: know where model traffic flows and what a compromise would expose.
Engineers
Audit LiteLLM logs for POST or PUT requests to /config/update, /model/new, and /key/generate from unexpected sources. Upgrade to the patched build, set DISABLE_CONFIG_UPDATE=True in production, keep management routes off the inference port, and require IMDSv2 with HttpPutResponseHopLimit=1 on host nodes.
Everyone (non-IT)
When a company sends your prompts through shared AI plumbing, a flaw in that plumbing can expose what you typed. Treat AI tools like any other system that sees sensitive text: do not paste customer data, credentials, or internal documents into tools your organization has not approved.
Read the standalone brief
HHS OCR settlement announced October 8, 2026
One Patient Complaint, a $140,000 HIPAA Penalty: The Shen Smiles Settlement
Compliance
HHS's Office for Civil Rights announced a $140,000 settlement with Shen Smiles, a small Pennsylvania dental practice, after a single former patient's complaint about access to her records opened a wider investigation. OCR did not pursue the access complaint itself, because the practice stated the records had been taken by a former employee, but investigators found the practice had no HIPAA policies and procedures at all, kept records in unsecured locations, moved them between offices and the dentist's home, and had not trained its workforce. OCR calculated two violations running about six years at up to $700,000 each and reduced the total by 90 percent for the practice's small size. It is also, by one compliance tracker's count, the 56th settlement in OCR's Right of Access initiative.
Executives
A ten-person practice paid $140,000 not because of a hacker, but because it could not produce basic policies when a regulator asked. The lesson scales: compliance programs fail on paper long before they fail in practice, and small size reduced the fine without excusing the violations.
CIO / CISO
Be able to produce, on request: written privacy, security, and breach-response policies that match actual operations; named Privacy and Security Officials; documented workforce training; a current security risk analysis; and business associate agreements for every vendor touching PHI. An EHR vendor does not carry these duties for you.
Engineers
Support the program with evidence your tooling already generates: access logs, terminated-user deprovisioning records, encryption status, and backup reports. When an employee departs, credential removal and record custody are security events, not just HR paperwork.
Everyone (non-IT)
You have a legal right to get a copy of your own health records, and asking for them is never out of line. If a provider stalls repeatedly, the HHS Office for Civil Rights accepts complaints, and as this case shows, one complaint can trigger a full review.
Read the standalone brief
DoD CIO program page, current as of October 24, 2026; suspension announced July 13, 2026
CMMC Phase II Stays Suspended: Self-Assessments Still Rule the Defense Supply Chain
Compliance
With the November 10, 2026 Phase II start date now weeks away, the Department of Defense's own CMMC page confirms the program remains paused in Phase 1: the July 13 suspension of Phase II third-party certification requirements still stands, a CMMC Reform Task Force review is under way, and in the interim the Department enforces NIST SP 800-171 Rev 2 through self-assessments and select government-led assessments. Phase 1 duties are unchanged: annual Level 1 self-assessment and affirmation for Federal Contract Information, and Level 2 self-assessment against the 110 requirements of NIST SP 800-171 Rev 2 for Controlled Unclassified Information, with results and affirmations entered in SPRS. The Department cited SBA data that compliance costs were pushing innovative companies out of the defense industrial base as a reason for the pause.
Executives
The certification deadline moved; the underlying obligations did not. Budget relief is real, but treating the suspension as a holiday risks contracts, because DFARS 252.204-7012 duties and SPRS affirmations continue and a false affirmation is a legal exposure, not a paperwork issue.
CIO / CISO
Keep the NIST SP 800-171 program running: current SSP, honest SPRS score, POA&M items closing inside 180 days, and annual affirmations calendared. Document the suspension decision trail so an auditor or customer can see you tracked the official program page, not headlines.
Engineers
The work is unchanged in substance: implement and evidence the 110 controls, from MFA and access control to audit logging and incident response. Use the breathing room to close the hard controls properly instead of papering them for an assessment date.
Everyone (non-IT)
If your employer sells to the Defense Department, you may hear that a big certification was postponed. The day-to-day rules for handling sensitive contract information stayed exactly the same, so handle that information with the same care as before.
Read the standalone brief
Datatilsynet decision dated October 2, 2026; announced October 12, 2026
Norway Fines Xandr EUR 8.6 Million: A Partner's Consent Is Not Your Consent
Compliance
Norway's data protection authority, Datatilsynet, fined Xandr, the advertising technology company now part of Microsoft, NOK 92 million (listed by the European Data Protection Board as EUR 8.6 million) for processing Grindr users' data without a valid legal basis. The authority found that Xandr never collected consent itself and relied on consent Grindr said it had gathered, which did not meet the GDPR standard; that the mere fact of using Grindr, together with an advertising ID and IP address, counts as special category data under Article 9; and that Xandr was a joint controller whose contracts did not transfer its accountability. The decision was signed October 2, announced in Norway on October 12, and republished by the EDPB on October 16.
Executives
Accountability cannot be outsourced. If your business receives personal data from partners, including through AI tools and data feeds, your regulator will ask what you verified, not what a contract promised. Consent and data lineage evidence are now enforcement-grade records.
CIO / CISO
Inventory every inbound and outbound personal data flow, including email, file sharing, APIs, and AI agents, and attach the legal basis and the evidence for it at each hop. Where a partner collects consent on your behalf, obtain and test the actual consent records; a signal that consent exists is not a demonstration under Article 7.
Engineers
Build the evidence as you go: log data exports with recipient, purpose, and basis; tag special category data at ingestion; and make withdrawal of consent propagate to downstream systems. If you cannot trace a record's path, that is the finding waiting to happen.
Everyone (non-IT)
Companies can be fined for data about you that they never collected directly. When an app asks for consent in vague bundles, that choice can follow your data through a chain of companies you have never heard of, which is why the regulator treated careful consent as the whole ballgame.
Read the standalone brief
DFS press release, September 10, 2026
New York DFS Tells Financial Firms: Your Risk Assessment Is the Program
Compliance
The New York State Department of Financial Services issued guidance spelling out its expectations for risk assessments under its Cybersecurity Regulation, 23 NYCRR Part 500. DFS reminded regulated entities that risk assessments must be reviewed and updated at least annually, and whenever business or technology changes materially alter cyber risk, and it detailed what it looks for: governance and oversight, methodology, scope, documentation, and real integration into the cybersecurity program. The Department specifically flagged reassessment around major technology changes, concentration in a single cloud or service provider, and emerging risks such as AI adoption. DFS noted the guidance clarifies existing obligations rather than adding new ones, and published it alongside a refreshed Cybersecurity Resource Center.
Executives
Your regulator just published its grading rubric. If your risk assessment is a dated document that the security program does not visibly follow, that gap is now the easiest finding a DFS examiner can write. Expect questions about AI adoption and single-provider concentration at board level.
CIO / CISO
Align the assessment calendar to the rule: at least annual, plus event-driven updates for migrations, acquisitions, new critical systems, and material AI deployments. Document methodology and scope decisions, and trace each material risk to a control change, a monitoring change, or a signed acceptance.
Engineers
Feed the assessment real data: asset inventories, third-party dependency maps, and architecture diagrams that match production. When a new system or AI tool goes live, trigger the reassessment workflow as part of the change, not as an afterthought.
Everyone (non-IT)
If you bank or insure in New York, this guidance is part of why your institution keeps asking security questions and updating controls. State regulators are telling firms to prove their security homework is current, and to redo it whenever their technology changes in a big way.
Read the standalone brief