CVE-2025-24364: Vaultwarden RCE Vulnerability

CVE-2025-24364 Overview

CVE-2025-24364 is a high-severity command injection vulnerability in Vaultwarden, an unofficial Bitwarden-compatible server written in Rust. An attacker with authenticated access to the Vaultwarden admin panel can execute arbitrary commands on the host system. The exploitation path abuses the admin panel's mail agent configuration to switch the transport to sendmail, then crafts a malicious favicon image containing embedded shell commands. Triggering an action such as sending a test email causes the injected commands to execute under the Vaultwarden process context. The flaw is tracked as [CWE-74] (Improper Neutralization of Special Elements in Output Used by a Downstream Component) and is fixed in Vaultwarden 1.33.0.

Critical Impact
Authenticated administrators can achieve arbitrary code execution on the Vaultwarden host, compromising the confidentiality, integrity, and availability of every credential stored in the password vault.

Affected Products

Vaultwarden versions prior to 1.33.0
dani-garcia/vaultwarden self-hosted Bitwarden-compatible server
Deployments exposing the /admin panel to authenticated administrators

Discovery Timeline

2025-01-27 - CVE-2025-24364 published to NVD
2025-01-27 - Vendor security advisory GHSA-h6cc-rc6q-23j4 published
2025-01-27 - Vaultwarden 1.33.0 released containing the fix
2025-08-20 - Last updated in NVD database

Technical Details for CVE-2025-24364

Vulnerability Analysis

Vaultwarden exposes an administrative panel that allows operators to configure SMTP and mail transport settings. The vulnerability stems from insufficient validation of the mail transport configuration combined with unsafe handling of favicon image data used in outbound email rendering. An authenticated administrator can change the mail agent from SMTP to sendmail and supply a path that resolves to a shell command rather than the expected mail binary.

When the application processes an outbound email, it retrieves and embeds favicon image data referenced by the message template. By uploading or referencing a specially crafted favicon, the attacker injects command sequences that are passed to the configured mail agent. The result is execution of attacker-controlled commands under the Vaultwarden service account, typically with full read access to the encrypted vault database and environment secrets.

Root Cause

The root cause is improper neutralization of configuration inputs that flow into a downstream command interpreter [CWE-74]. The mail agent path and arguments are treated as trusted operator input, and the favicon data path allows attacker-controlled bytes to reach the shell invocation. Vaultwarden did not separate command arguments from data, nor did it constrain the sendmail setting to a safe binary path.

Attack Vector

Exploitation requires high privileges: the attacker must already hold valid admin panel credentials or have compromised an admin session. From there, the attack is fully remote over the network. The attacker logs into /admin, switches the mail agent to sendmail, modifies the binary path and arguments, uploads or stages a malicious favicon containing embedded commands, and triggers email delivery (for example, the "Send test email" function). The shell processes the favicon-borne payload, executing arbitrary commands.

No verified public proof-of-concept code is available. See the GitHub Security Advisory GHSA-h6cc-rc6q-23j4 for the vendor's technical description.

Detection Methods for CVE-2025-24364

Indicators of Compromise

Unexpected changes to the Vaultwarden admin configuration, particularly switching SMTP to sendmail or modifying SENDMAIL_COMMAND.
Newly uploaded or modified favicon assets in the Vaultwarden cache or working directory containing non-image byte sequences.
Child processes spawned by the Vaultwarden binary that are not the expected mail transport, such as /bin/sh, bash, curl, wget, or nc.
Outbound network connections from the Vaultwarden host immediately following an admin panel session or a "test email" action.

Detection Strategies

Monitor process lineage for the vaultwarden parent process spawning shells or interpreters.
Alert on writes to mail-related configuration values from the /admin endpoint by correlating HTTP access logs with configuration file diffs.
Inspect favicon cache directories for files whose magic bytes do not match valid .ico, .png, or .jpg formats.
Review authentication logs for successful admin panel logins from unusual IP addresses or outside maintenance windows.

Monitoring Recommendations

Forward Vaultwarden container or systemd logs to a central log platform and retain admin panel access records.
Enable file integrity monitoring on the Vaultwarden configuration file and any environment files containing ADMIN_TOKEN.
Baseline expected outbound connections from the Vaultwarden host and alert on deviations following admin sessions.

How to Mitigate CVE-2025-24364

Immediate Actions Required

Upgrade Vaultwarden to version 1.33.0 or later immediately.
Rotate the ADMIN_TOKEN and any SMTP credentials stored in Vaultwarden configuration.
Audit recent admin panel activity for unauthorized configuration changes, especially to mail transport settings.
Treat any pre-patch host with admin panel exposure as potentially compromised and rebuild from a known-good image if suspicious activity is found.

Patch Information

The vulnerability is fixed in Vaultwarden 1.33.0. Release notes and the upgrade artifact are available at the Vaultwarden 1.33.0 release. Container deployments should pull the updated image tag and recreate the service. Detailed remediation guidance is documented in the GitHub Security Advisory GHSA-h6cc-rc6q-23j4.

Workarounds

Restrict access to the /admin endpoint using a reverse proxy, IP allowlisting, or VPN until the patch is applied.
Disable the admin panel by unsetting ADMIN_TOKEN if administrative functions are not actively required.
Run Vaultwarden as an unprivileged user inside a hardened container with no shell utilities present on the image.
Block outbound network egress from the Vaultwarden host to limit post-exploitation impact.

bash

# Configuration example: restrict admin panel and harden deployment
# 1. Disable the admin panel entirely when not in use
unset ADMIN_TOKEN

# 2. Pull the patched image
docker pull vaultwarden/server:1.33.0

# 3. Recreate the service
docker stop vaultwarden && docker rm vaultwarden
docker run -d --name vaultwarden \
  -e DOMAIN=https://vault.example.com \
  -v /opt/vaultwarden/data:/data \
  -p 127.0.0.1:8080:80 \
  --read-only --tmpfs /tmp \
  vaultwarden/server:1.33.0