● Critical · CVSS 9.3

How to Fix CVE-2026-26266: Cross-site scripting in aliasvault

Q: What is the CVSS score for CVE-2026-26266?

9.3 (Critical). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`.

Q: Where is the official advisory for CVE-2026-26266?

The vendor advisory is at [https://github.com/aliasvault/aliasvault/security/advisories/GHSA-f65p-p65r-g53q](https://github.com/aliasvault/aliasvault/security/advisories/GHSA-f65p-p65r-g53q). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-26266.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-26266 is a cross-site scripting in aliasvault aliasvault. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	9.3 (Critical)
Actively exploited?	No public listing in CISA KEV
Affected	aliasvault < 0.26.0
Fixed in	See vendor advisory
Type (CWE)	CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

What is CVE-2026-26266?

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. The CVSS base score is 9.3 (Critical), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at [https://github.com/aliasvault/aliasvault/security/advisories/GHSA-f65p-p65r-g53q.

Am I affected?

Check the version of aliasvault you are running and compare it against the Affected row above (aliasvault < 0.26.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s aliasvault 2>/dev/null | grep -i ^Version
rpm -q aliasvault 2>/dev/null
command -v aliasvault >/dev/null && aliasvault --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*aliasvault*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "aliasvault" 2>$null

How to fix CVE-2026-26266

Upgrade aliasvault to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade aliasvault
dpkg -s aliasvault | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh aliasvault -y
# or for older releases:
sudo yum update aliasvault -y
rpm -q aliasvault

SUSE / openSUSE


sudo zypper refresh
sudo zypper update aliasvault
rpm -q aliasvault

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-26266 affecting aliasvault
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-26266-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*aliasvault*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\aliasvault-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\aliasvault" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "aliasvault" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "aliasvault"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-26266 affecting aliasvault
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-26266-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s aliasvault 2>/dev/null | grep -i ^Version || echo "aliasvault not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q aliasvault || echo "aliasvault not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-26266-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/aliasvault /etc/aliasvault.d /etc/aliasvault.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y aliasvault
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y aliasvault
elif command -v yum >/dev/null; then
    yum update -y aliasvault
elif command -v zypper >/dev/null; then
    zypper --non-interactive update aliasvault
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s aliasvault 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q aliasvault
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-26266" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-26266"

Disable the affected service (Linux)


sudo systemctl stop aliasvault 2>/dev/null || true
sudo systemctl disable aliasvault 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s aliasvault 2>/dev/null | grep -i ^Version
rpm -q aliasvault 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*aliasvault*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-2464: Path Traversal in AMR Printer Management Beta web service — Path Traversal in AMR Printer Management Beta web service
How to Fix CVE-2026-5705: code-projects Online Hotel Booking Booking Endpoint booknow.php cross site scripting — code-projects Online Hotel Booking Booking Endpoint booknow.php cross site scripting
How to Fix CVE-2026-39970: Cross-Site Scripting in typebot.io , Cross-Site Scripting in typebot.io
How to Fix CVE-2026-24999: Critical Vulnerability in Alma , Critical Vulnerability in Alma
How to Fix CVE-2026-47317: Critical Vulnerability in Escargot , Critical Vulnerability in Escargot

Is CVE-2026-26266 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-26266?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-26266?

9.3 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N.

Where is the official advisory for CVE-2026-26266?

The vendor advisory is at https://github.com/aliasvault/aliasvault/security/advisories/GHSA-f65p-p65r-g53q. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-26266.

References

Official vendor advisory: https://github.com/aliasvault/aliasvault/security/advisories/GHSA-f65p-p65r-g53q
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26266
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/aliasvault/aliasvault/commit/382e2e96fa502891638a48404f6d82dc972ab481
Additional reference: https://github.com/aliasvault/aliasvault/releases/tag/0.26.0

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*