Local Segment write-key disclosure via bundled configuration
Published Apr 3, 2026 · Updated Apr 3, 2026
Hard-coded key exposure in Dialogue 4.3.0 through 4.3.2 for Android allows local users to extract a Segment write key from the app package. The ca.diagram.dialogue package stores SEGMENT_WRITE_KEY as a static value in res/raw/config.json, exposing it when the APK resources are inspected. Exploitation requires low-privileged local access; the published assessment limits impact to credential disclosure, with no integrity or availability loss.
Summary
What happened
Hard-coded key exposure in Dialogue 4.3.0 through 4.3.2 for Android allows local users to extract a Segment write key from the app package. The ca.diagram.dialogue package stores SEGMENT_WRITE_KEY as a static value in res/raw/config.json, exposing it when the APK resources are inspected. Exploitation requires low-privileged local access; the published assessment limits impact to credential disclosure, with no integrity or availability loss.
The record
- CVE
- CVE-2026-5455
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- Dialogue Health Technologies Inc.
- Product
- Dialogue
- Classifications
- CWE-320, CWE-321, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=4.3.0
- Affected versionversion=4.3.1
- Affected versionversion=4.3.2
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Segment Write Key Exposure proof of conceptproof of concept · unverified
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