{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2974 exists.","fix":"No fix has been published for CVE-2026-2974 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-2974 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2974 exists.\n\nAffected product: AliasVault App. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-2974/ (Markdown: https://insights.sbomify.com/CVE-2026-2974/index.md)","id":"CVE-2026-2974","markdown":"https://insights.sbomify.com/CVE-2026-2974/index.md","name":"CVE-2026-2974","record":{"aliases":["GHSA-hx47-q2x9-r28j"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AliasVault mobile app","requires_auth":"low_privilege","summary":"Local attackers can access backup files containing API session tokens, exposing sensitive authentication data despite zero-knowledge encryption.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"aliasvault","vendor":"aliasvault"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-530","name":"Exposure of Backup File to an Unauthorized Control Sphere"},{"id":"CWE-285","name":"Improper Authorization"}],"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.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"AliasVault App Backup aliasvault.xml backup","id":"CVE-2026-2974","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"FastApiAdmin Custom Documentation Endpoint init_app.py reset_api_docs information disclosure","id":"CVE-2026-2975"},"packages":[],"prev":{"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab","id":"CVE-2026-2973"},"products":["AliasVault App"],"published":"2026-02-23","related":[{"cvss_score":9.3,"headline":"AliasVault affected by Cross-Site Scripting (XSS) via Email HTML Rendering","id":"CVE-2026-26266","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":6.1,"headline":"AliasVault is Missing Origin Validation in Android Passkey Credential Provider","id":"CVE-2026-22694","kev_date_added":null,"published":"2026-01-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["n/a"]},"summary":"Local attackers can access backup files containing API session tokens, exposing sensitive authentication data despite zero-knowledge encryption.","url":"https://insights.sbomify.com/CVE-2026-2974/"}