Patch-Bypass · CuraSec

tag: Patch-Bypass · 2 items

Engineer — Act: PaperCut NG and MF are actively exploited and the first fix was bypassed, meaning unpatched and initially-patched instances remain at risk; update to the latest emergency release immediately and verify the new version is applied end-to-end.
SOC/IR — Plan: Active exploitation with a bypassed patch means print servers in the estate may already be compromised; build or tune detections for anomalous outbound connections and process spawning from PaperCut service accounts, and sweep logs back to the original disclosure date.
Leader — Plan: If PaperCut is in the environment, confirm with engineering that the second emergency patch is deployed and request a status update — active exploitation plus a failed first fix is the kind of event that can escalate to a breach if patching is delayed.

Engineer — Plan: Public PoC on GitHub means the original CVE-2026-50656 patch is insufficient, but EPSS 0.11 and no KEV listing indicate no confirmed active exploitation yet. Monitor Microsoft’s advisory for an updated patch and apply it immediately when released; in the interim, audit for any unexpected SYSTEM-level Defender process activity.
SOC/IR — Plan: The public PoC provides enough technical detail to build behavioral detections before in-the-wild exploitation begins. Develop signatures for anomalous Microsoft Defender process privilege escalation patterns from the PoC and queue for tuning once exploitation is confirmed.
Leader — Skip
Signals: CVE-2026-50656 — CISA KEV: not listed, EPSS 0.11, public PoC on GitHub