Which versions of OpenSearch SQL are affected by EUVD-2026-58178?

OpenSearch SQL plugin (CVE-2026-18428) allows authenticated users to execute code on analytics infrastructure with no publicly available exploits identified at time of analysis, but the attack…. A patch is available.

How to fix or mitigate EUVD-2026-58178?

Within 24 hours, inventory all OpenSearch deployments running SQL plugin/Flint extension and document current versions; review audit logs for async query activity from user accounts to establish baseline of legitimate versus suspicious access patterns. Within 7 days, apply patches upgrading to OpenSearch 3.7.0 (current release) or 2.19.6 (legacy branch); validate Spark worker connectivity and SQL query functionality post-upgrade. Within 30 days, implement role-based access control restrictions limiting SQL async queries to authorized personnel only, conduct comprehensive review and remediation of excessive user permissions, and deploy continuous monitoring to detect anomalous query patterns targeting analytics infrastructure.

OpenSearch SQL EUVD-2026-58178

Q: What is the CVSS score of EUVD-2026-58178?

EUVD-2026-58178 has a CVSS 4.0 base score of 8.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.7%.

| CVE-2026-18428 HIGH

Protection Mechanism Failure (CWE-693)

2026-08-13 AMZN

GHSA-3rvx-fcj6-wr45

RCE Apache Github AWS Opensearch

8.7

CVSS 4.0 · Vendor: AMZN

Severity by source

Vendor (AMZN) PRIMARY

8.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.9 CRITICAL

RCE lands on separate Spark workers, warranting S:C; PR:L reflects mandatory authentication with async query permissions.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H

Primary rating from Vendor (AMZN).

CVSS VectorVendor: AMZN

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 13, 2026 - 18:24 vuln.today

CVE Published

Aug 13, 2026 - 17:32 cve.org

HIGH 8.7

DescriptionCVE.org

A SQL query validation bypass in the Flint extension query handler in the OpenSearch SQL plugin allows a remote authenticated actor with async query access to execute arbitrary code on Apache Spark workers by sending a crafted SQL query to the direct query endpoint.

Articles & Coverage 1

News 3 New Apache Vulnerabilities - 1 Critical, 2 High, 1 With POC Aug 14, 2026

AnalysisAI

Remote code execution via the OpenSearch SQL plugin's Flint extension query handler exposes Apache Spark workers to arbitrary code execution by any authenticated user holding async query access. The vulnerable component is the SQL query validation layer in the Flint extension, which fails to prevent crafted payloads from reaching and executing on Spark worker nodes. No public exploit code has been identified at time of analysis, but the network-reachable RCE primitive, low complexity, and low privilege requirement collectively make this a high-priority remediation target; vendor patches are available in OpenSearch 3.7.0 and 2.19.6.

Technical ContextAI

OpenSearch is an open-source distributed search and analytics engine (successor to Elasticsearch) maintained by AWS and the community, identified in CPEs as cpe:2.3:a:aws:opensearch and cpe:2.3:a:github:opensearch covering both the AWS-managed service and the upstream open-source distribution. The SQL plugin extends OpenSearch with SQL query capabilities, and its Flint extension integrates with Apache Spark to enable federated query execution against external data sources via the direct query endpoint. Queries submitted to this endpoint are dispatched asynchronously to Spark workers for distributed processing. CWE-693 (Protection Mechanism Failure) identifies the root cause: the query validation mechanism that is supposed to sanitize or reject malicious SQL constructs before they reach Spark can be circumvented by a specifically crafted query, allowing the attacker-controlled payload to execute directly on Spark worker nodes rather than being safely rejected at the OpenSearch layer.

RemediationAI

The primary fix is to upgrade to OpenSearch 3.7.0 (for the 3.x release line) or OpenSearch 2.19.6 (for the 2.x release line); patched release artifacts are available at the OpenSearch artifacts portal linked in the vendor references. AWS OpenSearch Service customers should apply the latest service software update as described at https://docs.aws.amazon.com/opensearch-service/latest/developerguide/service-software.html. Where immediate patching is not feasible, the most effective compensating control is to disable the Flint extension integration entirely if Apache Spark federation is not operationally required, which removes the vulnerable query handler from the attack surface; the trade-off is loss of Spark-federated query capability. A secondary compensating control is to aggressively restrict async query permissions - revoke the privilege from any account that does not operationally require it, reducing the pool of principals who can reach the vulnerable code path; this does not eliminate the vulnerability but significantly narrows exposure. Network-layer access control to the direct query endpoint (restricting which source IPs or internal services can reach it) provides additional defense-in-depth.