GHSA-27f5-xjrr-q9ff
CRITICALMalware in @opensearch-project/opensearch
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@opensearch-project/opensearchnpmDescription
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/New_York) |
|---|---|---|
| 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 considered fully compromised. Steps should immediately be taken to prevent further compromise.
- All secrets and keys stored on that computer should be rotated immediately from an alternate system.
- The affected packages should be removed immediately, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
References
GHSA-g7cv-rxg3-hmpx https://github.com/TanStack/router/issues/7383
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @opensearch-project/opensearch | all versions | No fix |
| 📦npm | @opensearch-project/opensearch | all versions | No fix |
| 📦npm | @opensearch-project/opensearch | all versions | No fix |
| 📦npm | @opensearch-project/opensearch | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @opensearch-project/opensearch. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of @opensearch-project/opensearch has shipped for GHSA-27f5-xjrr-q9ff yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-27f5-xjrr-q9ff is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-27f5-xjrr-q9ff. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-27f5-xjrr-q9ff in your dependencies?
O3 detects GHSA-27f5-xjrr-q9ff across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.