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

> A race condition in PaperCut MF allows unauthorized session establishment via truncated badge IDs when custom post-processing scripts are enabled.

- **Severity:** Medium 4.1 (`CVSS:4.0/AV:P/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-hqg4-rx24-2464

## What is CVE-2026-6180?

CVE-2026-6180 is a medium-severity vulnerability in PaperCut NG/MF, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-6180?

It affects 2 products.


Products: Papercut Papercut Mf, Papercut Papercut Ng.

## How do I fix CVE-2026-6180?

No fix has been published for CVE-2026-6180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6180 being exploited?

There is no known exploitation of CVE-2026-6180 in the wild and no public exploit code.

## Other vulnerabilities in PaperCut NG/MF

- [CVE-2023-27350](https://insights.sbomify.com/CVE-2023-27350/): PaperCut MF/NG Improper Access Control (critical 9.8, exploited in the wild)
- [CVE-2026-82078](https://insights.sbomify.com/CVE-2026-82078/): PaperCut NG/MF Unsafe Reflection (critical 9.4, exploited in the wild)
- [CVE-2026-81578](https://insights.sbomify.com/CVE-2026-81578/): PaperCut NG/MF Missing Authentication for Critical Function (high 8.8, exploited in the wild)
- [CVE-2023-2533](https://insights.sbomify.com/CVE-2023-2533/): PaperCut NG/MF Cross-Site Request Forgery (CSRF) (high 8.4, exploited in the wild)
- [CVE-2023-27351](https://insights.sbomify.com/CVE-2023-27351/): PaperCut NG/MF Improper Authentication (high 8.2, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6180 and fix it if it is affected.

What it is: CVE-2026-6180 is a medium-severity vulnerability in PaperCut NG/MF, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6180 in the wild and no public exploit code.

Affected product: PaperCut NG/MF. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6180/ (Markdown: https://insights.sbomify.com/CVE-2026-6180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6180
- OSV: https://osv.dev/vulnerability/CVE-2026-6180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6180/
Summaries are generated and may contain mistakes; the official description above is the record.