Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2024-11831 serialize-javascript

MEDIUMFix: yahoo/serialize-javascript@f27d65d

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

Also known asGHSA-76p7-773f-r4q5
Published
Feb 10, 2025
Updated
Sep 10, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

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-2024-11831 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 377,333 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

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
serialize-javascriptnpm
37.2Mdownloads / week

Description

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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmserialize-javascript6.0.0&&< 6.0.26.0.2npm install serialize-javascript@6.0.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-11831 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-11831. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

Red HatModerate
ProductFixed inAdvisory
Red Hat Advanced Cluster Security 4.4advanced-cluster-security/rhacs-main-rhel8:4.4.8-2RHSA-2025:1468
Red Hat Advanced Cluster Security 4.5advanced-cluster-security/rhacs-main-rhel8:4.5.6-2RHSA-2025:1334
Red Hat Ceph Storage 7.1ceph-2:18.2.1-381.el8cpRHSA-2026:2769
Red Hat Ceph Storage 8.1ceph-2:19.2.1-292.el9cpRHSA-2025:21068
Red Hat Ceph Storage 9.0ceph-2:20.1.0-144.el10cpRHSA-2026:1536
Red Hat Enterprise Linux 8dotnet8.0-0:8.0.112-1.el8_10RHSA-2025:0381
Red Hat Enterprise Linux 9dotnet8.0-0:8.0.112-1.el9_5RHBA-2025:0304
RHODF-4.14-RHEL-9odf4/ocs-client-console-rhel9:v4.14.18-2RHSA-2025:8551

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-11831 in your dependencies?

O3 Security finds CVE-2024-11831 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2024-11831: serialize (Medium 5.4) | O3 Security