CVE-2026-6180: PaperCut MF: Card truncation on HP readers

Published May 5, 2026
·
Updated

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

5 affected components
PaperCut PaperCut MF
PaperCut PaperCut MF<24.1.9
PaperCut PaperCut MF>=25.0.2<25.0.10
PaperCut PaperCut NG<24.1.9
PaperCut PaperCut NG>=25.0.2<25.0.10

Event History

May 5, 2026
CVE Published
via MITRE·06:19 AM
Data Sourced
via MITRE·06:19 AM
DescriptionWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

Which devices are affected by CVE-2026-6180?

CVE-2026-6180 primarily affects HP readers used with PaperCut MF.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203