# Elasticsearch StackOverflow vulnerability

Advisory record · `GHSA-4q22-422g-m4pj`

- **Identifiers:** `GHSA-4q22-422g-m4pj` · `BIT-elasticsearch-2024-37280` · `CVE-2024-37280`
- **State:** Confirmed
- **Severity:** CVSS 4.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-122](https://cwe.mitre.org/data/definitions/122.html) · [CWE-787](https://cwe.mitre.org/data/definitions/787.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Published:** 13 Jun 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Jun 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.elasticsearch:elasticsearch` (Maven): affected `>=8.13.1, <8.14.0`; fixed in `8.14.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Elasticsearch versions 8.13.1 up to but not including 8.14.0 are affected. When an index template uses a dynamic field mapping of "passthrough" type, ingesting certain documents into that index can trigger a StackOverflow exception, leading to denial of service. The source does not state what access an attacker needs. Upgrade to Elasticsearch 8.14.0 or later; no other workaround is listed.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`, from CNA (elastic)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0062, the 50th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4q22-422g-m4pj)

## Sources

- [GitHub Advisory Database: GHSA-4q22-422g-m4pj](https://github.com/advisories/GHSA-4q22-422g-m4pj)
- [OSV: GHSA-4q22-422g-m4pj](https://osv.dev/vulnerability/GHSA-4q22-422g-m4pj)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-37280>
- <https://discuss.elastic.co/t/elasticsearch-8-14-0-security-update-esa-2024-14/361007>
- <https://github.com/elastic/elasticsearch>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4q22-422g-m4pj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4q22-422g-m4pj/>. Everything for agents: <https://agentprime.io/llms.txt>.