Cross-Site Scripting in serialize-javascriptGHSA-h9rv-jmmf-4pgx
MEDIUMGHSA-h9rv-jmmf-4pgx is a medium-severity (CVSS 4.2) Cross-site Scripting (XSS) vulnerability in serialize-javascript. A fix is available for serialize-javascript — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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.
serialize-javascriptnpmDescription
The serialize-javascript npm package before version 2.1.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.toString() backslash-escapes all forward slashes in regular expressions. If serialized data of regular expression objects are used in an environment other than Node.js, it is affected by this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | serialize-javascript | all versions | 2.1.1npm install serialize-javascript@2.1.1 |
Affected Products
serialize-javascriptverizonDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for serialize-javascript, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update serialize-javascript to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h9rv-jmmf-4pgx 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
In both OpenShift Container Platform (OCP) and OpenShift ServiceMesh (OSSM), the grafana and prometheus containers are behind OpenShift OAuth authentication. This restricts access to the vulnerable serialize-javascript library to authenticated users only, therefore the impact is low.
| Product | Fixed in | Advisory |
|---|---|---|
| OpenShift Service Mesh 1.1 | servicemesh-grafana-0:6.4.3-11.el8 | RHSA-2020:2796 |
| Red Hat OpenShift Container Platform 4.6 | openshift4/ose-grafana:v4.6.0-202010061132.p0 | RHSA-2020:4298 |
Frequently Asked Questions
Is GHSA-h9rv-jmmf-4pgx in your dependencies?
Find it across npm, including transitive dependencies.