# CVE-2026-94621: AliasVault: Server-Side Request Forgery via DNS rebinding in Favicon Extraction

> Authenticated users can exploit DNS rebinding in the favicon extractor to force the server to make requests to internal hosts, enabling network reconnaissance.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-7hm6-fj4m-pf6f

## What is CVE-2026-94621?

CVE-2026-94621 is a medium-severity server-side request forgery vulnerability in aliasvault, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-94621?


## How do I fix CVE-2026-94621?

No fix has been published for CVE-2026-94621 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-94621 being exploited?

There is no known exploitation of CVE-2026-94621 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94621 and fix it if it is affected.

What it is: CVE-2026-94621 is a medium-severity server-side request forgery vulnerability in aliasvault, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94621 in the wild and no public exploit code.

Affected product: aliasvault. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94621/ (Markdown: https://insights.sbomify.com/CVE-2026-94621/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94621
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94621
- OSV: https://osv.dev/vulnerability/CVE-2026-94621

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94621/
Summaries are generated and may contain mistakes; the official description above is the record.