Attack Chain

1. A user installs and configures the garminconnect library version 0.3.4 or earlier on a multi-user Linux or macOS system and authenticates with their Garmin Connect account.
2. The garminconnect library calls Client.dump(), persisting OAuth tokens, including the di_refresh_token and di_client_id, to the file ~/.garminconnect/garmin_tokens.json.
3. Due to the Client.dump() function not specifying a mode argument for file creation, and the system operating under a default umask (e.g., 022), the garmin_tokens.json file is created with world-readable permissions (0o644).
4. A separate, unprivileged local user on the same shared system discovers and reads the ~/.garminconnect/garmin_tokens.json file, which contains the sensitive OAuth refresh token.
5. The attacker extracts the di_refresh_token and di_client_id from the world-readable JSON file.
6. The attacker then uses the stolen di_refresh_token and di_client_id to exchange for fresh access tokens from Garmin's OAuth endpoint, bypassing the need for re-authentication.
7. The attacker uses these valid access tokens to gain unauthorized, persistent access to the victim's Garmin Connect account, enabling access to health data, activity history, and device management features.

Impact

Successful exploitation of CVE-2026-54447 leads to local credential theft and unauthorized access to victims' Garmin Connect accounts. On multi-user Linux or macOS hosts, any local, unprivileged user can read the garmin_tokens.json file, which contains the refresh token. This allows the attacker to obtain persistent access to the victim's Garmin Connect data, including sensitive health and fitness information, activity history, and device management capabilities, until the stolen refresh token is explicitly revoked. The primary risk is unauthorized access to personal data and potential account hijacking.

Recommendation

• Upgrade garminconnect: Immediately upgrade the garminconnect library to version 0.3.5 or later to mitigate CVE-2026-54447 by running pip install --upgrade garminconnect.
• Remediate existing files: Manually set secure permissions for the token store by executing chmod 700 ~/.garminconnect and chmod 600 ~/.garminconnect/garmin_tokens.json to protect existing garmin_tokens.json files.
• Rotate compromised tokens: If the garmin_tokens.json file was exposed on a shared host, treat the refresh token as compromised. Delete the existing token store (e.g., rm ~/.garminconnect/garmin_tokens.json) and log in again using the garminconnect library to mint a fresh, securely stored token.