# CVE-2026-5455: Dialogue App ca.diagram.dialogue config.json hard-coded key

> Local attackers can exploit a hard-coded cryptographic key in the Dialogue App to bypass security controls and access protected data.

- **Severity:** Medium 4.8 (`CVSS: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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-8mvv-fc8c-63jh

## What is CVE-2026-5455?

CVE-2026-5455 is a medium-severity vulnerability in Dialogue App, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in Dialogue App up to 4.3.2 on Android. The affected element is an unknown function of the file file res/raw/config.json of the component ca.diagram.dialogue. Executing a manipulation of the argument SEGMENT_WRITE_KEY can lead to use of hard-coded cryptographic key
 . The attack is restricted to local execution. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

## Which versions are affected by CVE-2026-5455?


## How do I fix CVE-2026-5455?

No fix has been published for CVE-2026-5455 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5455 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5455 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5455 and fix it if it is affected.

What it is: CVE-2026-5455 is a medium-severity vulnerability in Dialogue App, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5455 exists.

Affected product: Dialogue App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5455/ (Markdown: https://insights.sbomify.com/CVE-2026-5455/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5455
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5455
- OSV: https://osv.dev/vulnerability/CVE-2026-5455

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5455/
Summaries are generated and may contain mistakes; the official description above is the record.