CVE Catalog

CVE-2026-54447

HighCVSS 8.4
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.15%

4th percentile - higher than 4% of all known CVEs

Summary

In garminconnect prior to 0.3.5, Client.dump in client.py creates the OAuth token directory and garmin_tokens.json without explicit owner-only modes, so with umask 022 the directory is 0755 and the file is 0644. garmin_tokens.json contains di_refresh_token, which another unprivileged user on a shared Linux/macOS host can read to gain persistent access to the victim's Garmin Connect account.

Risk Assessment

Exposure of the refresh token grants persistent access to the victim's health, fitness, activity, and device data in Garmin Connect. Pre-existing loosely permissioned token files remain exposed as well.

Recommendation

Upgrade garminconnect to version 0.3.5 or later and manually restrict permissions on existing token files and directories (e.g. chmod 600/700).

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS