Summary
Workarounds
If you cannot upgrade immediately, you can avoid the problem by using field level security (FLS) protection on fields of the affected types instead of field masking.
Impact
OpenSearch versions 2.19.2 and earlier improperly apply field masking rules on fields of the types ip, geo_point, geo_shape, xy_point, xy_shape. While the content of these fields is properly redacted in the _source document returned by search operations, the original unredacted values remain available to search queries. This allows to reconstruct the original field contents using range queries.
Additionally, the content of fields of type geo_point, geo_shape, xy_point, xy_shape is returned in an unredacted form if requested via the fields option of the search API.
GHSA-RRMM-WQ7Q-H4V5 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-RRMM-WQ7Q-H4V5? GHSA-RRMM-WQ7Q-H4V5 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-RRMM-WQ7Q-H4V5? GHSA-RRMM-WQ7Q-H4V5 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-RRMM-WQ7Q-H4V5? org.opensearch.plugin:opensearch-security (maven) versions < 2.19.3.0 is affected.
- Is there a fix for GHSA-RRMM-WQ7Q-H4V5? Yes. GHSA-RRMM-WQ7Q-H4V5 is fixed in 2.19.3.0. Upgrade to this version or later.
- Is GHSA-RRMM-WQ7Q-H4V5 exploitable, and should I be worried? Whether GHSA-RRMM-WQ7Q-H4V5 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-RRMM-WQ7Q-H4V5 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-RRMM-WQ7Q-H4V5? Upgrade
org.opensearch.plugin:opensearch-securityto 2.19.3.0 or later.