# CVE-2026-2974: AliasVault App Backup aliasvault.xml backup

> Local attackers can access backup files containing API session tokens, exposing sensitive authentication data despite zero-knowledge encryption.

- **Severity:** Low 2.0 (`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`)
- **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:** 23 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-hx47-q2x9-r28j

## What is CVE-2026-2974?

CVE-2026-2974 is a low-severity vulnerability in AliasVault App, published on 23 Feb 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 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."

Weakness: CWE-530 (Exposure of Backup File to an Unauthorized Control Sphere), CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Aliasvault Aliasvault.

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

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

## Is CVE-2026-2974 being exploited?

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

## Other vulnerabilities in AliasVault App

- [CVE-2026-26266](https://insights.sbomify.com/CVE-2026-26266/): AliasVault affected by Cross-Site Scripting (XSS) via Email HTML Rendering (critical 9.3)
- [CVE-2026-22694](https://insights.sbomify.com/CVE-2026-22694/): AliasVault is Missing Origin Validation in Android Passkey Credential Provider (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2974 is a low-severity vulnerability in AliasVault App, published on 23 Feb 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-2974 exists.

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

## Sources

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

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