CVE-2019-7614· NVD / CVE Program· CNA elastic

A race condition flaw was found in the response headers Elasticsearch versions before 7.2.1 and 6.8.2 returns to a request.

Noroxi assessment

Priority: Monitor (action score 23/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 62.5% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: org.elasticsearch:elasticsearch (Maven) 7.2.1, 6.8.2.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to org.elasticsearch:elasticsearch (Maven) 7.2.1, 6.8.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A race condition flaw was found in the response headers Elasticsearch versions before 7.2.1 and 6.8.2 returns to a request. On a system with multiple users submitting requests, it could be possible for an attacker to gain access to response header containing sensitive data from another user.

MediumCVSS 5.9 · v3.1—No exploit Fix available

GHSA-jqm6-m3j3-8gg9

Published: Jul 30, 2019
Updated: Jun 16, 2026
EPSS: 1.0% · 62th percentile
CWE: CWE-362

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 23 / 40 · 5.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.0%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
elastic	elasticsearch	cpe:2.3:a:elastic:elasticsearch

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

elastic elasticsearchbefore 6.8.2
elastic elasticsearch7.0.0 and later · before 7.2.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (elastic). Independent of NVD's CPE analysis and usually ahead of it.

Elastic Elasticsearch
- before 7.2.1 and 6.8.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.elasticsearch:elasticsearch	from 7.0.0 · before 7.2.1	7.2.1
Maven	org.elasticsearch:elasticsearch	before 6.8.2	6.8.2

Same product

elastic: all records

Other highest-scoring records for the same primary product.

CVE-2015-1427The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection meKEV
99Now
CVE-2014-3120The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expKEV
89Now
CVE-2023-31419Elasticsearch StackOverflow vulnerability
49Plan

Published before and after this one in the same product

← EarlierCVE-2018-17247Dec 20, 2018 · Elasticsearch Security versions 6.5.0 and 6.5.1 contain an XXE flaw in Machine Learning's find_file_structure API.
23Monitor
← EarlierCVE-2019-7611Mar 25, 2019 · A permission issue was found in Elasticsearch versions before 5.6.15 and 6.6.1 when Field Level Security and Document Level Security are dis
33Monitor
Later →CVE-2019-7619Oct 30, 2019 · Elasticsearch versions 7.0.0-7.3.2 and 6.7.0-6.8.3 contain a username disclosure flaw was found in the API Key service.
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:org.elasticsearch:elasticsearch	6.8.2	Package registry (OSV)
Maven:org.elasticsearch:elasticsearch	7.2.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope