There are two invocations of `qrencode` to display a QR code for scanning. These invocations leak...
Summary
Vulnerability reported (CVE-2026-104617). Confidential information can be exposed externally. Exploitable via qrencode.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104617 has been found.
Attackers can target a specific entry point like qrencode over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-104617" on the vendor's site.
CVE-2026-104617 — CWE-522 / CVSS v3 5.1
Attack vector: local / unauthenticated / no user interaction
Attack surface: qrencode
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) has been reported. Attackers reach the vulnerable code path via qrencode without authentication.
Check the vendor advisory for the affected versions. Attack surface: qrencode.
Severity: Medium (CVSS 5.1/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web meissner@suse.de
- web meissner@suse.de
- web github.com