CVE-2026-54447 garminconnect: Insecure Permission Assignment for Garmin OAuth Token Store
An attacker on a shared host can read insecurely stored OAuth tokens to access victim's Garmin Connect account data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54447?
CVE-2026-54447 is a high-severity vulnerability in cyberjunky python-garminconnect, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Weakness: CWE-732
Which versions are affected by CVE-2026-54447?
3 open source packages ship an affected version, including garminconnect.
| Package | Affected | Fixed in |
|---|---|---|
garminconnect PyPI | All versions | 0.3.5 |
garminconnect PyPI | All versions | 0.3.5 |
garminconnect PyPI | All versions | 0.3.5 |
How do I fix CVE-2026-54447?
Upgrade garminconnect to 0.3.5 or later.
Is CVE-2026-54447 being exploited?
There is no known exploitation of CVE-2026-54447 in the wild and no public exploit code.
Sources
Also known as GHSA-wjhr-76vg-2hvc, PYSEC-2026-3467.