# OpenSearch unauthorized data access on fields protected by field level security if field is a member of an object

Advisory record · `GHSA-2rjv-cv85-xhgm`

- **Identifiers:** `GHSA-2rjv-cv85-xhgm`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 1 Aug 2025
- **Updated:** 1 Aug 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Aug 2025, 18:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.opensearch.plugin:opensearch-security` (Maven): affected `<2.19.3.0`; fixed in `2.19.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The opensearch-security plugin (Maven org.opensearch.plugin:opensearch-security) before 2.19.3.0 does not properly apply Field Level Security to fields nested inside JSON objects. When an FLS exclusion is set on an object, the object is removed from search and get results, but its member fields remain searchable. An attacker with search access can use range queries to reconstruct the hidden field contents. Upgrade to 2.19.3.0 or later. As a workaround, add an exclusion rule for the object's members (for example, object.\*) alongside the existing exclusion.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.7 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2rjv-cv85-xhgm)

## Sources

- [GitHub Advisory Database: GHSA-2rjv-cv85-xhgm](https://github.com/advisories/GHSA-2rjv-cv85-xhgm)
- [OSV: GHSA-2rjv-cv85-xhgm](https://osv.dev/vulnerability/GHSA-2rjv-cv85-xhgm)
- <https://github.com/opensearch-project/security/security/advisories/GHSA-2rjv-cv85-xhgm>
- <https://github.com/opensearch-project/security>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2rjv-cv85-xhgm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2rjv-cv85-xhgm/>. Everything for agents: <https://agentprime.io/llms.txt>.