-
Help Center home
-
Product manuals
-
Release notes
-
System requirements
Contents
- Overview
- What hardware is affected?
- What PaperCut products does this impact?
- What versions of PaperCut NG/MF are impacted?
- Is there a manual mitigation for this vulnerability?
- Is there any impact in applying the remediation workaround above if I’m not using impacted hardware?
- Are you releasing an update to PaperCut NG/MF?
- Overview
- What hardware is affected?
- What PaperCut products does this impact?
- What versions of PaperCut NG/MF are impacted?
- Is there a manual mitigation for this vulnerability?
- Is there any impact in applying the remediation workaround above if I’m not using impacted hardware?
- Are you releasing an update to PaperCut NG/MF?
Security Advisory: Java vulnerability “Java4Shell” (CVE-2026-114938)
Last updated November 18, 2026
Contents
- Overview
- What hardware is affected?
- What PaperCut products does this impact?
- What versions of PaperCut NG/MF are impacted?
- Is there a manual mitigation for this vulnerability?
- Is there any impact in applying the remediation workaround above if I’m not using impacted hardware?
- Are you releasing an update to PaperCut NG/MF?
- Overview
- What hardware is affected?
- What PaperCut products does this impact?
- What versions of PaperCut NG/MF are impacted?
- Is there a manual mitigation for this vulnerability?
- Is there any impact in applying the remediation workaround above if I’m not using impacted hardware?
- Are you releasing an update to PaperCut NG/MF?
We are aware of a vulnerability in Java named Java4Shell (CVE-2026-114938). The flaw is in Java’s Base64 decoder and only applies when Java runs on x86-64 processors that support the AVX-512 VBMI instruction set extension. On affected systems, an unauthenticated attacker may be able to corrupt memory, which could lead to remote code execution.
There are no reported exploits of this vulnerability at the time of writing.
For more information, see:
What hardware is affected?
Affected: x86-64 processors that support AVX-512 VBMI, including:
- Intel Xeon from Ice Lake onward, including Sapphire Rapids, Emerald Rapids and Granite Rapids
- Some Intel Core client processors (Ice Lake, Tiger Lake, Rocket Lake)
- AMD EPYC, Threadripper and Ryzen from Zen 4 onward
Not affected:
- ARM64 processors, including Apple Silicon
- x86-64 processors without AVX-512 VBMI, including Intel Skylake, Cascade Lake and Cooper Lake Xeons, and AMD processors before Zen 4
If your server’s processor does not support AVX-512 VBMI, you do not need to apply the mitigation below. If you’re unsure, it is safe to apply it anyway.
What PaperCut products does this impact?
Impacted: PaperCut NG/MF Application Servers and PaperCut NG/MF Site Servers.
Not impacted: PaperCut MF/NG secondary servers (Print Providers), PaperCut MF/NG Direct Print Monitors (Print Providers), MFD Embedded Software, PaperCut Hive, PaperCut Pocket, Print Deploy, Mobility Print, PaperCut User Client software.
What versions of PaperCut NG/MF are impacted?
These versions bundle an affected Java version and are affected when running on the hardware listed above:
- 25.0.0 up to and including 25.0.13
- 26.0.0 up to and including 26.0.6
Note: PaperCut NG/MF version 24.x and earlier are not affected.
Is there a manual mitigation for this vulnerability?
Yes. The steps below turn off Java’s vulnerable Base64 intrinsic. Applying this configuration to PaperCut’s custom/ directory ensures the setting is upgrade-safe and will not be overwritten by future PaperCut updates.
This should be applied to any PaperCut NG/MF Application Servers and Site Servers determined to be running on impacted hardware.
Windows/Linux
- Locate the text file
service.confin the following directory:[app-path]/server/custom/ - Open the file in a text editor and add or modify the additional config lines below:
wrapper.java.additional.18=-XX:-UseBASE64Intrinsics
Important: if you already have a different entry in this file containing .18 then increment by 1 so it becomes:wrapper.java.additional.19=-XX:-UseBASE64Intrinsics - Restart the Application Server or Site Server.
macOS
- Locate the text file
launch-app-server.confin the following directory:[app-path]/server/custom/ - Open the file in a text editor and add or modify the additional config lines below:
wrapper.java.additional.18=-XX:-UseBASE64Intrinsics
Important: if you already have a different entry in this file containing .18 then increment by 1 so it becomes:wrapper.java.additional.19=-XX:-UseBASE64Intrinsics - Restart the Application Server or Site Server.
Is there any impact in applying the remediation workaround above if I’m not using impacted hardware?
No functional impact. Base64 decoding switches to Java’s standard (non-accelerated) code, which may be marginally slower but isn’t noticeable in normal PaperCut use. If in doubt, you can safely apply the mitigation.
Are you releasing an update to PaperCut NG/MF?
Vulnerability scanners may still flag the Java installation as vulnerable - as such we are looking to release a maintenance release week commencing 23rd Nov, 2026 which will contain an updated (fixed) version of Java.
Category: Security Bulletins
Subcategory: Security and Privacy
Comments
Comments are not available in this preview environment. On papercut.com, this space shows the live Disqus comment thread for this page.