# CVE-2025-3193: algoliasearch-helper is vulnerable to Prototype Pollution in _merge()

> Prototype pollution in algoliasearch-helper allows code execution via search parameters if errors are caught, requiring non-default configuration.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2025
- **Updated:** 8 Aug 2026
- **Also known as:** GHSA-529q-4j3p-7c5r

## What is CVE-2025-3193?

CVE-2025-3193 is a high-severity code injection vulnerability in algoliasearch-helper, published on 27 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-3193?

2 open source packages ship an affected version, including algoliasearch-helper. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `algoliasearch-helper` | npm | From 2.0.0-rc1 | 3.11.2 |
| `algoliasearch-helper` | npm | From 2.0.0-rc1 | 3.11.2 |

Products: Algolia Algoliasearch-Helper.

## How do I fix CVE-2025-3193?

Upgrade algoliasearch-helper to 3.11.2 or later.

## Is CVE-2025-3193 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3193 exists.

## Other vulnerabilities in algoliasearch-helper

- [CVE-2021-23433](https://insights.sbomify.com/CVE-2021-23433/): Prototype Pollution (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3193 and fix it if it is affected.

What it is: CVE-2025-3193 is a high-severity code injection vulnerability in algoliasearch-helper, published on 27 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3193 exists.

Affected packages and fixed versions:
- algoliasearch-helper (npm): affected from 2.0.0-rc1; fixed in 3.11.2
- algoliasearch-helper (npm): affected from 2.0.0-rc1; fixed in 3.11.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3193/ (Markdown: https://insights.sbomify.com/CVE-2025-3193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3193
- OSV: https://osv.dev/vulnerability/CVE-2025-3193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3193/
Summaries are generated and may contain mistakes; the official description above is the record.