CVE-2022-29230 is a medium-severity (CVSS 6.3) Cross-site Scripting (XSS) vulnerability in @shopify/hydrogen. A fix is available for @shopify/hydrogen — see the affected versions and patch details below.
Potential Cross-site Scripting vulnerability in Hydrogen
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-29230 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
@shopify/hydrogennpmDescription
Impact
There is a potential Cross-Site Scripting (XSS) vulnerability where an arbitrary user is able to execute scripts on pages that are built with Hydrogen. This affects all versions of Hydrogen starting from version 0.10.0 to 0.18.0. This vulnerability is exploitable in applications whose hydrating data is user controlled.
Patches
All Hydrogen users should upgrade their project to v0.19.0.
Workarounds
There is no current workaround, and users should update as soon as possible.
Additionally, the Content Security Policy is not an effective mitigation for this vulnerability.
References
GitHub: Hydrogen v0.19.0 Fix PR: https://github.com/Shopify/hydrogen/pull/1272
For more information
If you have any questions or comments about this advisory:
- Open an issue in Shopify/hydrogen
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @shopify/hydrogen | ≥ 0.10.0&&< 0.19.0 | 0.19.0npm install @shopify/hydrogen@0.19.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @shopify/hydrogen, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @shopify/hydrogen to 0.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29230 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-29230 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-29230. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-29230 in your dependencies?
O3 Security finds CVE-2022-29230 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.