Skip to main content
VulnerabilityPublished

CVE-2026-4818: floragunn Search Guard FLX · Improper Authorization

Affects floragunn Search Guard FLXSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
floragunnSearch Guard FLXAffected
  • >=3.0.0 <=4.0.1
Fixed in–

AI-suggested

Organizations should immediately assess their use of Search Guard FLX versions 3.0.0 through 4.0.1 and plan for an upgrade to a patched version once available. In the absence of official patches, administrators should enforce stricter access controls by limiting user privileges to the minimum necessary and auditing user roles to ensure no unauthorized management permissions are granted. Network segmentation and firewall rules should restrict access to Elasticsearch management interfaces to trusted administrators only. Implement monitoring and alerting for unusual management operations on data streams to detect potential exploitation attempts early. Additionally, consider deploying compensating controls such as proxy-based access control or additional authentication layers around Elasticsearch endpoints. Regularly review and update security policies to align with the principle of least privilege and maintain comprehensive logging for forensic analysis.

Description

In Search Guard FLX versions from 3.0.0 up to 4.0.1, there exists an issue which allows users without the necessary privileges to execute some management operations against data streams.

References

Community reviews

Loading reviews…