CVE-2026-54447

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

garminconnect is a Python 3 API wrapper for Garmin Connect that retrieves statistics and manages activities. Prior to 0.3.5, garminconnect/client.py Client.dump creates the OAuth token directory and garmin_tokens.json without explicit owner-only modes, so a permissive umask such as 022 can leave the directory mode at 0755 and the token file mode at 0644. garmin_tokens.json contains di_refresh_token, and another unprivileged user on a shared Linux or macOS host can read the token and obtain persistent access to the victim's Garmin Connect account, including health, fitness, activity, and device data. The Garmin.login tokenstore path is affected, and a pre-existing loosely permissioned token file remains exposed until rewritten or manually restricted. This issue is fixed in version 0.3.5.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 15, 2026

Last Modified

September 14, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

Release 0.3.5

Patch available: cyberjunky/python-garminconnect 0.3.5

https://github.com/cyberjunky/python-garminconnect/releases/tag/0.3.5
github_commit Patch Available

commit 8256b577190b (cyberjunky/python-garminconnect)

Patch available: cyberjunky/python-garminconnect 0.3.5 (contains commit 8256b577190b)

https://github.com/cyberjunky/python-garminconnect/commit/8256b577190b446e279c81b845d8e27d0ea1fbf5
github Patch Available

Insecure Permission Assignment for Garmin OAuth Token Store · Advisory · cyberjunky/python-garminconnect · GitHub

https://github.com/cyberjunky/python-garminconnect/security/advisories/GHSA-wjhr-76vg-2hvc

Vendor Advisories for CVE-2026-54447(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
garminconnect0.1.1 ... 0.3.4 (98 versions)0.3.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 04:44 UTCEG score recompute
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-14 20:27 UTCEG score recompute
  7. 2026-09-14 20:16 UTCEG score recompute
  8. 2026-07-30 14:10 UTCEG score recompute
  9. 2026-07-26 11:33 UTCEG score recompute
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-07-15 17:54 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54447?
CVE-2026-54447 is a high vulnerability published on July 15, 2026. garminconnect is a Python 3 API wrapper for Garmin Connect that retrieves statistics and manages activities. Prior to 0.3.5, garminconnect/client.py Client.dump creates the OAuth token directory and garmintokens.json without explicit owner-only modes, so a permissive umask such as 022 can leave the…
When was CVE-2026-54447 disclosed?
CVE-2026-54447 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54447 actively exploited?
CVE-2026-54447 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-54447?
CVE-2026-54447 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-54447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54447, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54447

Explore →

Is Your Infrastructure Affected by CVE-2026-54447?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs