How severe is CVE-2025-3193?

CVE-2025-3193 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2025-3193 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-3193?

CVE-2025-3193 affects Algolia Algoliasearch-helper. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-3193?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-3193 have an EU (EUVD) identifier?

Yes. CVE-2025-3193 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-31407.

When was CVE-2025-3193 published?

CVE-2025-3193 was published on 2025-09-27 and last updated on 2026-06-17.

CVE-2025-3193

CVE-2025-3193 is a high-severity vulnerability in Algolia Algoliasearch-helper with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1321.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (38th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-31407
Weakness: CWE-1321
Affected product: Algolia Algoliasearch-helper
Published: 2025-09-27
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-3193?: 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.
How severe is CVE-2025-3193?: CVE-2025-3193 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2025-3193 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-3193?: CVE-2025-3193 affects Algolia Algoliasearch-helper. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-3193?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-3193 have an EU (EUVD) identifier?: Yes. CVE-2025-3193 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-31407.
When was CVE-2025-3193 published?: CVE-2025-3193 was published on 2025-09-27 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:algolia:algoliasearch-helper:*:*:*:*:*:node.js:*:*

More vulnerabilities in Algolia Algoliasearch-helper

CVE-2021-23433 — Medium (CVSS 5.9): The package algoliasearch-helper before 3.6.2 are vulnerable to Prototype Pollution due to use of the merge function in…

All CVEs affecting Algolia Algoliasearch-helper →

Other CWE-1321 (Prototype Pollution) vulnerabilities

CVE-2026-25142 — Critical (CVSS 10.0): SandboxJS is a JavaScript sandboxing library. Prior to 0.8.27, SanboxJS does not properly restrict __lookupGetter__…
CVE-2024-39008 — Critical (CVSS 10.0): robinweser fast-loops v1.1.3 was discovered to contain a prototype pollution via the function objectMergeDeep. This…
CVE-2024-38999 — Critical (CVSS 10.0): jrburke requirejs v2.3.6 was discovered to contain a prototype pollution via the function s.contexts._.configure. This…
CVE-2022-29823 — Critical (CVSS 10.0): Feather-Sequalize cleanQuery method uses insecure recursive logic to filter unsupported keys from the query object.…
CVE-2022-24760 — Critical (CVSS 10.0): Parse Server is an open source http web server backend. In versions prior to 4.10.7 there is a Remote Code Execution…
CVE-2020-12079 — Critical (CVSS 10.0): Beaker before 0.8.9 allows a sandbox escape, enabling system access and code execution. This occurs because Electron…

Browse all CWE-1321 (Prototype Pollution) vulnerabilities →