Python Garminconnect
Approved changes feed: RSS · Atom
cpe:2.3:a:cyberjunky:python-garminconnect:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Cyberjunky (b489b91f-de27-56af-a610-fc791284c769) |
|---|---|
| Product | Python Garminconnect (6d315d95-0f0a-5d61-8b08-829e5b08a8ac) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54447 |
vulnerable | 2026-09-16 04:33:28.736460 |
garminconnect: Insecure Permission Assignment for Garmin OAuth Token Store
HIGH (8.4)
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.
Published: 2026-09-14T19:53:38.954Z
Updated: 2026-09-14T20:10:01.561Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.