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

CVE-2021-23433 — algoliasearch-helper

CRITICALFix: algolia/algoliasearch-helper-js@4ff542b

CVE-2021-23433 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in algoliasearch-helper. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for algoliasearch-helper — see the affected versions and patch details below.

Prototype Pollution in algoliasearch-helper

Also known asGHSA-vpf5-82c8-9v36SNYK-JS-ALGOLIASEARCHHELPER-1570421
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk
0.00%0.71%1.42%2.13%0.2%1.6%May 26Sep 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.

58other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
algoliasearch-helpernpm
3.3Mdownloads / week

Description

The package algoliasearch-helper before 3.6.2 are vulnerable to Prototype Pollution due to use of the merge function in src/SearchParameters/index.jsSearchParameters._parseNumbers without any protection against prototype properties. Note that this vulnerability is only exploitable if the implementation allows users to define arbitrary search patterns.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmalgoliasearch-helperall versions3.6.2npm install algoliasearch-helper@3.6.2

Affected Products

1 product · 1 configurations
Application
algoliasearch-helperalgolia
< 3.6.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.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

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

The package algoliasearch-helper before 3.6.2 are vulnerable to Prototype Pollution due to use of the merge function in src/SearchParameters/index.jsSearchParameters._parseNumbers without any protection against prototype properties. Note that this vulnerability is only exploitable if the implementation allows users to define arbitrary search patterns.
O3 Security · Impact-Aware SCA

Is CVE-2021-23433 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2021-23433: algoliasearch-helper — Fixed in 3.6.2