Algolia Search & Discovery for Magento 2 Has Untrusted Data Handling

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Versions of the Algolia Search & Discovery extension for Magento 2 prior to 3.17.2 and 3.16.2 contain a vulnerability where data read from the database was treated as a trusted source during job execution. If an attacker is able to modify records used by the extension’s indexing queue, this could result in arbitrary PHP code execution when the affected job is processed. Exploitation requires the ability to write malicious data to the Magento database and for the indexing queue to be enabled. --- Patches This vulnerability has been fixed in the following versions: - 3.17.2 - 3.16.2 Merchants should upgrade to a supported patched version immediately. Versions outside the supported maintenance window do not receive security updates and remain vulnerable. --- Workarounds Upgrading to a patched version is the only recommended remediation. If an immediate upgrade is not possible, the following temporary risk mitigations may reduce exposure: - Disable the Algolia indexing queue to…

Published by the source

14 Jan 2026, 21:46 UTC

Last modified by the source

15 Jan 2026, 06:02 UTC

Source last checked

26 Oct 2026, 14:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-595p-g7xc-c333

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-595p-g7xc-c333

Advisory: Algolia Search & Discovery for Magento 2 Has Untrusted Data Handling
IDs: GHSA-595p-g7xc-c333
Record: https://patchnext.com/advisories/ghsa-595p-g7xc-c333 (revision 1, source checked 26 Oct 2026, 14:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: algolia/algoliasearch-magento-2 3.17.2, 3.16.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist algolia/algoliasearch-magento-2: affected >= 3.17.0-beta.1, <= 3.17.1; <= 3.16.1; fixed in 3.17.2, 3.16.2

## Suggested inspection (read-only)
- Packagist algolia/algoliasearch-magento-2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on algolia/algoliasearch-magento-2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-595p-g7xc-c333 (GitHub-reviewed advisory GHSA-595p-g7xc-c333 lists affected ranges: Packagist algolia/algoliasearch-magento-2 >=3.17.0-beta.1 =0 <=3.16.1)

Commands are suggestions: review each one before running it.