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

merge vulnerable to Prototype PollutionGHSA-cqqh-49mx-fq63

CRITICALFix: viking04/merge@baba403

GHSA-cqqh-49mx-fq63 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in @viking04/merge. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @viking04/merge — see the affected versions and patch details below.

Also known asCVE-2021-3645
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.64%1.29%1.93%0.5%1.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-cqqh-49mx-fq63 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@viking04/mergenpm
52downloads / week

Description

merge is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@viking04/mergeall versions1.0.2npm install @viking04/merge@1.0.2

Affected Products

1 product · 1 configurations
Application
mergemerge_project
< 1.0.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

merge is vulnerable to Improperly Controlled Modification of Object Prot…

huntr.devNVDSep 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update @viking04/merge to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cqqh-49mx-fq63 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.

Frequently Asked Questions

merge is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
O3 Security · Impact-Aware SCA

Is GHSA-cqqh-49mx-fq63 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
merge vulnerable to Prototype Pollution (Critical 9.8)