# CVE-2026-61702: OpenPrinting CUPS: root-side banner file disclosure

> Attackers can exploit path traversal in CUPS banner processing to read arbitrary files via job sheets, requiring specific pre-positioned filesystem state.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-108281, BELL-CVE-2026-61702, DEBIAN-CVE-2026-61702, ECHO-d1e3-6268-da43, GHSA-gq9p-4w7m-2f5g, UBUNTU-CVE-2026-61702

## What is CVE-2026-61702?

CVE-2026-61702 is a medium-severity path traversal vulnerability in OpenPrinting cups, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to 2.4.20, copy_banner() in scheduler/ipp.c uses the attacker-controlled IPP attributes-natural-language value as a directory component beneath DataDir/banners when processing a job-sheets banner. The job-sheets value must first match a registered banner basename, and the traversed path must contain a matching reachable basename; selecting an arbitrary target as demonstrated additionally requires pre-positioned path state such as a symlink with that basename. Subject to the scheduler's filesystem and sandbox access, path separators in the language value can escape the intended banner directory, make the root scheduler open the reachable file, and copy its bytes into a job-sheet spool object that a configured backend can deliver to an attacker-observable endpoint. This issue is fixed in version 2.4.20.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Openprinting Cups.

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

Upgrade to a fixed version.

## Is CVE-2026-61702 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61702 exists.

## Other vulnerabilities in OpenPrinting cups

- [CVE-2025-58060](https://insights.sbomify.com/CVE-2025-58060/): cups has Authentication bypass with AuthType Negotiate (high 8.0)
- [CVE-2026-34978](https://insights.sbomify.com/CVE-2026-34978/): Path traversal in cups (medium 6.5)
- [CVE-2025-58364](https://insights.sbomify.com/CVE-2025-58364/): cups: Remote DoS via null dereference (medium 6.5)
- [CVE-2026-34980](https://insights.sbomify.com/CVE-2026-34980/): OpenPrinting CUPS: Shared PostScript queue lets anonymous Print-Job requests reach `lp` code execution over the network (medium 6.1)
- [CVE-2025-61915](https://insights.sbomify.com/CVE-2025-61915/): OpenPrinting CUPS vulnerable to stack based out-of-bound write (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61702 is a medium-severity path traversal vulnerability in OpenPrinting cups, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61702 exists.

Affected product: OpenPrinting cups. 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-61702/ (Markdown: https://insights.sbomify.com/CVE-2026-61702/index.md)
```

## Sources

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

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