How severe is GHSA-g5x8-v2ch-gj2g?

No CVSS score has been assigned to GHSA-g5x8-v2ch-gj2g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g5x8-v2ch-gj2g?

GHSA-g5x8-v2ch-gj2g affects the following packages: vaultwarden (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-g5x8-v2ch-gj2g?

Update vaultwarden to 1.32.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5x8-v2ch-gj2g is resolved across your whole dependency graph.

How do I detect GHSA-g5x8-v2ch-gj2g in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vaultwarden, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g5x8-v2ch-gj2g if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-g5x8-v2ch-gj2g actively exploited in the wild?

No public exploit code has been indexed for GHSA-g5x8-v2ch-gj2g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g5x8-v2ch-gj2g?

GHSA-g5x8-v2ch-gj2g has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g5x8-v2ch-gj2g?

GHSA-g5x8-v2ch-gj2g is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-g5x8-v2ch-gj2g published, and has it been updated?

GHSA-g5x8-v2ch-gj2g was published on January 9, 2025 and was last updated on January 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Vaultwarden HTML injection vulnerabilityGHSA-g5x8-v2ch-gj2g

GHSA-g5x8-v2ch-gj2g is a Cross-site Scripting (XSS) vulnerability in vaultwarden. A fix is available for vaultwarden — see the affected versions and patch details below.

Also known asCVE-2024-55224

Published

Jan 9, 2025

Updated

Jan 9, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g5x8-v2ch-gj2g.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀vaultwarden

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

An HTML injection vulnerability in Vaultwarden prior to v1.32.5 allows attackers to execute arbitrary code via injecting a crafted payload into the username field of an e-mail message.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`vaultwarden`	all versions	1.32.5`cargo update -p vaultwarden --precise 1.32.5`

Affected Products

1 product · 1 configurations

Application

vaultwardendani-garcia

< 1.32.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vaultwarden, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vaultwarden to 1.32.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5x8-v2ch-gj2g is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

An HTML injection vulnerability in Vaultwarden prior to v1.32.5 allows attackers to execute arbitrary code via injecting a crafted payload into the username field of an e-mail message.

O3 Security · Impact-Aware SCA

Is GHSA-g5x8-v2ch-gj2g in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works