Wahoo Fitness SYSTM App up to 7.2.1 on Android com.WahooFitness.SYSTM BuildConfig.java SEGMENT_WRITE_KEY hard-coded key

Summaryinfo

A vulnerability classified as problematic has been found in Wahoo Fitness SYSTM App up to 7.2.1 on Android. The affected element is an unknown function of the file com/WahooFitness/SYSTM/BuildConfig.java of the component com.WahooFitness.SYSTM. Performing a manipulation of the argument SEGMENT_WRITE_KEY results in hard-coded key. This vulnerability was named CVE-2026-5462. The attack needs to be approached locally. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Wahoo Fitness SYSTM App up to 7.2.1 on Android. This affects some unknown processing of the file com/WahooFitness/SYSTM/BuildConfig.java of the component com.WahooFitness.SYSTM. The manipulation of the argument SEGMENT_WRITE_KEY with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality.

The advisory is shared at notion.so. This vulnerability is uniquely identified as CVE-2026-5462. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

The exploit is shared for download at notion.so. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-18613). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Hard-coded key
CWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

04/03/2026 Advisory disclosed
04/03/2026 +0 days VulDB entry created
04/03/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: notion.so
Status: Not defined

CVE: CVE-2026-5462 (🔒)
GCVE (CVE): GCVE-0-2026-5462
GCVE (VulDB): GCVE-100-355053
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20130704

Entryinfo

Created: 04/03/2026 02:56
Updated: 04/03/2026 12:18
Changes: 04/03/2026 02:56 (59), 04/03/2026 12:18 (1)
Complete: 🔍
Submitter: fxizenta
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #781767: Wahoo Fitness Wahoo SYSTM(com.WahooFitness.SYSTM) 7.2.1 Segment Write Key Exposure (by fxizenta)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!