CVEvulnerability

CVE-2026-2974

1.1 LOW Published 2026-02-23 Modified 2026-06-17 Official page ↗
Status
Analyzed
Published
2026-02-23
Last modified
2026-06-17
Assigner
[email protected]
CVSS 4.0 ([email protected])
1.1 LOW — CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 ([email protected])
2.5 LOW — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 2.0 ([email protected])
1.0 LOW — AV:L/AC:H/Au:S/C:P/I:N/A:N
Weaknesses
CWE-285, CWE-530

Description

A vulnerability was identified in AliasVault App up to 0.25.3 on Android/iOS. This vulnerability affects unknown code 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 leads to exposure of backup file to an unauthorized control sphere. An attack has to be approached locally. The attack is considered to have high complexity. It is stated that the exploitability is difficult. The exploit is publicly available and might be used. Upgrading to version 0.26.0 is able to resolve this issue. The identifier of the patch is 873ecc03f92238e162f98a068ad56069a922b4f6/0bd662320174d8265dfe3b05a04bc13efc960532. It is recommended to upgrade the affected component. 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."

Affected configurations

• aliasvault aliasvault (<= 0.25.3)

Related

Weakness · CWE (2)

  • CWE-285 Improper Authorization weakness
  • CWE-530 Exposure of Backup File to an Unauthorized Control Sphere weakness

References