Align Technology My Invisalign App 3.12.4 on Android com.aligntech.myinvisalign.emea BuildConfig.java CDAACCESS_TOKEN hard-coded key
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Align Technology My Invisalign App 3.12.4 on Android and classified as problematic. This affects 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 results in hard-coded key. This vulnerability is cataloged as CVE-2026-5456. The attack must be initiated from a local position. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability, which was classified as problematic, was found in Align Technology My Invisalign App 3.12.4 on Android. Affected is an unknown code of the file com/aligntech/myinvisalign/BuildConfig.java of the component com.aligntech.myinvisalign.emea. The manipulation of the argument CDAACCESS_TOKEN with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality.
The advisory is shared for download at notion.so. This vulnerability is traded as CVE-2026-5456. The exploitability is told to be easy. The attack needs to be approached locally. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1600.001.
The exploit is shared for download 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.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/02/2026 VulDB entry created04/03/2026 Advisory disclosed
04/03/2026 VulDB entry last update
Sources
Advisory: notion.soStatus: Not defined
CVE: CVE-2026-5456 (🔒)
GCVE (CVE): GCVE-0-2026-5456
GCVE (VulDB): GCVE-100-355044
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 04/03/2026 00:25Changes: 04/03/2026 00:25 (59)
Complete: 🔍
Submitter: fxizenta
Cache ID: 216::103
Submit
Accepted
- Submit #781763: Align Technology My Invisalign(com.aligntech.myinvisalign.emea) 3.12.4 Contentful CDA Tokens Exposure (by fxizenta)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.