PaperCut Under Fire: Repeated Patch Bypasses Keep a Pre-Auth Flaw Alive
On Thursday, 27 August 2026, PaperCut published an advisory warning that a vulnerability in its print management software was being exploited in the wild, leading to system compromise. The advisory arrived without a patch. It did include indicators of compromise in the form of log snippets, plus temporary mitigations. watchTowr Labs says its honeypot network captured the in-the-wild exploitation.
PaperCut is used by schools, universities, healthcare providers, government agencies, law firms and businesses of all sizes to control and track printing. That broad user base makes it attractive to ransomware gangs and advanced threat groups. Earlier flaws, including CVE-2023-27350 and CVE-2023-27351, were also exploited in the wild.
According to watchTowr, the root cause of the authentication bypass (CVE-2026-81578, seen in version 26.0.3) lies in how PaperCut uses the Apache Tapestry 3 framework, which the researchers describe as obsolete for roughly 20 years. Each page has its own permissions, and the authorization check only looks at the first page named in a request. Because a single request can chain several pages, an unauthenticated attacker can reach forms that belong to authenticated pages.
The first patch, version 26.0.4, added temporary protection against certain attack paths, but researchers found bypasses. watchTowr's latest write-up covers WT-2026-0143, a bypass of the patch for an earlier bypass, affecting version 26.0.4-PO build 76508. It focuses on the Setup Wizard forms, such as Create Account and Choose Organization Type, which the earlier patches had overlooked. Without a global authorization check across all pages, the researchers argue, it is hard to verify every page in the codebase.
Why it matters
Any organisation running PaperCut, especially with the server reachable from the internet, is exposed, and a patch labelled as a fix may not close the flaw. The failed control is authorization that is enforced per page rather than globally, so each patch that blocks one route leaves others open. Defenders should treat this product as one needing ongoing verification, not a single patch-and-forget update.
What to do
- Apply the latest PaperCut release and confirm your build is newer than 26.0.4-PO build 76508, which watchTowr reports was still bypassable.
- Review PaperCut logs against the indicator log snippets in the vendor advisory of 27 August 2026.
- Apply PaperCut's temporary mitigations wherever a fixed version is not yet in place.
- Restrict access to the PaperCut web interface so it is not reachable from the internet.