Security readout for executives and security teams
Plain-English summary
CVE-2025-3193 affects the JavaScript package algoliasearch-helper before 3.11.2. A prototype pollution flaw can cause availability impact and, in a narrow edge case, possible execution of code supplied through search parameters. Sources state default InstantSearch is not exploitable because users cannot modify searchParameters there.
Executive priority
Treat as high priority for internet-facing applications with custom Algolia search parameter handling. For default InstantSearch use, urgency is lower but upgrading remains the cleanest risk reduction.
Technical view
The issue is in algoliasearch-helper’s _merge() function in merge.js. It allows writes to constructor.prototype, triggering an error. If that error is caught in the specific vulnerable flow, user-supplied search parameter content may execute. It is related to, but distinct from, CVE-2021-23433.
Likely exposure
Exposure is most likely in applications using algoliasearch-helper from 2.0.0-rc1 through versions before 3.11.2, especially custom integrations where users can influence searchParameters. Default InstantSearch configurations are stated as not exploitable.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not show active exploitation. Practical exploitability appears limited by configuration and application behavior, specifically user-modifiable searchParameters and caught errors in the affected flow.
Researcher notes
Sources identify CWE-1321 prototype pollution and CVSS 7.5. The stated exploit condition is unusually narrow. Do not assume default InstantSearch exposure. No public source in the bundle confirms exploitation in the wild.
Mitigation direction
- Upgrade algoliasearch-helper to 3.11.2 or later.
- Confirm transitive dependencies do not pin a vulnerable version.
- Avoid exposing searchParameters to direct user modification.
- Review custom error handling around Algolia search parameter processing.
- Monitor Algolia and Snyk guidance for any updated remediation details.
Validation and detection
- Check package.json and lockfiles for algoliasearch-helper versions.
- Use SCA tooling to flag versions before 3.11.2.
- Confirm deployed bundles include the fixed dependency version.
- Review whether InstantSearch is default or customized.
- Inspect custom code paths that accept user-controlled search parameters.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-3193 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6snykVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://security.snyk.io/vuln/SNYK-JS-ALGOLIASEARCHHELPER-3318396CVE reference, snyk
- https://github.com/algolia/algoliasearch-helper-js/issues/922CVE reference, snyk
- https://github.com/algolia/algoliasearch-helper-js/commit/776dff23c87b0902e554e02a8c2567d2580fe12aCVE reference, snyk
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.