CVE-2025-3193: Prototype Pollution in algoliasearch-helper
Versions of the package algoliasearch-helper from 2.0.0-rc1 and before 3.11.2 are vulnerable to Prototype Pollution in the _merge() function in merge.js, which allows constructor.prototype to be written even though doing so throws an error. In the "extreme edge-case" that the resulting error is caught, code injected into the user-supplied search parameter may be exeucted. This is related to but distinct from the issue reported in [CVE-2021-23433](https://security.snyk.io/vuln/SNYK-JS-ALGOLIASEARCHHELPER-1570421). **NOTE:** This vulnerability is not exploitable in the default configuration of InstantSearch since searchParameters are not modifiable by users.
AI Analysis
Technical Summary
CVE-2025-3193 describes a prototype pollution vulnerability in the algoliasearch-helper package affecting versions from 2.0.0-rc1 up to but not including 3.11.2. The vulnerability arises in the _merge() function within merge.js, where constructor.prototype can be overwritten despite an error being thrown. In rare cases where the error is caught, this can lead to execution of code injected via user-supplied search parameters. This issue is related but distinct from CVE-2021-23433. The default configuration of InstantSearch is not vulnerable as it does not allow user modification of searchParameters.
Potential Impact
The vulnerability allows prototype pollution which can lead to arbitrary code execution if the error thrown by writing constructor.prototype is caught and the injected code is executed. However, in the default InstantSearch configuration, this attack vector is not exploitable because user input cannot modify searchParameters. There are no known exploits in the wild at this time.
Mitigation Recommendations
No official patch or fix is explicitly stated in the provided data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should verify if they are using affected versions (2.0.0-rc1 and versions before 3.11.2) and consider upgrading to a fixed version once available. Additionally, ensure that user input cannot modify searchParameters or that error handling does not allow execution of injected code.
CVE-2025-3193: Prototype Pollution in algoliasearch-helper
Description
Versions of the package algoliasearch-helper from 2.0.0-rc1 and before 3.11.2 are vulnerable to Prototype Pollution in the _merge() function in merge.js, which allows constructor.prototype to be written even though doing so throws an error. In the "extreme edge-case" that the resulting error is caught, code injected into the user-supplied search parameter may be exeucted. This is related to but distinct from the issue reported in [CVE-2021-23433](https://security.snyk.io/vuln/SNYK-JS-ALGOLIASEARCHHELPER-1570421). **NOTE:** This vulnerability is not exploitable in the default configuration of InstantSearch since searchParameters are not modifiable by users.
CVSS v3.1
Score 7.5high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-3193 describes a prototype pollution vulnerability in the algoliasearch-helper package affecting versions from 2.0.0-rc1 up to but not including 3.11.2. The vulnerability arises in the _merge() function within merge.js, where constructor.prototype can be overwritten despite an error being thrown. In rare cases where the error is caught, this can lead to execution of code injected via user-supplied search parameters. This issue is related but distinct from CVE-2021-23433. The default configuration of InstantSearch is not vulnerable as it does not allow user modification of searchParameters.
Potential Impact
The vulnerability allows prototype pollution which can lead to arbitrary code execution if the error thrown by writing constructor.prototype is caught and the injected code is executed. However, in the default InstantSearch configuration, this attack vector is not exploitable because user input cannot modify searchParameters. There are no known exploits in the wild at this time.
Mitigation Recommendations
No official patch or fix is explicitly stated in the provided data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should verify if they are using affected versions (2.0.0-rc1 and versions before 3.11.2) and consider upgrading to a fixed version once available. Additionally, ensure that user input cannot modify searchParameters or that error handling does not allow execution of injected code.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- snyk
- Date Reserved
- 2025-04-03T10:26:27.920Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68d87cd25d6228f86ddc92bb
Added to database: 09/28/2025, 00:09:54 UTC
Last enriched: 08/14/2026, 15:46:23 UTC
Last updated: 09/10/2026, 19:36:50 UTC
Views: 396
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.