CVE-2025-59344 Details
Description
AliasVault is a privacy-first password manager with built-in email aliasing. A server-side request forgery (SSRF) vulnerability exists in the favicon extraction feature of AliasVault API versions 0.23.0 and lower. The extractor fetches a user-supplied URL, parses the returned HTML, and follows <link rel="icon" href="…">. Although the initial URL is validated to allow only HTTP/HTTPS with default ports, the extractor automatically follows redirects and does not block requests to loopback or internal IP ranges. An authenticated, low-privileged user can exploit this behavior to coerce the backend into making HTTP(S) requests to arbitrary internal hosts and non-default ports. If the target host serves a favicon or any other valid image, the response is returned to the attacker in Base64 form. Even when no data is returned, timing and error behavior can be abused to map internal services. This vulnerability only affects self-hosted AliasVault instances that are reachable from the public internet with public user registration enabled. Private/internal deployments without public sign-ups are not directly exploitable. This issue has been fixed in AliasVault release 0.23.1.
A server-side request forgery (SSRF) vulnerability has been identified in the AliasVault API, specifically in versions 0.23.0 and prior. This vulnerability arises within the favicon extraction feature, which fetches a user-supplied URL, parses the HTML response, and follows links to icons. While the initial URL is validated to permit only HTTP and HTTPS protocols on default ports, the extractor automatically follows redirects without restriction, allowing requests to loopback or internal IP ranges. An authenticated, low-privileged user could exploit this to induce the server to make HTTP or HTTPS requests to arbitrary internal hosts and non-default ports. If the target host provides a favicon or any valid image, the extracted response is returned in Base64 format. Even in the absence of data, timing and error responses can be manipulated to map internal services. This vulnerability is present only in self-hosted AliasVault instances accessible from the public internet with public user registration enabled. Private deployments without public sign-ups are not directly exploitable.
Users are advised to upgrade to AliasVault version 0.23.1 or later, which patches this vulnerability by restricting favicon extraction to public IP ranges and disallowing redirects to loopback or local IPs. For self-hosted instances, public account registration can be disabled to reduce exposure.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 19, 2025CISA-ADP
Assessed Sep 19, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/aliasvault/aliasvault/commit/58c39815e4c8bb27a311c3b592d54e157b4e6968 | [email protected] | Source CodeVendor |
| https://github.com/aliasvault/aliasvault/pull/1226 | [email protected] | Issue TrackingVendor |
| https://github.com/aliasvault/aliasvault/releases/tag/0.23.1 | [email protected] | Release NotesVendor |
| https://github.com/aliasvault/aliasvault/security/advisories/GHSA-f253-f7xc-w7pj | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-918 | Server-Side Request Forgery (SSRF) | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| AliasVault | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Sep 19, 2025 | New CVE Received | [email protected] |
Volerion