NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

billboard.js allows prototype pollution via the function generateGHSA-65p9-j6pg-72hj

CRITICALFix: naver/billboard.js@82ea7ac

GHSA-65p9-j6pg-72hj is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in billboard.js. A fix is available for billboard.js — see the affected versions and patch details below.

Also known asCVE-2025-49223
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk+0.06%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.23%0.62%1.01%1.40%0.8%0.9%May 26Aug 26Nov 26

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

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.

51other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
billboard.jsnpm
60Kdownloads / week

Description

billboard.js before 3.15.1 was discovered to contain a prototype pollution via the function generate, which could allow attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmbillboard.jsall versions3.15.1npm install billboard.js@3.15.1

Affected Products

1 product · 1 configurations
Application
billboard.jsnaver
< 3.15.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for billboard.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update billboard.js to 3.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65p9-j6pg-72hj is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

billboard.js before 3.15.1 was discovered to contain a prototype pollution via the function generate, which could allow attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.
O3 Security · Impact-Aware SCA

Is GHSA-65p9-j6pg-72hj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
GHSA-65p9-j6pg-72hj: billboard.js RCE — Fixed in 3.15.1