# CVE-2026-116678: Vaultwarden: Icon endpoint SSRF fix bypass via second-stage favicon IP literal URLs


- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-hw4g-2v3f-74x5

## What is CVE-2026-116678?

CVE-2026-116678 is a medium-severity vulnerability in dani-garcia vaultwarden, published on 27 Oct 2026. 

### Official description

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 get_page_with_referer() without applying should_block_host() 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.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-116678 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116678 is a medium-severity vulnerability in dani-garcia vaultwarden, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116678 in the wild and no public exploit code.

Affected product: dani-garcia vaultwarden. 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-116678/ (Markdown: https://insights.sbomify.com/CVE-2026-116678/index.md)
```

## Sources

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

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