PaperCut’s guidance updated November 18 identifies NG/MF Application Servers and Site Servers affected by Java4Shell, CVE-2026-114938. The flaw can corrupt memory and potentially allow remote code execution. Exposure depends on the bundled Java runtime and processor capabilities.
Check the server version and hardware
The vendor lists NG/MF 25.0.0–25.0.13 and 26.0.0–26.0.6 on x86-64 processors supporting AVX-512 VBMI. Version 24.x and earlier, and ARM64 hardware, are outside this affected scope.
Temporary mitigation and planned maintenance
PaperCut documents a configuration change that disables Java’s vulnerable Base64 intrinsic, followed by a server restart. Use its platform-specific instructions and preserve existing configuration entries.
The vendor is targeting a maintenance release containing corrected Java for the week beginning November 23. That remains a planned release. Vulnerability scanners may continue flagging the runtime after the workaround.
IPCRIME analysis: Track the temporary control
Record each server’s role, application build, processor support and mitigation status before scheduling changes. Assign an owner to revisit the maintenance release when it becomes available, then validate printing and administrative workflows after deployment.
Keep evidence of the applied configuration and restart with the change record. A temporary control needs an explicit follow-up date; otherwise it can be mistaken for a completed software upgrade. Treat a scanner result as one input to the review and retain the vendor’s explanation alongside the remediation record.
Related reading: Oracle’s November Java update and Java4Shell coverage.
Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.
