# CVE-2026-104617: sdbootutil: qrencode invocation leaks PIN/recovery key in /proc/<pid>/cmdline

> Local attackers can read sensitive PINs and recovery keys from process command lines due to insecure qrencode invocation in sdbootutil.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-v6xc-4hh7-9pw3, openSUSE-SU-2026:12308-1

## What is CVE-2026-104617?

CVE-2026-104617 is a medium-severity vulnerability in SUSE Linux Enterprise Server 16.1, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There are two invocations of `qrencode` to display a QR code for scanning. These invocations leak the private data $pin / $key via /proc accessible for arbitrary low-privileged users in the system.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sdbootutil` | openSUSE:Tumbleweed | All versions | 1+git20261026.4e266f0-1.1 |

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

Apply the vendor's patch.

## Is CVE-2026-104617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104617 is a medium-severity vulnerability in SUSE Linux Enterprise Server 16.1, published on 15 Oct 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-104617 in the wild and no public exploit code.

Affected product: SUSE Linux Enterprise Server 16.1. 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-104617/ (Markdown: https://insights.sbomify.com/CVE-2026-104617/index.md)
```

## Sources

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

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