CVE-2026-47160
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVaultwarden is a Bitwarden-compatible server written in Rust. Prior to 1.36.0, Vaultwarden's /icons/{domain}/icon.png endpoint used src/http_client.rs checks including should_block_address() and post_resolve() that missed decimal, hexadecimal, and octal IP representations, allowing SSRF through the icon-fetching HTTP client for blind internal network or port discovery. This issue is fixed in version 1.36.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVaultwarden's icon-fetching endpoint at /icons/{domain}/icon.png contains SSRF vulnerability due to incomplete IP address validation in http_client.rs. The should_block_address() and post_resolve() functions fail to block decimal, hexadecimal, and octal IP representations, allowing attackers to bypass blocklists and probe internal network services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Vaultwarden versionCheck the running Vaultwarden container image tag, or check the binary version with 'vaultwarden --version' or by examining the Docker/container metadataAffected if The installed version is earlier than 1.36.0
-
Verify icon endpoint is accessibleConfirm the /icons/{domain}/icon.png endpoint is reachable from the network. This is the vulnerable attack surface.Affected if The icon endpoint is exposed and responds to requests (even if only internally)
-
Check for alternative IP format handling in configurationReview Vaultwarden's configuration files and environment variables for any network restrictions or PROXY settings. The vulnerability exists in the http_client.rs IP validation routines.Affected if No additional IP validation layers are implemented beyond Vaultwarden's built-in should_block_address() function, which is known to be incomplete in versions before 1.36.0
-
Compare against affected version rangeDocument the exact Vaultwarden version and compare it to the fixed version 1.36.0Affected if The version is below 1.36.0 and the icon-fetching feature is enabled
A user is affected if Vaultwarden version is below 1.36.0 and the icon endpoint at /icons/{domain}/icon.png is accessible, since the built-in IP address validation in http_client.rs fails to block decimal, hexadecimal, and octal IP representations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Vaultwarden to version 1.36.0 or later, which implements proper validation of alternative IP address formats in the icon-fetching HTTP client.
1.36.0
- Identify the current Vaultwarden version currently running (e.g., check docker image tag or binary version)
- Upgrade Vaultwarden to version 1.36.0 or later
- Verify the upgrade was successful by checking the version
- Confirm the /icons/{domain}/icon.png endpoint now properly blocks decimal, hexadecimal, and octal IP representations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47160 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data