CVE-2026-6180: PaperCut MF: Card truncation on HP readers
A race condition exists in PaperCut MF when processing badge-swipe data from certain HP multifunction devices. Under specific network conditions involving dropped packets and out-of-order sequence counters, the server may incorrectly process fragmented data chunks. If a sequence reset notification fails to reach the server, the server may reject the initial data chunk while erroneously accepting subsequent chunks before a connection reset completes.
This leads to the registration of a truncated badge ID string. While this typically results in an authentication failure, the vulnerability is compounded in environments utilizing custom badge-ID post-processing scripts. In such configurations, the truncated string may be transformed into a valid ID belonging to a different user, leading to unauthorized session establishment (Incorrect User Login) on the device.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6180?
CVE-2026-6180 has been classified with a moderate severity due to the potential for improper processing of badge-swipe data.
How do I fix CVE-2026-6180?
To fix CVE-2026-6180, ensure that you apply the latest updates and patches provided by PaperCut for PaperCut MF.
What causes CVE-2026-6180 to occur?
CVE-2026-6180 occurs due to a race condition when processing badge-swipe data from specific HP multifunction devices under certain network conditions.
Which devices are affected by CVE-2026-6180?
CVE-2026-6180 primarily affects HP readers used with PaperCut MF.
Is there a workaround for CVE-2026-6180?
Currently, there is no official workaround for CVE-2026-6180 other than applying the updates from PaperCut.