{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26266 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26266 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26266 is a critical cross-site scripting vulnerability in aliasvault, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-26266 and fix it if it is affected.\n\nWhat it is: CVE-2026-26266 is a critical cross-site scripting vulnerability in aliasvault, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-26266 in the wild and no public exploit code.\n\nAffected product: aliasvault. 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-26266/ (Markdown: https://insights.sbomify.com/CVE-2026-26266/index.md)","id":"CVE-2026-26266","markdown":"https://insights.sbomify.com/CVE-2026-26266/index.md","name":"CVE-2026-26266","record":{"aliases":["GHSA-f65p-p65r-g53q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Password manager","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript in the victim's browser by sending crafted emails, potentially leading to account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"aliasvault","vendor":"aliasvault"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"AliasVault is a privacy-first password manager with built-in email aliasing. A stored cross-site scripting (XSS) vulnerability was identified in the email rendering feature of AliasVault Web Client versions 0.25.3 and lower. When viewing received emails on an alias, the HTML content is rendered in an iframe using srcdoc, which does not provide origin isolation. An attacker can send a crafted email containing malicious JavaScript to any AliasVault email alias. When the victim views the email in the web client, the script executes in the same origin as the application. No sanitization or sandboxing was applied to email HTML content before rendering. This vulnerability is fixed in 0.26.0.[","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"AliasVault affected by Cross-Site Scripting (XSS) via Email HTML Rendering","id":"CVE-2026-26266","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"rs-soroban-sdk #[contractimpl] macro calls inherent function instead of trait function when names collide","id":"CVE-2026-26267"},"packages":[],"prev":{"headline":"Discourse has IDOR vulnerability in the directory items endpoint","id":"CVE-2026-26265"},"products":["aliasvault"],"published":"2026-03-03","related":[{"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"},{"cvss_score":2,"headline":"AliasVault App Backup aliasvault.xml backup","id":"CVE-2026-2974","kev_date_added":null,"published":"2026-02-23"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-04","vendors":["aliasvault"]},"summary":"Attackers can execute arbitrary JavaScript in the victim's browser by sending crafted emails, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-26266/"}