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

Prototype pollution in controlled-mergeGHSA-5pg7-v24c-9rp9

HIGHFix: hlfshell/controlled-merge@5a4b2e9

GHSA-5pg7-v24c-9rp9 is a high-severity (CVSS 7.5) CWE-1321 vulnerability in controlled-merge. 1 public exploit reference exists, so weaponization risk is real. A fix is available for controlled-merge — see the affected versions and patch details below.

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

EPSS Exploitation Probability

via FIRST.org ↗
3.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk
1.78%2.55%3.31%4.07%2.3%3.6%May 26Sep 26Oct 26

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

How urgent is this, really

GHSA-5pg7-v24c-9rp9 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.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
controlled-mergenpm
101downloads / week

Description

Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmcontrolled-merge≥ 1.0.0&&< 1.3.01.3.0npm install controlled-merge@1.3.0

Affected Products

1 product · 1 configurations
Application
controlled-mergecontrolled-merge_project
≥ 1.0.0 && ≤ 1.2.0
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.

Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 t…

whitesourcesoftware.comNVDDec 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update controlled-merge to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pg7-v24c-9rp9 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

Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.
O3 Security · Impact-Aware SCA

Is GHSA-5pg7-v24c-9rp9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Prototype pollution in controlled-merge (High 7.5)