Skip to content
Noroxi
OSV ecosystem advisory

GHSA-x83w-23jp-g6pw: OpenSearch Security plugin: DLS not applied on documents linked by has_child or has_parent relation

MediumCVSS 5.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: org.opensearch.plugin:opensearch-security (Maven) 2.19.4.0, 3.2.0.0.

Low priority for now. Upgrade to org.opensearch.plugin:opensearch-security (Maven) 2.19.4.0, 3.2.0.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

### Description A flaw was identified in the OpenSearch Security plugin's document-level security (DLS) implementation. DLS restrictions were not correctly applied to search queries that use has_parent or has_child join relations. This could allow an authenticated user to access document contents that should have been restricted by DLS rules. ### Impact An authenticated user with access to an index containing parent/child join relations could bypass DLS restrictions on documents linked by those relations, potentially accessing restricted document contents. This only affects clusters that use both DLS and the `join` field type on the same index. ### Patches This issue is fixed in OpenSearch `2.19.4` and `3.2.0`. ### Workarounds Avoid using the `join` field type on indices that are subject to DLS rules.

Published
May 7, 2026
Updated
May 7, 2026
EPSS
—

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-x83w-23jp-g6pw

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Mavenorg.opensearch.plugin:opensearch-security

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.opensearch.plugin:opensearch-securityfrom 1.0.0 · before 2.19.4.02.19.4.0
Mavenorg.opensearch.plugin:opensearch-securityfrom 3.0.0 · before 3.2.0.03.2.0.0

Other highest-scoring records for the same primary product.

  • GHSA-8wx3-324g-w4qqOpenSearch uncontrolled resource consumption
    30Monitor
  • GHSA-2rjv-cv85-xhgmOpenSearch unauthorized data access on fields protected by field level security if field is a member of an object
    22Monitor
  • GHSA-rrmm-wq7q-h4v5OpenSearch unauthorized data access on fields protected by field masking for fields of type ip, geo_point, geo_shape, xy_point, xy_shape
    22Monitor

Published before and after this one in the same product

  • ← EarlierGHSA-83x9-vc3c-hghcMay 7, 2026 · OpenSearch has a bypass of REST Layer Authorization Using Malformed Paths
    14Monitor
  • ← EarlierGHSA-22vx-2x23-98w6May 7, 2026 · OpenSearch vulnerable to improper authorization for Rollover Requests
    8Monitor
  • Later →GHSA-x5hg-x4gv-j98mMay 7, 2026 · OpenSearch has ineffective TLS certificate hostname verification
    8Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.opensearch.plugin:opensearch-security2.19.4.0Package registry (OSV)
Maven:org.opensearch.plugin:opensearch-security3.2.0.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • GHSA-83x9-vc3c-hghc0 days apartOpenSearch has a bypass of REST Layer Authorization Using Malformed Paths
    14Monitor
  • GHSA-22vx-2x23-98w60 days apartOpenSearch vulnerable to improper authorization for Rollover Requests
    8Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records