CVE-2026-5458

Segment write key disclosure via BuildConfig embedding

Published Apr 3, 2026 · Updated Apr 3, 2026

Hard-coded key exposure in Noelse Individuals & Pro 2.1.0 through 2.1.7 allows local users to recover the Segment write key. BuildConfig.java embeds SEGMENT_WRITE_KEY in the Android application package instead of obtaining it from protected configuration. Local access and low privileges are required; the published assessment limits impact to disclosure of the embedded key.

CVSS severity3.3
Low
EPSS probability0.14%
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 Noelse Individuals & Pro 2.1.0 through 2.1.7 allows local users to recover the Segment write key. BuildConfig.java embeds SEGMENT_WRITE_KEY in the Android application package instead of obtaining it from protected configuration. Local access and low privileges are required; the published assessment limits impact to disclosure of the embedded key.

The record

CVE
CVE-2026-5458
Published
Apr 3, 2026
Updated
Apr 3, 2026
Vendor
Noelse
Product
Noelse - Individuals & Pro
Classifications
CWE-320, CWE-321, T1552.001
Attack vector
local
Privileges
authenticated

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=2.1.0
  2. Affected versionversion=2.1.1
  3. Affected versionversion=2.1.2
  4. Affected versionversion=2.1.3
  5. Affected versionversion=2.1.4
  6. Affected versionversion=2.1.5
  7. Affected versionversion=2.1.6
  8. Affected versionversion=2.1.7

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Noelse · Noelse - Individuals & Proversion=2.1.0; version=2.1.1; version=2.1.2; version=2.1.3; version=2.1.4; version=2.1.5; version=2.1.6; version=2.1.7

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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-320Key Management Errors
CWE-321Use of Hard-coded Cryptographic Key
T1552.001Unsecured Credentials: Credentials 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