# CVE-2026-6418: PaperCut NG/MF: Path Traversal in Shared Account Synchronization

> Administrative users can exploit path traversal in Shared Account Synchronization to read arbitrary local files and disclose sensitive system information.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-mhwr-j844-q9pq

## What is CVE-2026-6418?

CVE-2026-6418 is a medium-severity path traversal vulnerability in PaperCut NG/MF, published on 5 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in the Shared Account Synchronization component of PaperCut MF (version 25.0.4). The application allows administrative users to configure a source path for account data synchronization.

Due to a lack of proper path validation and sanitization, an authenticated user with administrative privileges can specify arbitrary file paths on the local file system. This allows for the enumeration of directory structures and the unauthorized reading of sensitive text-based configuration or system files.

When the synchronization process is triggered, the application attempts to parse the contents of the specified file, subsequently exposing the data within the application's account management interface. This vulnerability could lead to the disclosure of sensitive system information or configuration details, depending on the permissions of the service account under which the application is running.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-36 (Absolute Path Traversal)

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

It affects 2 products.


Products: Papercut Papercut Mf, Papercut Papercut Ng.

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

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

## Is CVE-2026-6418 being exploited?

There is no known exploitation of CVE-2026-6418 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-6418 and fix it if it is affected.

What it is: CVE-2026-6418 is a medium-severity path traversal vulnerability in PaperCut NG/MF, published on 5 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6418 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-6418/ (Markdown: https://insights.sbomify.com/CVE-2026-6418/index.md)
```

## Sources

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

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