{"answers":{"affected":"3 open source packages ship an affected version, including garminconnect.","exploited":"There is no known exploitation of CVE-2026-54447 in the wild and no public exploit code.","fix":"Upgrade garminconnect to 0.3.5 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-54447 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-54447 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- garminconnect (PyPI): affected all versions; fixed in 0.3.5\n- garminconnect (PyPI): affected all versions; fixed in 0.3.5\n- garminconnect (PyPI): affected all versions; fixed in 0.3.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54447/ (Markdown: https://insights.sbomify.com/CVE-2026-54447/index.md)","id":"CVE-2026-54447","markdown":"https://insights.sbomify.com/CVE-2026-54447/index.md","name":"CVE-2026-54447","record":{"aliases":["GHSA-wjhr-76vg-2hvc","PYSEC-2026-3467"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Python Garmin API wrapper","requires_auth":"low_privilege","summary":"An attacker on a shared host can read insecurely stored OAuth tokens to access victim's Garmin Connect account data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"garminconnect: Insecure Permission Assignment for Garmin OAuth Token Store","id":"CVE-2026-54447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Trivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser","id":"CVE-2026-54448"},"packages":[{"ecosystem":"PyPI","fixed":["0.3.5"],"introduced":["0"],"last_affected":[],"package":"garminconnect","purl":null,"source":"GHSA-wjhr-76vg-2hvc"},{"ecosystem":"PyPI","fixed":["0.3.5"],"introduced":["0"],"last_affected":[],"package":"garminconnect","purl":"pkg:pypi/garminconnect","source":"GHSA-wjhr-76vg-2hvc"},{"ecosystem":"PyPI","fixed":["0.3.5"],"introduced":["0"],"last_affected":[],"package":"garminconnect","purl":"pkg:pypi/garminconnect","source":"PYSEC-2026-3467"}],"prev":{"headline":"NetLicensing MCP Server: Unauthenticated Use of Server-Side NetLicensing API Key in HTTP Mode","id":"CVE-2026-54446"},"products":["python-garminconnect"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["cyberjunky"]},"summary":"An attacker on a shared host can read insecurely stored OAuth tokens to access victim's Garmin Connect account data.","url":"https://insights.sbomify.com/CVE-2026-54447/"}