CVE-2026-47160 dani-garcia CVE debrief

Who should care

Defenders managing Vaultwarden instances, especially those exposed to internal networks, should assess their exposure and ensure remediation. This includes reviewing instance configurations, verifying version numbers, and implementing compensating controls where necessary. Additionally, security teams should monitor for potential SSRF attacks on internal networks and review relevant monitoring, detection, and logs for exposed assets.

Why it matters

This SSRF vulnerability in Vaultwarden allows for potential discovery of internal network or port information, posing a risk to defenders managing exposed instances.

• Potential for blind internal network or port discovery.
• Risk of unauthorized access to internal resources.
• Need for verification of Vaultwarden instance exposure and version.

Technical summary

The /icons/{domain}/icon.png endpoint in Vaultwarden prior to version 1.36.0 was vulnerable to SSRF due to improper checks for IP representations, allowing for blind internal network or port discovery. The vulnerability was caused by a lack of proper validation of IP addresses, which could be bypassed using decimal, hexadecimal, and octal IP representations. This issue was fixed in version 1.36.0 by implementing proper IP address validation. Defenders should prioritize verifying exposure of Vaultwarden instances, especially those with access to internal networks, and ensure they are running version 1.36.0 or later.

Defensive priority

Defenders should prioritize verifying exposure of Vaultwarden instances, especially those with access to internal networks, and ensure they are running version 1.36.0 or later.

Recommended defensive actions

• Verify Vaultwarden instances for exposure, especially those with access to internal networks.
• Ensure Vaultwarden instances are running version 1.36.0 or later.
• Monitor for potential SSRF attacks on internal networks.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fixed version. However, specific exploitation details or victim information are not provided. The vulnerability was publicly disclosed and fixed in version 1.36.0. There is no evidence of in-the-wild exploitation. Defenders should verify Vaultwarden instances for exposure, especially those with access to internal networks, and ensure they are running version 1.36.0 or later.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.