LowGHSA-22vx-2x23-98w6

OpenSearch vulnerable to improper authorization for Rollover Requests

Published 7 May 2026 · Updated 7 May 2026

Is your project on an affected org.opensearch.plugin:opensearch-security?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.0.0 <2.19.4.0
Fixed in
2.19.4.0
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.opensearch.plugin:opensearch-security -DdepVersion=2.19.4.0 -DforceVersion=true
Affected
>=3.0.0 <3.2.0.0
Fixed in
3.2.0.0
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.opensearch.plugin:opensearch-security -DdepVersion=3.2.0.0 -DforceVersion=true

Details

Description

A flaw was identified in the OpenSearch Security plugin's handling of index rollover requests. When a rollover request included an explicit target index name, the security plugin did not properly evaluate access control permissions against the target index. This could allow a user with rollover permissions on a source index to create a new index with a name they are not authorized to use.

Impact

A user with indices:admin/rollover permission on a source index pattern could roll over to a target index name outside their authorized index patterns. This is limited to index creation via the rollover API and requires the user to already have rollover privileges on the source index.

Patches

This issue is fixed in OpenSearch 2.19.4 and 3.2.0

Workarounds

Grant the indices:admin/rollover permission only to fully trusted users.

Is GHSA-22vx-2x23-98w6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.opensearch.plugin:opensearch-security, and gives you the command that fixes it.

More advisories for org.opensearch.plugin:opensearch-security

  • LowGHSA-x5hg-x4gv-j98mOpenSearch has ineffective TLS certificate hostname verification · 7 May 2026
  • MediumGHSA-x83w-23jp-g6pwOpenSearch Security plugin: DLS not applied on documents linked by has_child or has_parent relation · 7 May 2026
  • LowGHSA-83x9-vc3c-hghcOpenSearch has a bypass of REST Layer Authorization Using Malformed Paths · 7 May 2026
  • MediumGHSA-2rjv-cv85-xhgmOpenSearch unauthorized data access on fields protected by field level security if field is a member of an object · 1 Aug 2025
  • MediumGHSA-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 · 1 Aug 2025
  • MediumCVE-2023-45807OpenSearch Issue with tenant read-only permissions · 17 Oct 2023
All 14 advisories for org.opensearch.plugin:opensearch-security

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.