Security & Threat Intelligence

The Watch

The Signal

PaperCut's second emergency fix means hosts you marked remediated are still exploitable.

Two flaws chained together skip authentication outright. The first fix closed the route and left the underlying primitive alive, which is why the vulnerability-platform record your remediation report rests on describes last week's software. The build number on each NG/MF host is the only artifact that proves what is actually running.

In Play

  1. PaperCut Re-Patch and the ownCloud KEV Listing

    PaperCut has shipped a second emergency fix for the same unauthenticated remote code execution chain, and The Hacker News reports attackers are chaining two flaws to skip authentication entirely. Instances patched in the earlier round can still be exposed, so a remediated status in your vulnerability platform is not evidence. Separately, a critical ownCloud flaw entered CISA's KEV catalog after a Chinese-speaking actor used it to steal nuclear records from a Philippine research body.

  2. Microsoft Concedes the Patch Window

    Microsoft's Azure networking executive Igor Sakhnov says attackers outpace remediation and enterprises must cut exposure before patches deploy, a concession carried in both CSO digests. That undercuts the metric most programs report to boards, because hitting 95% of a 30-day patch SLA means little when exploitation starts on day two. Note who is speaking. The prescription is network containment, which is what Azure networking sells, so evaluate segmentation cloud-neutral.

  3. Agents Damaged Real Industrial Controllers

    Autonomous agents pointed at real industrial controllers caused sustained physical damage in roughly 31% of 240 attempts, in what Techpresso describes as the first test on physical hardware rather than a simulation. The same research set explains why defenses missed it: guardrails that reset every task cannot see an attack spread across many steps. If any service account, CI runner, or tool-calling host holds a routable path to your PLC or historian VLANs, that path is now the control that matters.

  4. Encrypted Client Hello Meets Local Inference

    Android 17 turns on Encrypted Client Hello across the operating system, which hides the plaintext server name your URL filtering and network data-loss prevention read to make decisions, per The Hacker News. Exponential View reports the second removal: open-weight models reached 62% of daily tokens on Vercel, up from 28% two months earlier, and a 27b model now runs offline on a desktop Mac. Both changes delete the network event your inspection rules depend on, and neither raises an alert.

  5. Iran Sanctions Widen to a Third-Country Branch

    The US Treasury extended Iran sanctions to an Egyptian bank's UAE branch while active war disrupts Iranian oil, per Morning Brew. That pairing has historically preceded Iranian-nexus activity against US financial services and internet-exposed operational technology, skewed toward destructive impact rather than quiet collection. Two jobs follow: resolve counterparties by legal-entity hierarchy instead of name string, and execute a real restore from immutable backup rather than reviewing the runbook.

Deep Dives

  1. PaperCut's Second Emergency Fix Makes Your First Ticket Wrong

    Three of the exploited exposures sit in software already running in production, and the only field that proves your state is the build number on the host.

    Check the build banner A vendor shipping a second emergency fix for the same attack chain narrowed the exploit rather than removing the primitive. The Hacker News reports a PaperCut release adding hardening beyond the original patch. Remediation status recorded…

    3 action items

  2. Agent Identities Now Have a Routable Path to Physical Damage

    The finding that should change your backlog is not that agents attacked controllers, but that the guardrail nearly everyone deployed cannot see a campaign spread across steps.

    Where per-task filtering fails by design A guardrail that evaluates one invocation at a time carries no state between invocations. An operator who keeps each individual step innocuous never crosses a threshold, because no threshold spans the sequence. That holds…

    3 action items

  3. Android 17 Encrypts the Field Your Filtering Reads

    A phone privacy default and a cost-driven move to open weights remove the same asset from your program: the network event your inspection controls were built to observe.

    The failure mode is silent, not broken A control that loses its input does not alarm. URL filtering, network data-loss prevention, TLS-inspection policy, and guest Wi-Fi enforcement all read the plaintext server name in the TLS handshake to decide what…

    3 action items

The edition continues

Take the signal into the room.

Sign up or log in to read all 3 deep dives in full, plus the final take.

Read the full edition

Continue with LinkedIn