Dialogue App up to 4.3.2 on Android ca.diagram.dialogue config.json SEGMENT_WRITE_KEY hard-coded key

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.0$0-$5k2.85

Summaryinfo

A vulnerability has been found in Dialogue App up to 4.3.2 on Android and classified as problematic. The impacted element is an unknown function of the file file res/raw/config.json of the component ca.diagram.dialogue. The manipulation of the argument SEGMENT_WRITE_KEY leads to hard-coded key. This vulnerability is listed as CVE-2026-5455. The attack must be carried out 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, has been found in Dialogue App up to 4.3.2 on Android. This issue affects an unknown part of the file file res/raw/config.json of the component ca.diagram.dialogue. The manipulation of the argument SEGMENT_WRITE_KEY with an unknown input leads to a hard-coded key vulnerability. Using CWE to declare the problem leads to CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. Impacted is confidentiality.

It is possible to read the advisory at notion.so. The identification of this vulnerability is CVE-2026-5455. The exploitation is known to be easy. Attacking locally is a requirement. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.

The exploit is available 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. By approaching the search of inurl:file res/raw/config.json it is possible to find vulnerable targets with Google Hacking.

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

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: 🔒
Google Hack: 🔒

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/02/2026 VulDB entry created
04/03/2026 +0 days Advisory disclosed
04/03/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: notion.so
Status: Not defined

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

Entryinfo

Created: 04/03/2026 00:20
Changes: 04/03/2026 00:20 (58)
Complete: 🔍
Submitter: fxizenta
Cache ID: 216:255:103

Submitinfo

Accepted

  • Submit #781761: Dialogue Dialogue(ca.diagram.dialogue) 4.3.2 Segment Write Key Exposure (by fxizenta)

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!