How severe is CVE-2019-7611?

CVE-2019-7611 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-7611?

CVE-2019-7611 affects the following packages: org.elasticsearch:elasticsearch (Maven), org.elasticsearch:elasticsearch (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-7611?

Update org.elasticsearch:elasticsearch to 5.6.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-7611 is resolved across your whole dependency graph.

How do I detect CVE-2019-7611 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch:elasticsearch, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-7611 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2019-7611 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-7611 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-7611?

CVE-2019-7611 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-7611?

CVE-2019-7611 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-7611 published, and has it been updated?

CVE-2019-7611 was published on March 25, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2019-7611 — elasticsearch

HIGH

CVE-2019-7611 is a high-severity (CVSS 8.1) CWE-284 vulnerability in org.elasticsearch:elasticsearch. A fix is available for org.elasticsearch:elasticsearch — see the affected versions and patch details below.

Improper Access Control in Elasticsearch

Also known asGHSA-fj32-6v7m-57pg

Published

Mar 25, 2019

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.elasticsearch:elasticsearch☕org.elasticsearch:elasticsearch

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 disabled and the _aliases, _shrink, or _split endpoints are used . If the elasticsearch.yml file has xpack.security.dls_fls.enabled set to false, certain permission checks are skipped when users perform one of the actions mentioned above, to make existing data available under a new index/alias name. This could result in an attacker gaining additional permissions against a restricted index.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.elasticsearch:elasticsearch`	all versions	5.6.15`org.elasticsearch:elasticsearch:5.6.15`
☕Maven	`org.elasticsearch:elasticsearch`	≥ 6.0.0&&< 6.6.1	6.6.1`org.elasticsearch:elasticsearch:6.6.1`

Affected Products

1 product · 2 configurations

Application

elasticsearchelastic

≥ 6.0.0 && < 6.6.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch:elasticsearch, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.elasticsearch:elasticsearch to 5.6.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-7611 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat OpenStack Platform 8.0/9.0 Operational Tools Kibana/Elasticsearch versions do not include nor support X-Pack (8/9 versions must use the optional Shield, also not packaged); not affected. OpenShift Container Platform (OCP) does not include X-Pack with Elasticsearch, which prevents this vulnerability from being…

Product	Fixed in	Advisory
Red Hat Decision Manager 7	`elasticsearch`	RHSA-2020:0899
Red Hat Process Automation 7	`elasticsearch`	RHSA-2020:0895

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-7611 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-284CWE-284

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

elasticsearch

6.0/10

Code-Review9/10

Maintained10/10

Branch-Protection4/10

Assessed Nov 2, 2026

Timeline

Disclosed

Mar 25, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-7611

GHSA-fj32-6v7m-57pg

References

Advisorydiscuss.elastic.co Advisoryelastic.co · security Advisorynvd.nist.gov · CVE 2019 7611 Packagegithub.com · elasticsearch

Related vulnerabilities

This CVE is high severity — higher than any of the other 8 CVEs affecting elasticsearch (highest there: moderate).

CVE-2024-52979CVE-2024-52981CVE-2024-43709CVE-2024-12539CVE-2024-23444CVE-2023-49921CVE-2024-37280CVE-2024-23449

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-7611 — elasticsearch

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-7611 in your dependencies?