Skip to main content
VulnerabilityPublished

CVE-2025-12148: floragunn Search Guard FLX · Information Exposure

Affects floragunn Search Guard FLXSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
floragunn Search Guard FLXAffected
  • =1.0.0
Fixed in–

AI-suggested

  1. Upgrade Search Guard FLX to the latest version that addresses CVE-2025-12148 as soon as it becomes available from floragunn.
  2. Until an upgrade is possible, implement field level security (FLS) on IP address fields instead of relying on field masking to prevent unauthorized access to sensitive IP data.
  3. Review and tighten user privileges to minimize the number of accounts with access to search functionality, especially those with permissions to query IP fields.
  4. Monitor Elasticsearch query logs for unusual or targeted searches involving IP address fields that could indicate exploitation attempts.
  5. Conduct internal audits of data classification and ensure sensitive IP information is only stored and accessible where strictly necessary.
  6. Educate security and IT teams about this vulnerability and the importance of applying the recommended mitigations promptly.
  7. Consider network segmentation and additional access controls around Elasticsearch clusters to reduce the risk of insider threats exploiting this vulnerability.

Description

In Search Guard versions 3.1.1 and earlier, Field Masking (FM) rules are improperly enforced on fields of type IP (IP Address). While the content of these fields is properly redacted in the _source document returned by search operations, the results do return documents (hits) when searching based on a specific IP values. This allows to reconstruct the original contents of the field. Workaround - If you cannot upgrade immediately, you can avoid the problem by using field level security (FLS) protection on fields of the affected types instead of field masking.

References

Community reviews

Loading reviews…