AliasVault App up to 0.25.3 on Android/iOS Backup aliasvault.xml backup
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in AliasVault App up to 0.25.3 on Android/iOS. This issue affects some unknown processing of the file shared_prefs/aliasvault.xml of the component Backup Handler. The manipulation of the argument accessToken/refreshToken/metadata/key_derivation_params/auth_methods results in backup. This vulnerability is known as CVE-2026-2974. Attacking locally is a requirement. Furthermore, an exploit is available. Upgrading the affected component is advised. The creator of the software explains: "Because of AliasVault's zero-knowledge encryption design, the tokens stored in aliasvault.xml are API session tokens that cannot decrypt the vault on their own: the master password is required for that. So while this isn't a direct vault compromise risk, there's no reason to include them in backups either."
Details
A vulnerability, which was classified as problematic, was found in AliasVault App up to 0.25.3 on Android/iOS. Affected is an unknown function of the file shared_prefs/aliasvault.xml of the component Backup Handler. The manipulation of the argument accessToken/refreshToken/metadata/key_derivation_params/auth_methods with an unknown input leads to a backup vulnerability. CWE is classifying the issue as CWE-530. A backup file is stored in a directory or archive that is made accessible to unauthorized actors. This is going to have an impact on confidentiality.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-2974. The exploitability is told to be difficult. The attack needs to be approached locally. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The creator of the software explains: "Because of AliasVault's zero-knowledge encryption design, the tokens stored in aliasvault.xml are API session tokens that cannot decrypt the vault on their own: the master password is required for that. So while this isn't a direct vault compromise risk, there's no reason to include them in backups either." By approaching the search of inurl:shared_prefs/aliasvault.xml it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.26.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 873ecc03f92238e162f98a068ad56069a922b4f6/0bd662320174d8265dfe3b05a04bc13efc960532 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 2.5VulDB Meta Temp Score: 2.4
VulDB Base Score: 2.5
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 2.5
CNA Vector: 🔒
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: BackupCWE: CWE-530 / CWE-285 / CWE-266
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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: AliasVault App 0.26.0
Patch: 873ecc03f92238e162f98a068ad56069a922b4f6/0bd662320174d8265dfe3b05a04bc13efc960532
Timeline
02/22/2026 Advisory disclosed02/22/2026 VulDB entry created
03/12/2026 VulDB entry last update
Sources
Advisory: 1497Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-2974 (🔒)
GCVE (CVE): GCVE-0-2026-2974
GCVE (VulDB): GCVE-100-347340
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 02/22/2026 15:52Updated: 03/12/2026 19:00
Changes: 02/22/2026 15:52 (64), 02/23/2026 08:08 (30), 03/12/2026 19:00 (1)
Complete: 🔍
Submitter: nmaochea
Cache ID: 216::103
Submit
Accepted
- Submit #756058: AliasVault v0.25.3 Insecure Storage of Sensitive Information (by nmaochea)
Duplicate
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.