# CVE-2026-87739: PaperCut MF/NG: User permissions are not evaluated on report generation

> Unauthenticated attackers can generate reports to access sensitive information due to missing permission checks in PaperCut MF/NG.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-hcgg-7hh4-grvw

## What is CVE-2026-87739?

CVE-2026-87739 is a medium-severity missing authorization vulnerability in PaperCut NG/MF, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper authentication vulnerability in PaperCut MF/NG allows an unauthenticated, remote attacker to trigger report generation. By submitting report generation requests without valid credentials, an attacker can generate reports and gain unauthorized access to sensitive information.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-87739 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87739 is a medium-severity missing authorization vulnerability in PaperCut NG/MF, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87739 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-87739/ (Markdown: https://insights.sbomify.com/CVE-2026-87739/index.md)
```

## Sources

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

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