Vulnerability Description
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 Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/cyberjunky/python-garminconnect/commit/8256b577190b446e279c81
- https://github.com/cyberjunky/python-garminconnect/releases/tag/0.3.5
- https://github.com/cyberjunky/python-garminconnect/security/advisories/GHSA-wjhr
FAQ
What is CVE-2026-54447?
CVE-2026-54447 is a vulnerability with a CVSS score of 8.4 (HIGH). 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 g...
How severe is CVE-2026-54447?
CVE-2026-54447 has been rated HIGH with a CVSS base score of 8.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-54447?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.