CVE-2026-94621: AliasVault: Server-Side Request Forgery via DNS rebinding in Favicon Extraction
AliasVault is a privacy-first password manager with built-in email aliasing. Prior to 0.30.3, the AliasVault server API favicon extractor validates a user-supplied hostname with a first DNS lookup but allows the HTTP client to perform a second DNS lookup when connecting. An authenticated low-privileged user operating an attacker-controlled authoritative DNS server can return a public address during validation and a private address during connection, causing a publicly reachable self-hosted server to issue HTTP or HTTPS requests to internal hosts. A valid image response is returned in Base64 form, while other responses can expose limited timing and error information for internal-network reconnaissance. Exploitation requires a publicly reachable self-hosted instance with public registration enabled, an authenticated AliasVault account, an attacker-controlled authoritative DNS server, and a resolver that permits rebinding; default checks limit requests to ports 80 and 443. The browser extensions, web application, and mobile applications are not affected. This issue is fixed in version 0.30.3.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
AliasVaultto a version that resolves this vulnerability.Fixed in 0.30.3
Event History
Frequently Asked Questions
Which deployments are realistically exposed?
Publicly reachable self-hosted AliasVault Server instances running a version before 0.30.3 are exposed when public registration is enabled. Browser extensions, the web application, and mobile applications are not affected.
What does an attacker need to exploit this issue?
The attacker needs an authenticated low-privileged AliasVault account, control of an authoritative DNS server, and a resolver that permits DNS rebinding. They also need the target server to be publicly reachable and allow public registration.
What internal access can exploitation provide?
The server can be induced to send HTTP or HTTPS requests to internal hosts, with requests limited by default to ports 80 and 443. Valid image responses may be returned as Base64 data; other targets may reveal limited timing and error information useful for internal reconnaissance.
How can the issue be remediated?
Upgrade AliasVault Server to version 0.30.3, which fixes the issue. If upgrading cannot happen immediately, the provided information identifies public reachability and public registration as required exposure conditions.