Malware in @opensearch-project/opensearch
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @opensearch-project/opensearch
- Affected
- >= 3.5.3, <= 3.5.3>= 3.6.2, <= 3.6.2>= 3.7.0, <= 3.7.0>= 3.8.0, <= 3.8.0
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-27f5-xjrr-q9ff lists affected ranges: npm @opensearch-project/opensearch >=3.5.3 =3.6.2 =3.7.0 =3.8.0 <=3.8.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-27f5-xjrr-q9ff lists affected ranges: npm @opensearch-project/opensearch >=3.5.3 =3.6.2 =3.7.0 =3.8.0 <=3.8.0
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Overview The OpenSearch Project has sustained a security incident involving an external actor gaining force-push permissions within the project's CI infrastructure to embed malicious packages into four release versions of @opensearch-project/opensearch. Users are instructed to immediately take actions recommended in the Remediation section of this advisory. Affected Versions Package: @opensearch-project/opensearch | Version | Published (UTC) | Published (America/NewYork) | |---------|----------------|------------------------------| | 3.5.3 | 2026-05-12T00:47:39Z | May 11, 2026, 8:47:39 PM EDT | | 3.6.2 | 2026-05-12T00:29:34Z | May 11, 2026, 8:29:34 PM EDT | | 3.7.0 | 2026-05-12T00:42:29Z | May 11, 2026, 8:42:29 PM EDT | | 3.8.0 | 2026-05-12T00:43:54Z | May 11, 2026, 8:43:54 PM EDT | Remediation Any computer that has these package versions installed or updated between 00:00 UTC 12 May 2026 (8:00 PM EDT 11 May 2026) and 10:00 UTC 12 May 2026 (6:00 AM EDT 12 May 2026) should be…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-27f5-xjrr-q9ff
- Revision 2 · amended ·
Amended from osv record GHSA-27f5-xjrr-q9ff
- Revision 1 · created ·
Published from ghsa record GHSA-27f5-xjrr-q9ff
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-27f5-xjrr-q9ff Advisory: Malware in @opensearch-project/opensearch IDs: GHSA-27f5-xjrr-q9ff Record: https://patchnext.com/advisories/ghsa-27f5-xjrr-q9ff (revision 3, source checked 26 Oct 2026, 12:52 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @opensearch-project/opensearch: affected >= 3.5.3, <= 3.5.3; >= 3.6.2, <= 3.6.2; >= 3.7.0, <= 3.7.0; >= 3.8.0, <= 3.8.0 ## Suggested inspection (read-only) - `npm ls @opensearch-project/opensearch --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @opensearch-project/opensearch. - 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-27f5-xjrr-q9ff (GitHub-reviewed advisory GHSA-27f5-xjrr-q9ff lists affected ranges: npm @opensearch-project/opensearch >=3.5.3 =3.6.2 =3.7.0 =3.8.0 <=3.8.0) - Verified: https://osv.dev/vulnerability/GHSA-27f5-xjrr-q9ff (OSV record GHSA-27f5-xjrr-q9ff lists affected ranges: npm @opensearch-project/opensearch >=3.5.3 =3.6.2 =3.7.0 =3.8.0 <=3.8.0) Commands are suggestions: review each one before running it.
Loading voting…