Back to vendor advisories
AWS Security BulletinsCVE-2026-75897

CVE-2026-75897 - Uncontrolled resource consumption in OpenSearch Dashboards capabilities route

Severity not listed 1 CVE Published Oct 21, 2026 at 7:53 PM UTC

Summary

Bulletin ID: 2026-082-AWS

Scope: AWS

Content Type: Important (requires attention)

Publication Date: 08/18/2026 10:00 AM PDT

Description:

OpenSearch Dashboards is the open-source visualization and management UI for OpenSearch, and ships as part of Amazon OpenSearch Service. We identified CVE-2026-75897, an improper input validation in the capabilities route handler in OpenSearch Dashboards. The handler does not bound the size of the request payload, which might allow remote attackers to cause a denial of service via a crafted HTTP request.

Affected Products and Versions:

OpenSearch "Plugin Type" Plugin (open-source, self-managed):

- Affected: All versions from 1.3.0 through 3.7.0 inclusive, including all 2.x releases up to and including 2.19.6. The issue is inherited from upstream Kibana and is also present in Kibana 7.7.1 through 7.10.2.

- Fixed: 3.8.0

Amazon OpenSearch Service (AWS Managed):

- Affected: Engine versions OpenSearch 1.3, 2.11, 2.13, 2.15, 2.17, 2.19, 3.1, 3.3, and 3.5, and Elasticsearch-compatibility versions using Kibana 7.9 and 7.10.

- Fixed: A patched service software release is available for all affected versions. Apply the latest available service software update to your domain.

Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.

Products covered

A separate affected-products list was not included in the collected bulletin.

Remediation

- Fixed: 3.8.0 Amazon OpenSearch Service (AWS Managed): - Affected: Engine versions OpenSearch 1.3, 2.11, 2.13, 2.15, 2.17, 2.19, 3.1, 3.3, and 3.5, and Elasticsearch-compatibility versions using Kibana 7.9 and 7.10.

CVEs in this advisory 1

Update history

What changed in later vendor updates

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

    • The vendor changed the advisory's last-updated date.
    • The vendor changed the advisory's last-updated date.
    • The vendor changed the advisory's last-updated date.
    • The vendor changed the advisory's last-updated date.

Updates

  1. Added to SecurityAlert

    We collected the advisory from the official source.

  2. Published by AWS

    The publication date reported by the vendor.

  3. Confirmed at the source

    Our collector saw this advisory during a later source check.