GHSA-22vx-2x23-98w6: OpenSearch vulnerable to improper authorization for Rollover Requests
Noroxi assessment
Priority: Monitor (action score 8/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. Administrator privileges are required. 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 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.
- Published
- May 7, 2026
- Updated
- May 7, 2026
- EPSS
- —
- CWE
- CWE-863
Report tools
Action score
8
Low priority for now.
- CVSS
- 8 / 40 · 2.2 / 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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| Maven | org.opensearch.plugin:opensearch-security | pkg:maven/org.opensearch.plugin/opensearch-security |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.opensearch.plugin:opensearch-security | from 1.0.0 · before 2.19.4.0 | 2.19.4.0 |
| Maven | org.opensearch.plugin:opensearch-security | from 3.0.0 · before 3.2.0.0 | 3.2.0.0 |
Same product
Maven: all recordsOther highest-scoring records for the same primary product.
- GHSA-8wx3-324g-w4qqOpenSearch uncontrolled resource consumption30Monitor
- GHSA-2rjv-cv85-xhgmOpenSearch unauthorized data access on fields protected by field level security if field is a member of an object22Monitor
- 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_shape22Monitor
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 Paths14Monitor
- Later →GHSA-x83w-23jp-g6pwMay 7, 2026 · OpenSearch Security plugin: DLS not applied on documents linked by has_child or has_parent relation21Monitor
- Later →GHSA-x5hg-x4gv-j98mMay 7, 2026 · OpenSearch has ineffective TLS certificate hostname verification8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.opensearch.plugin:opensearch-security | 2.19.4.0 | Package registry (OSV) |
| Maven:org.opensearch.plugin:opensearch-security | 3.2.0.0 | Package 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-x83w-23jp-g6pw0 days apartOpenSearch Security plugin: DLS not applied on documents linked by has_child or has_parent relation21Monitor
- GHSA-83x9-vc3c-hghc0 days apartOpenSearch has a bypass of REST Layer Authorization Using Malformed Paths14Monitor
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.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.