X-Pack Security 5.2.x would allow access to more fields than the user should have seen if the field level security rules used a mix of gran…

published 2017-06-16 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17399

cvss: 5.9; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits: 0; none known

X-Pack Security 5.2.x would allow access to more fields than the user should have seen if the field level security rules used a mix of grant and exclude rules when merging multiple rules with field level security rules for the same index.

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.9	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

Elastic Elastic X-Pack Security

Classification

Weakness

CWE-732 Incorrect Permission Assignment for Critical Resource
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

elastic.co /community/security
vendor-advisory

Sources

CVE List CVE-2017-8449
NVD CVE-2017-8449

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.

Summary