Print-management vendor PaperCut issued an urgent advisory on 27 August 2026 about zero-day attacks against PaperCut NG and PaperCut MF application servers. The company said it was aware of confirmed customer incidents and was treating every supported version as potentially affected. It reproduced the issue using information supplied by a university customer.
Technical details
The attacks chain two vulnerabilities, assigned on 28 August:
- CVE-2026-81578 – an authentication bypass in PaperCut’s use of the Apache Tapestry framework that lets an unauthenticated attacker forge URLs reaching administrative functions such as the config editor.
- CVE-2026-82078 – code execution through the external user-lookup database connector: anyone with configuration access can load Java bytecode via a crafted JDBC URL.
Chained, they give pre-authentication remote code execution on the PaperCut Application Server. PaperCut shipped an emergency patch for versions 25 and 26 on 28 August; watchTowr found a bypass the same day, prompting a second emergency patch. watchTowr’s sensors recorded exploitation from 30 August, and CISA added both CVEs to its Known Exploited Vulnerabilities catalogue on 31 August.
Observed activity
watchTowr observed an attacker temporarily reconfiguring the database connector to run Groovy/Java code and then restoring the original settings to cover tracks. Two in-memory implants were loaded as Jetty servlet filters, a Godzilla web shell and a suo5 HTTP tunnel, which suggests the goal was to pivot into internal networks. Because the implants live only in memory, they disappear on service restart, along with the evidence. PaperCut was abused by multiple ransomware and state-backed groups in 2023, so rapid follow-on attacks are likely.
Recommendations
- Immediately restrict access to PaperCut web interfaces to trusted IP ranges using firewall rules.
- Assume unpatched, internet-exposed servers are compromised: capture a memory image or heap dump and preserve logs before restarting, then apply the latest emergency release for v25/v26 and restart.
- Hunt for suspicious child processes of
pc-app.exeand for missing, truncated or deletedserver.logfiles. - Search logs for
No suitable driver found for jdbc:no:xandDatabase error looking up cardID: VALUES CAST. - Review the external database connector configuration for unexpected changes and look for newly installed remote-access tools on print servers.