CVE-2024-11831 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in serialize-javascript. A fix is available for serialize-javascript — see the affected versions and patch details below.
Npm-serialize-javascript: cross-site scripting (xss) in serialize-javascript
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2024-11831.
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
A flaw was found in npm-serialize-javascript. The vulnerability occurs because the serialize-javascript module does not properly sanitize certain inputs, such as regex or other JavaScript object types, allowing an attacker to inject malicious code. This code could be executed when deserialized by a web browser, causing Cross-site scripting (XSS) attacks. This issue is critical in environments where serialized data is sent to web clients, potentially compromising the security of the website or web application using this package.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | serialize-javascript | ≥ 6.0.0&&< 6.0.2 | 6.0.2npm install serialize-javascript@6.0.2 |
Detection & 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 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-11831 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.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-11831 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Advanced Cluster Security 4.4 | advanced-cluster-security/rhacs-main-rhel8:4.4.8-2 | RHSA-2025:1468 |
| Red Hat Advanced Cluster Security 4.5 | advanced-cluster-security/rhacs-main-rhel8:4.5.6-2 | RHSA-2025:1334 |
| Red Hat Ceph Storage 7.1 | ceph-2:18.2.1-381.el8cp | RHSA-2026:2769 |
| Red Hat Ceph Storage 8.1 | ceph-2:19.2.1-292.el9cp | RHSA-2025:21068 |
| Red Hat Ceph Storage 9.0 | ceph-2:20.1.0-144.el10cp | RHSA-2026:1536 |
| Red Hat Enterprise Linux 8 | dotnet8.0-0:8.0.112-1.el8_10 | RHSA-2025:0381 |
| Red Hat Enterprise Linux 9 | dotnet8.0-0:8.0.112-1.el9_5 | RHBA-2025:0304 |
| RHODF-4.14-RHEL-9 | odf4/ocs-client-console-rhel9:v4.14.18-2 | RHSA-2025:8551 |
Frequently Asked Questions
Is CVE-2024-11831 in your dependencies?
Find it across npm, including transitive dependencies.