Search Guard versions before 24.3 had an issue when Cross Cluster Search (CCS) was enabled, authenticated users are always authorized on th…

published 2019-08-13 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-4910

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

Search Guard versions before 24.3 had an issue when Cross Cluster Search (CCS) was enabled, authenticated users are always authorized on the local cluster ignoring their roles on the remote cluster(s).

Patch / fix

fixed in 1

search-guard search_guard 24.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-13416 updated 2025-11-21 cvss 5.3

search-guard: authenticated users ignoring their roles on the remote cluster

Red Hat OpenShift Container Platform 3.9 search-guard-2, openshift-elasticsearch-plugin Red Hat OpenShift Container Platform 3.10 openshift-elasticsearch-plugin Red Hat OpenShift Container Platform 3.11 openshift3/ose-logging-elasticsearch5 Red Hat OpenShift Container Platform 4 openshift4/ose-logging-elasticsearch5
affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

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

floragunn Search Guard

Classification

Weakness

CWE-285 Improper Authorization

References

search-guard.com /cve-advisory/
vendor-advisory
docs.search-guard.com /6.x-25/changelog-searchguard-6-x-24_3
release-notes, vendor-advisory

Sources

CVE List CVE-2019-13416
NVD CVE-2019-13416

Fencer Vulns 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