Quick answers
- Is CVE-2026-63393 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63393 being exploited in the wild.
- How severe is CVE-2026-63393?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- OpenSearch Project OpenSearch SQL 2.8.0.0 through 2.19.5.0; 3.0.0.0 through 3.6.0.0.
- Is there a fix for CVE-2026-63393?
- Yes: fixed in OpenSearch SQL 2.19.6.0, 3.7.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63393 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63393?
- Check whether you run OpenSearch Project OpenSearch SQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: OpenSearch SQL 2.19.6.0, 3.7.0.0
Technical details
The vulnerability exists in the SQL plugin's `/plugins/sql` endpoint, where the `cursor` parameter is deserialized without proper validation, allowing remote code execution. An authenticated attacker with search permissions can craft a malicious cursor parameter to trigger unsafe deserialization of untrusted data. The fix implements ObjectInputFilter to restrict the classes that can be deserialized.
Affected products
- OpenSearch Project OpenSearch SQL 2.8.0.0 through 2.19.5.0; 3.0.0.0 through 3.6.0.0
Timeline
- 2026-10-30: disclosed: Vulnerability publicly disclosed
- 2026-10-30: patched: Fix released in versions 2.19.6.0 and 3.7.0.0