# CVE-2026-5456: Align Technology My Invisalign App com.aligntech.myinvisalign.emea BuildConfig.java hard-coded key

> A hardcoded cryptographic key in the My Invisalign Android app allows local attackers to bypass security controls and potentially access sensitive 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-cqgp-9jf3-3w3c

## What is CVE-2026-5456?

CVE-2026-5456 is a medium-severity vulnerability in My Invisalign 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 identified in Align Technology My Invisalign App 3.12.4 on Android. The impacted element is an unknown function of the file com/aligntech/myinvisalign/BuildConfig.java of the component com.aligntech.myinvisalign.emea. The manipulation of the argument CDAACCESS_TOKEN leads to use of hard-coded cryptographic key
 . The attack must be carried out locally. The exploit is publicly available and might be used. 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-5456?


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

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

## Is CVE-2026-5456 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5456 is a medium-severity vulnerability in My Invisalign 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-5456 exists.

Affected product: My Invisalign 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-5456/ (Markdown: https://insights.sbomify.com/CVE-2026-5456/index.md)
```

## Sources

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

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