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

GHSA-vpf5-82c8-9v36

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

GHSA-vpf5-82c8-9v36 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in algoliasearch-helper. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-vpf5-82c8-9v36 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in algoliasearch-helper

Also known asCVE-2021-23433
Published
Nov 23, 2021
Updated
Mar 13, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Mar 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦algoliasearch-helper

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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.2
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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 GHSA-vpf5-82c8-9v36 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vpf5-82c8-9v36 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vpf5-82c8-9v36. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-vpf5-82c8-9v36 in your dependencies?

O3 detects GHSA-vpf5-82c8-9v36 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-vpf5-82c8-9v36: Prototype Pollution in… | O3 Security