Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local account
-
ExploitPoll /proc/<pid>/cmdline while qrencode runs
-
ImpactRead leaked PIN/key from process arguments
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V6 - Authentication Credential protection in transit/storage
|
| Exploitation Conditions | Exploitation requires that the vulnerable SUSE workflow invoke qrencode with the secret ($pin/$key) passed as a command-line argument, which exposes it in /proc/<pid>/cmdline. The attacker must already have a local low-privileged account on the same host (AV:L) and must read /proc during the short window while the qrencode process is executing, making this a timing race (AC:H). Limiting factors: no remote access path, confidentiality-only impact (no integrity/availability effect), and relevance largely confined to multi-user systems where untrusted local users share the host with the secret-generating process; single-user or tightly controlled hosts have little realistic exposure. |
| Impact | This is a genuine but modest-severity local credential-exposure issue, not a top-tier priority. The input CVSS 4.0 vector (AV:L/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N) and CWE-522 (Insufficiently Protected Credentials) are internally consistent with the description: secrets ($pin/$key) are passed as command-line arguments to qrencode and therefore become readable via /proc/<pid>/cmdline by other local users. Confidentiality impact is High but there is no integrity or availability impact, and the attack vector is Local with High attack complexity - the attacker must win a timing race against the short-lived qrencode process. No EPSS score, KEV listing, or public POC is present in the supplied data, so by the precision rules this is 'no public exploit identified at time of analysis'; it is neither confirmed exploited nor known-weaponized. CONFLICT TO NOTE: the input Tags include 'RCE', which contradicts the description, CWE-522, and the VC:H/VI:N/VA:N vector - this is a credential-disclosure bug, not remote code execution, and the RCE tag appears mislabeled. Net: a low-urgency, defense-in-depth fix most relevant to multi-user systems where untrusted local accounts coexist with the secret-handling workflow. |
| Exploit ScenarioDerived | On a shared SUSE/openSUSE system, a privileged setup or enrollment workflow invokes qrencode with a PIN or key passed as a command-line argument to render a scannable QR code. A separate low-privileged local user polls /proc/<pid>/cmdline during that brief execution window and reads the secret out of the process arguments. No public exploit code is identified; exploitation is a simple /proc read but requires catching the process while it runs (AC:H). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Local unprivileged users on SUSE Linux Enterprise Server 16.1, SLES for NVIDIA 16.1, openSUSE Leap 16.1 and openSUSE Tumbleweed can read a PIN or key secret that SUSE tooling renders as a QR code, because the secret is passed to qrencode as a command-line argument and is therefore exposed in /proc/<pid>/cmdline while the process runs. Exploitation requires the attacker to already hold a local low-privileged account on the same host (PR:L) and to win a short timing race against the brief qrencode invocation (AC:H), so this is a confidentiality-only credential-disclosure issue of modest severity with little realistic exposure on single-user or tightly controlled systems. There is no public exploit identified at time of analysis, and no vendor-released fix version has been confirmed in the available data, though SUSE tracks the issue through its Bugzilla and CVE pages.
RemediationAI
No vendor-released patch or fixed version is identified in the available data, so remediation currently consists of compensating controls plus monitoring the SUSE Bugzilla entry (https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-104617) and SUSE CVE page (https://www.suse.com/security/cve/CVE-2026-104617.html) for an updated package and then applying it as soon as it ships. The most effective mitigation is to stop placing the secret in argv: modify the workflow so the PIN/key is fed to the QR-code generator through a non-argv channel - for example a mode-0600 temporary file consumed with qrencode's file-input option and deleted immediately afterwards, a pipe/stdin path, or an in-process QR library - which removes the exposure entirely; the trade-off is a small amount of tooling change and careful cleanup of the temporary file. Mounting procfs with hidepid=2 (and gid= for the monitoring group) can block other users from reading /proc/<pid>/cmdline and is a quick host-wide control, but it does not protect against a same-UID reader, it can break systemd/user session tooling, monitoring agents and some container and troubleshooting utilities, and it requires /proc remount or an fstab change with a reboot or close/reopen of sessions, so it should be tested before wide deployment. Because the window is short, there is no reliable network-level or port-level control; instead, reduce local exposure by restricting shared-shell access on hosts where the secret-generating workflow runs, running that workflow only in single-user or administrator sessions, and auditing for untrusted local accounts. If there is any reason to believe the QR code was displayed on a multi-user host, treat the affected PIN/key as compromised and rotate it. Note that suppressing the terminal echo of the QR code is not a fix, since the leak occurs before any output is rendered.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
qrencode is a small command-line utility that encodes data supplied as arguments into a QR code image. Its typical usage pattern places the payload in argv, and on Linux every process's argv is readable through /proc/<pid>/cmdline by any user with permission on that procfs entry. The affected SUSE workflow invokes qrencode twice to display a QR code containing a secret ($pin / $key), so the credential is written into the process command line instead of being supplied through a non-argv channel such as stdin or a protected file descriptor. This maps to CWE-522 (Insufficiently Protected Credentials): the root cause is a credential-handling design choice, not a memory-safety or injection flaw. Exploitation is a narrow race because the secret is only visible for the lifetime of the qrencode process, and the attacker must already have a local account on the shared host. Note that the vendor-supplied CVSS 4.0 vector (AV:L/AC:H/PR:N) scores the local attack path without a privilege prerequisite at 5.9, whereas the independent assessment scores the same issue under CVSS 3.1 as AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N: the substantive difference is the prerequisite of an existing low-privileged local account, and the affected scope is confidentiality-only with no integrity or availability impact. A feed tag on this record labels it 'RCE', but the description, CWE and both score sets describe disclosure of a secret via procfs only; no code-execution path is evidenced by the supplied data.
Know when Tumbleweed gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Local access by a low-privileged account (AV:L/PR:L), a timing race against the short-lived qrencode process (AC:H), and secret disclosure only (C:H, I:N, A:N).
Primary rating from Vendor (suse).
CVSS VectorVendor: suse
Lifecycle Timeline
3DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Tumbleweed
View allIncorrect Default Permissions vulnerability in the openSUSE Tumbleweed hawk2 package allows users with access to the hac
A UNIX Symbolic Link (Symlink) Following vulnerability in keylime of openSUSE Tumbleweed allows local attackers to escal
A Incorrect Default Permissions vulnerability in the packaging of inn in openSUSE Leap 15.2, openSUSE Tumbleweed, openSU
sdbootutil on SUSE Linux Enterprise Server 16.1, SLES for NVIDIA 16.1, openSUSE Leap 16.1, and Tumbleweed creates a worl
An Improper Check for Unusual or Exceptional Conditions vulnerability in OpenSMTPD allows local users to crash OpenSMTPD
EUVD-2026-101943
GHSA-v6xc-4hh7-9pw3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB