CVE-2026-5462

Analytics key disclosure via hard-coded BuildConfig value

Published Apr 3, 2026 · Updated Apr 3, 2026

Hard-coded key exposure in Wahoo SYSTM 7.2.0 and 7.2.1 on Android allows local users to read an embedded analytics write key. The com/WahooFitness/SYSTM/BuildConfig.java file embeds SEGMENT_WRITE_KEY in the distributed application instead of protecting it outside the client. Low-privileged local access to the Android package is required; disclosure permits reuse of the key, but the public record reports no integrity or availability impact.

CVSS severity3.3
Low
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded key exposure in Wahoo SYSTM 7.2.0 and 7.2.1 on Android allows local users to read an embedded analytics write key. The com/WahooFitness/SYSTM/BuildConfig.java file embeds SEGMENT_WRITE_KEY in the distributed application instead of protecting it outside the client. Low-privileged local access to the Android package is required; disclosure permits reuse of the key, but the public record reports no integrity or availability impact.

The record

CVE
CVE-2026-5462
Published
Apr 3, 2026
Updated
Apr 3, 2026
Vendor
Wahoo Fitness
Product
Wahoo SYSTM
Classifications
CWE-321, CWE-320, T1552.001
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Apr 3, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 3, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=7.2.0
  2. Affected versionversion=7.2.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

Wahoo Fitness · Wahoo SYSTMversion=7.2.0; version=7.2.1

Published CVSS scores

1.9VulDBCVSS: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
1.7VulDBAV:L/AC:L/Au:S/C:P/I:N/A:N
3.3VulDBCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-321Use of Hard-coded Cryptographic Key
CWE-320Key Management Errors
T1552.001Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo