A local file disclosure flaw was found in Elastic Code versions 7.3.0, 7.3.1, and 7.3.2.

published 2019-10-01 7y ago modified 2026-06-17 4mo ago also EUVD-2019-17152

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits: 0; none known

A local file disclosure flaw was found in Elastic Code versions 7.3.0, 7.3.1, and 7.3.2. If a malicious code repository is imported into Code it is possible to read arbitrary files from the local filesystem of the Kibana instance running Code with the permission of the Kibana system user.

Is CVE-2019-7618 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.45% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:P/I:N/A:N

Affected products

Elastic Elastic Code

Classification

Weakness

CWE-538 Insertion of Sensitive Information into Externally-Accessible File or Directory
CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

staging-website.elastic.co /community/security
permissions-required, vendor-advisory
discuss.elastic.co /t/elastic-stack-7-4-0-security-update/201831
release-notes, vendor-advisory

Sources

CVE List CVE-2019-7618
NVD CVE-2019-7618

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.