garminconnect Has Insecure Permission Assignment for Garmin OAuth Token Store

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.4 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-54447: 0.15% estimated exploitation activity in the next 30 days; percentile 4.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Insecure Permission Assignment for Garmin OAuth Token Store Summary garminconnect (≤ 0.3.4) wrote its OAuth token store to disk without restricting file-system permissions. Under the default Linux umask (022) the token file garmintokens.json was created world-readable (0o644). The file contains the DI refresh token, so any other local user on a shared host could read it and obtain persistent, unauthorized access to the victim's Garmin Connect account. - Severity: High - Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource) - Affected versions: <= 0.3.4 - Patched version: 0.3.5 Details Client.dump() created the token directory and file with no mode argument, leaving permissions entirely to the process umask: The serialized payload includes ditoken, direfreshtoken, and diclientid. The call is in the core library (Garmin.login(tokenstore=...) persists tokens this way), and all shipped usage examples default the token store to ~/.garminconnect. Under umask 022 the…

Published by the source

15 Jul 2026, 17:33 UTC

Last modified by the source

23 Jul 2026, 15:11 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wjhr-76vg-2hvc

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wjhr-76vg-2hvc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54447

Advisory: garminconnect Has Insecure Permission Assignment for Garmin OAuth Token Store
IDs: CVE-2026-54447, GHSA-wjhr-76vg-2hvc
Record: https://patchnext.com/advisories/cve-2026-54447 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: garminconnect 0.3.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI garminconnect: affected <= 0.3.4; fixed in 0.3.5

## Suggested inspection (read-only)
- `python -m pip show garminconnect`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on garminconnect.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wjhr-76vg-2hvc (OSV record GHSA-wjhr-76vg-2hvc lists affected ranges: PyPI garminconnect >=0 <0.3.5 (fixed))
- Verified: https://github.com/advisories/GHSA-wjhr-76vg-2hvc (GitHub-reviewed advisory GHSA-wjhr-76vg-2hvc lists affected ranges: PyPI garminconnect >=0 <=0.3.4)

Commands are suggestions: review each one before running it.