{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5462 exists.","fix":"No fix has been published for CVE-2026-5462 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5462 is a medium-severity vulnerability in Wahoo Fitness SYSTM App, published on 3 Apr 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-5462 and fix it if it is affected.\n\nWhat it is: CVE-2026-5462 is a medium-severity vulnerability in Wahoo Fitness SYSTM App, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5462 exists.\n\nAffected product: Wahoo Fitness SYSTM App. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-5462/ (Markdown: https://insights.sbomify.com/CVE-2026-5462/index.md)","id":"CVE-2026-5462","markdown":"https://insights.sbomify.com/CVE-2026-5462/index.md","name":"CVE-2026-5462","record":{"aliases":["GHSA-8294-68fr-jrmh"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Wahoo Fitness SYSTM App","requires_auth":"low_privilege","summary":"Attackers with local access can exploit a hard-coded cryptographic key in the Wahoo Fitness SYSTM Android app to potentially access sensitive data or bypass security controls.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"description":"A vulnerability was identified in Wahoo Fitness SYSTM App up to 7.2.1 on Android. Impacted is an unknown function of the file com/WahooFitness/SYSTM/BuildConfig.java of the component com.WahooFitness.SYSTM. Such manipulation of the argument SEGMENT_WRITE_KEY leads to use of hard-coded cryptographic key\r . Local access is required to approach this attack. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Wahoo Fitness SYSTM App com.WahooFitness.SYSTM BuildConfig.java hard-coded key","id":"CVE-2026-5462","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"pymetasploit3 - Command Injection via Newline Injection in console.run_module_with_output()","id":"CVE-2026-5463"},"packages":[],"prev":{"headline":"Heap Use-After-Free in PQC Hybrid KeyShare Error Cleanup in wolfSSL TLS 1.3","id":"CVE-2026-5460"},"products":["SYSTM App"],"published":"2026-04-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-03","vendors":["Wahoo Fitness"]},"summary":"Attackers with local access can exploit a hard-coded cryptographic key in the Wahoo Fitness SYSTM Android app to potentially access sensitive data or bypass security controls.","url":"https://insights.sbomify.com/CVE-2026-5462/"}