{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "versions": [
              {
                "introduced": "8.10.0"
              },
              {
                "last_affected": "8.15.0"
              }
            ]
          },
          "events": [
            {
              "introduced": "824bcbfd9972c61e79ca9def6d43b550c5ff2999"
            },
            {
              "last_affected": "8aa0b59da12c996e3048d8875446667ee6e15c7f"
            }
          ],
          "repo": "https://github.com/elastic/kibana",
          "type": "GIT"
        }
      ]
    }
  ],
  "details": "A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. A successful attack requires a malicious user to have a combination of both specific  Elasticsearch indices privileges https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html#roles-indices-priv  and  Kibana privileges https://www.elastic.co/guide/en/fleet/current/fleet-roles-and-privileges.html  assigned to them.\n\n\n\nThe following Elasticsearch indices permissions are required\n\n  *  write privilege on the system indices .kibana_ingest*\n  *  The allow_restricted_indices flag is set to true\n\n\nAny of the following Kibana privileges are additionally required\n\n  *  Under Fleet the All privilege is granted\n  *  Under Integration the Read or All privilege is granted\n  *  Access to the fleet-setup privilege is gained through the Fleet Server’s service account token",
  "id": "CVE-2024-37285",
  "modified": "2026-03-10T21:52:14.888366814Z",
  "published": "2024-11-14T17:15:06.457Z",
  "references": [
    {
      "type": "FIX",
      "url": "https://discuss.elastic.co/t/kibana-8-15-1-security-update-esa-2024-27-esa-2024-28/366119"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}