Vulnerability in github.com/jhaals/yopass (CVE-2026-107840)
Summary
Vulnerability in github.com/jhaals/yopass (CVE-2026-107840). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20260727191436-61e31ead04a4 or later.
Original description
The description as published by the source.
The Prometheus metrics middleware in pkg/server/server.go used r.Method directly as a label value on request counter and duration histogram metrics. Since the mux catch-all route matches any HTTP method, an unauthenticated attacker can send requests with arbitrary method strings (e.g. curl -X "M1" http://host/), each creating new counter and histogram time series in the Prometheus registry. The registry's internal maps never evict entries.
An attacker issuing requests with unique method values causes monotonic memory growth until the process is OOM-killed. Additionally, /metrics scrape latency degrades proportionally, eventually timing out and blinding monitoring.
Remediation: Upgrade to 14.7.0 or later, which clamps the method label to a fixed allowlist (GET, POST, PUT, DELETE, OPTIONS, HEAD, CONNECT, TRACE) and maps everything else to other.
Source: NIST National Vulnerability Database 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-107840 has been found in github.com/jhaals/yopass.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/jhaals/yopass to 0.0.0-20260727191436-61e31ead04a4 or later.
If unsure, ask your IT team or search "github.com/jhaals/yopass CVE-2026-107840" on the vendor's site.
CVE-2026-107840 (github.com/jhaals/yopass) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.0.0-20260727191436-61e31ead04a4 — apply immediately
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-400) exists in github.com/jhaals/yopass.
Check the vendor advisory for the affected versions of github.com/jhaals/yopass.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260727191436-61e31ead04a4.
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. Run grep -r 'github.com/jhaals/yopass' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/jhaals/yopass' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/jhaals/yopassを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/jhaals/yopass to 0.0.0-20260727191436-61e31ead04a4ステージング環境で 0.0.0-20260727191436-61e31ead04a4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。