Summary
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.*).
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.
GHSA-2RJV-CV85-XHGM has a CVSS score of 5.7 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.19.3.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The issue has been resolved in OpenSearch 3.0.0 and OpenSearch 2.19.3.
Frequently Asked Questions
- What is GHSA-2RJV-CV85-XHGM? GHSA-2RJV-CV85-XHGM is a medium-severity security vulnerability in org.opensearch.plugin:opensearch-security (maven), affecting versions < 2.19.3.0. It is fixed in 2.19.3.0.
- How severe is GHSA-2RJV-CV85-XHGM? GHSA-2RJV-CV85-XHGM has a CVSS score of 5.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.opensearch.plugin:opensearch-security are affected by GHSA-2RJV-CV85-XHGM? org.opensearch.plugin:opensearch-security (maven) versions < 2.19.3.0 is affected.
- Is there a fix for GHSA-2RJV-CV85-XHGM? Yes. GHSA-2RJV-CV85-XHGM is fixed in 2.19.3.0. Upgrade to this version or later.
- Is GHSA-2RJV-CV85-XHGM exploitable, and should I be worried? Whether GHSA-2RJV-CV85-XHGM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2RJV-CV85-XHGM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2RJV-CV85-XHGM? Upgrade
org.opensearch.plugin:opensearch-securityto 2.19.3.0 or later.