Answer in brief
CVE-2026-94621 records a Medium severity (CVSS 6.3) vulnerability in AliasVault: Server-Side Request Forgery via DNS rebinding in Favicon Extraction. The current sources do not mark it as known exploited. The current feed maps aliasvault/aliasvault (generic), aliasvault/ghcr.io/aliasvault/aliasvault (generic), aliasvault/ghcr.io/aliasvault/api (generic), aliasvault/ghcr.io/lanedirt/aliasvault-api (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps aliasvault/aliasvault (generic), aliasvault/ghcr.io/aliasvault/aliasvault (generic), aliasvault/ghcr.io/aliasvault/api (generic), aliasvault/ghcr.io/lanedirt/aliasvault-api (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| aliasvault/aliasvaultgeneric | <0.30.3 | 0.30.3 |
| aliasvault/ghcr.io/aliasvault/aliasvaultgeneric | <0.30.3 | 0.30.3 |
| aliasvault/ghcr.io/aliasvault/apigeneric | <0.30.3 | 0.30.3 |
| aliasvault/ghcr.io/lanedirt/aliasvault-apigeneric | <0.30.3 | 0.30.3 |
Published upstream
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.