1-minute read
What a defender needs to know
Attackers exploit PaperCut NG and MF: a pre-authentication request changes configuration before unsafe driver loading executes Java code in the Application Server. All versions may be affected; September 10 maintenance releases supersede emergency builds on v24-v26.
PaperCut’s August 30 timeline moves from identity and version queries through whoami and ver to a staged executable and the LocalSystem SimpleHelp service Remote Access Service in 27 minutes. It adds server.log markers and five-character class-file patterns.
CISA added CVE-2026-81578 and CVE-2026-82078 to the exploited-vulnerability catalog on August 31, with a September 14 deadline for federal civilian agencies.
Restrict every PaperCut web interface to trusted IP addresses. Install the applicable 26.0.5, 25.0.13, or 24.1.10 release on the Application Server, every Site Server, and every secondary or print server, including hosts that received an emergency patch. Preserve logs and process history before remediation. Search server.log for ERROR No suitable driver found for jdbc:no:x and DB URL: jdbc:derby:memory:pwn;create=true; correlate matches with <install>\server\lib\<5-char-name>.class, child execution from pc-app.exe, identity and version queries through whoami and ver, and Remote Access Service.
Only deployments that need external database Card/ID lookup should add security.card-number-lookup.enabled=Y to server/security.properties and restart the Application Server. This optional feature is not a security mitigation. For suspected compromise, PaperCut recommends rebuilding the Application Server and restoring a clean backup taken before suspicious behavior.
From an untrusted network, verify that each web interface receives a network-layer denial with no application response. On a rebuilt server, expect no unexplained indicators or PaperCut child shell. A clean search cannot clear a previously exposed host; attackers may delete files and logs.