Skip to main content
VulnerabilityPublished

CVE-2026-47874: Elasticsearch · vulnerability occurs when a client sends HTTP/1

Affects elasticsearchSource GCVE Database

0
Compare
Authoritative record:CVE-2026-47874· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 9.2.8-r13 when convenient.

Data as of 14 Nov 2026, 02:05 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 9.2.8-r13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade elasticsearch to 9.2.8-r13.

Affected software

ProductAffectedFixed in
CleanStartelasticsearchpkg:apk/cleanstart/elasticsearch?arch=x86_64Other threatsAffected
  • <9.2.8-r13
Fixed in
  • 9.2.8-r13
CleanStartelasticsearchpkg:apk/cleanstart/elasticsearch?arch=aarch64Other threatsAffected
  • <9.2.8-r13
Fixed in
  • 9.2.8-r13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Elasticsearch to version 9.2.8-r13 or later, where this vulnerability is fixed. No additional mitigations are indicated.

Description

A medium severity vulnerability in Elasticsearch occurs when a client sends HTTP/1 requests. This flaw affects versions prior to 9.2.8-r13 and can cause availability impact without compromising confidentiality or integrity.

References

Community reviews

Loading reviews…