How severe is GHSA-9xr8-8hmc-389f?

GHSA-9xr8-8hmc-389f has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9xr8-8hmc-389f?

GHSA-9xr8-8hmc-389f affects the following packages: vant (npm). Ecosystems affected: npm.

How do I fix GHSA-9xr8-8hmc-389f?

Update vant to 2.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9xr8-8hmc-389f is resolved across your whole dependency graph.

How do I detect GHSA-9xr8-8hmc-389f in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vant. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9xr8-8hmc-389f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-9xr8-8hmc-389f?

O3 pinpoints whether GHSA-9xr8-8hmc-389f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9xr8-8hmc-389f actively exploited in the wild?

No public exploit code has been indexed for GHSA-9xr8-8hmc-389f 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.

When was GHSA-9xr8-8hmc-389f published, and has it been updated?

GHSA-9xr8-8hmc-389f was published on November 22, 2019 and was last updated on August 18, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

GHSA-9xr8-8hmc-389f

CRITICALFix: youzan/vant#4278

GHSA-9xr8-8hmc-389f is a critical-severity (CVSS 9.1) vulnerability in vant. O3 Security confirms whether GHSA-9xr8-8hmc-389f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in vant

Published

Nov 22, 2019

Updated

Aug 18, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 18, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

vantnpm

98Kdownloads / week

Description

Versions of vant prior to 2.1.8 are vulnerable to Cross-Site Scripting. The text value of the Picker component column is not sanitized, which may allow attackers to execute arbitrary JavaScript in a victim's browser.

Recommendation

Upgrade to version 2.1.8 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vant`	all versions	2.1.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vant. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update vant to 2.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9xr8-8hmc-389f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9xr8-8hmc-389f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9xr8-8hmc-389f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `vant` prior to 2.1.8 are vulnerable to Cross-Site Scripting. The text value of the `Picker` component column is not sanitized, which may allow attackers to execute arbitrary JavaScript in a victim's browser. ## Recommendation Upgrade to version 2.1.8 or later.

O3 Security · Impact-Aware SCA

Is GHSA-9xr8-8hmc-389f in your dependencies?

O3 detects GHSA-9xr8-8hmc-389f across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works