GHSA-hw4g-2v3f-74x5: Vaultwarden: Icon endpoint SSRF fix bypass via second-stage favicon IP literal URLs

Published Oct 27, 2026
·
Updated

Vaultwarden is a Bitwarden-compatible server written in Rust. Prior to version 1.37.0, the Vaultwarden icon downloader validates the initial icon host and DNS results but passes favicon URLs parsed from attacker-controlled HTML to getpagewithreferer() without applying shouldblockhost() to the second-stage host. This flaw bypasses the remediation for CVE-2026-47160, which covered decimal, hexadecimal, octal, and IPv4-mapped IPv6 host normalization, because the second-stage IP-literal favicon fetch does not invoke the custom DNS resolver. A remote unauthenticated attacker can provide a public page whose favicon uses an IP-literal URL, allowing the Vaultwarden server to reach loopback or private and internal addresses. The issue affects instances with internal icon downloading enabled and can expose internal responses that resemble supported images or reveal reachability through timing, status, and cache behavior. This issue is fixed in version 1.37.0.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Vaultwarden to a version that resolves this vulnerability.

    Fixed in 1.37.0

Event History

Oct 27, 2026
CVE Published
via OSV·05:27 PM
Data Sourced
via OSV·05:27 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which Vaultwarden deployments are exposed?

Instances running a version earlier than 1.37.0 are affected if internal icon downloading is enabled. The vulnerable behavior is in the server-side icon downloader.

2

What does an attacker need to exploit this issue?

An unauthenticated remote attacker needs to provide a publicly reachable page whose favicon URL uses an IP-literal address. The Vaultwarden server then fetches that favicon, potentially reaching loopback, private, or other internal addresses.

3

What could an attacker learn or access through the vulnerable fetch?

The issue can expose internal responses if they resemble supported images. Even when response content is not usable, timing, status, and cache behavior may reveal whether internal addresses are reachable.

4

How can exposure be reduced before upgrading?

Disable internal icon downloading if patching cannot happen immediately. Upgrade Vaultwarden to version 1.37.0 to apply the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203