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

CVE-2021-32736 — think-helper

HIGH

CVE-2021-32736 is a high-severity (CVSS 7.5) CWE-1321 vulnerability in think-helper. A fix is available for think-helper — see the affected versions and patch details below.

Prototype Pollution in think-helper

Also known asGHSA-vr5m-3h59-7jcp
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk
0.00%0.50%1.01%1.51%0.2%1.0%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2021-32736 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.

125other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
think-helpernpm
3Kdownloads / week

Description

Impact

The software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

Patches

[email protected] patched it, anyone used think-helper should upgrade to >=1.1.3 version.

References

https://cwe.mitre.org/data/definitions/1321.html

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmthink-helperall versions1.1.3npm install think-helper@1.1.3

Affected Products

1 product · 1 configurations
Application
think-helperthinkjs
< 1.1.3
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 think-helper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update think-helper to 1.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32736 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

### Impact The software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. ### Patches `[email protected]` patched it, anyone used `think-helper` should upgrade to `>=1.1.3` version. ### References https://cwe.mitre.org/data/definitions/1321.html ### For more information If you have any questions or comments about this advisory: * Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs) * Email us at [[email protected]](mailt
O3 Security · Impact-Aware SCA

Is CVE-2021-32736 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-32736: think-helper — Fixed in 1.1.3