← Back
CVE-2026-54447
Vulnerability in garminconnect (CVE-2026-54447)
Summary
vulnerability in garminconnect (CVE-2026-54447). Risk of unauthorized operations or information disclosure. Exploitable via ``garminconnect``. Mitigation: upgrade to `0.3.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54447** has been found in garminconnect.
Attackers can target a specific entry point like ``garminconnect`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade garminconnect to **0.3.5** or later.
If unsure, ask your IT team or search "garminconnect CVE-2026-54447" on the vendor's site.
CVE-2026-54447 (garminconnect) — CWE-732 /
Attack surface: `garminconnect` / `mode` / `di_token` / `di_refresh_token`
Patched: `0.3.5` — 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.
❓ What is the problem
**A vulnerability** (CWE-732) exists in garminconnect. Attackers reach the vulnerable code path via ``garminconnect`` without authentication.
📍 Affected scope
garminconnect — . Attack surface: `garminconnect` / `mode` / `di_token` / `di_refresh_token`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.3.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'garminconnect' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'garminconnect' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `garminconnect` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade garminconnect to 0.3.5ステージング環境で 0.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
garminconnect
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.5"}]}]
References
- web https://github.com/cyberjunky/python-garminconnect/security/advisories/GHSA-wjhr-76vg-2hvc
- web https://github.com/cyberjunky/python-garminconnect/commit/77a3837f1f79d486663c9646438e70e8319e1a48
- web https://github.com/cyberjunky/python-garminconnect/commit/f74174a5647e1af78eca1f8f3a0aa5dc5a899947
- web https://github.com/cyberjunky/python-garminconnect/releases/tag/0.3.5
- web https://github.com/advisories/GHSA-wjhr-76vg-2hvc