CVE-2025-3193: Versions of the package algoliasearch-helper from 2.0.0-rc1 and before 3.11.2 are vulnerable to Prototype Poll

Q: How do I fix CVE-2025-3193?

algoliasearch-helper: upgrade to 3.11.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-3193 being exploited?

CVE-2025-3193 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-3193 affect?

CVE-2025-3193 affects algoliasearch-helper. Severity is high (CVSS 7.5). 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.

Q: How urgent is CVE-2025-3193?

Priority 47/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2025-3193 is a high-severity flaw (CVSS 7.5) affecting algoliasearch-helper. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-1321
Published	2025-09-27
Last modified	2026-10-19

Publisher (CNA): Snyk · Vendor: algolia

Last updated 2026-10-19 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-09-27 05:15 UTCPublished CVE record published
2026-10-19 16:10 UTCUpdated Record last modified

algolia algoliasearch-helper UPGRADE

Affected: >= 2.0.0 and < 3.11.2

Fixed in: 3.11.2

Safe to downgrade to: a release before 2.0.0

1. Check installed version

npm ls algoliasearch-helper

2. UPGRADE to 3.11.2

npm install algoliasearch-helper@">=3.11.2"

3. If no update is available yet, DOWNGRADE to a release before 2.0.0

npm view algoliasearch-helper versions npm install algoliasearch-helper@"<2.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-3193?

algoliasearch-helper: upgrade to 3.11.2. Exact commands for each OS are on this page.

Is CVE-2025-3193 being exploited?

CVE-2025-3193 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-3193 affect?

CVE-2025-3193 affects algoliasearch-helper. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2025-3193?

Priority 47/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs