GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration
Vulnerability from bitnami_vulndb
Published
2026-08-19 08:39
Modified
2026-09-08 08:34
Summary
Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service
Details

Elasticsearch does not validate a size value taken from a user-supplied input before that value is used to reserve memory for an internal data structure. An authenticated user holding only read privileges can submit a single small crafted request to a product API endpoint that causes the node to attempt an excessively large allocation. The resulting memory exhaustion raises a fatal error that terminates the Elasticsearch node process, causing a denial of service for the affected node and degrading cluster health. The defect is not volumetric, so a single request is sufficient regardless of the heap size configured on the target node.


{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "elasticsearch",
        "purl": "pkg:bitnami/elasticsearch"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "8.19.0"
            },
            {
              "fixed": "8.19.20"
            },
            {
              "introduced": "9.4.0"
            },
            {
              "fixed": "9.4.5"
            },
            {
              "introduced": "9.5.0"
            },
            {
              "fixed": "9.5.1"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-72678"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*",
      "cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:maven:*:*"
    ],
    "severity": "Medium"
  },
  "details": "Elasticsearch does not validate a size value taken from a user-supplied input before that value is used to reserve memory for an internal data structure. An authenticated user holding only read privileges can submit a single small crafted request to a product API endpoint that causes the node to attempt an excessively large allocation. The resulting memory exhaustion raises a fatal error that terminates the Elasticsearch node process, causing a denial of service for the affected node and degrading cluster health. The defect is not volumetric, so a single request is sufficient regardless of the heap size configured on the target node.",
  "id": "BIT-elasticsearch-2026-72678",
  "modified": "2026-09-08T08:34:36.952Z",
  "published": "2026-08-19T08:39:44.859Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://discuss.elastic.co/t/elasticsearch-8-19-20-9-4-5-9-5-1-security-update-esa-2026-80/389507"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72678"
    }
  ],
  "schema_version": "1.6.2",
  "summary": "Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…