GHSA-2rjv-cv85-xhgm
MEDIUMOpenSearch unauthorized data access on fields protected by field level security if field is a member of an object
Blast Radius
org.opensearch.plugin:opensearch-securityReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
OpenSearch versions 2.19.2 and earlier improperly apply Field Level Security (FLS) rules on fields which are not at the top level of the source document tree (i.e., which are members of a JSON object).
If an FLS exclusion rule (like ~object) is applied to an object valued attribute in a source document, the object is properly removed from the _source document in search and get results. However, any member attribute of that object remains available to search queries. This allows to reconstruct the original field contents using range queries.
Patches
The issue has been resolved in OpenSearch 3.0.0 and OpenSearch 2.19.3.
Workarounds
If FLS exclusion rules are used for object valued attributes (like ~object), add an additional exclusion rule for the members of the object (like ~object.*).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opensearch.plugin:opensearch-security | all versions | 2.19.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch.plugin:opensearch-security. 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.
Fix
Update org.opensearch.plugin:opensearch-security to 2.19.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2rjv-cv85-xhgm is resolved across your whole dependency graph.
Workarounds
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-2rjv-cv85-xhgm 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-2rjv-cv85-xhgm. 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-2rjv-cv85-xhgm in your dependencies?
O3 detects GHSA-2rjv-cv85-xhgm across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.