CVE-2025-12147: floragunn Search Guard FLX · Information Exposure
Affects floragunn Search Guard FLXSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| floragunn Search Guard FLX | Affected
| Fixed in– |
AI-suggested
1. Immediately review and audit all FLS exclusion rules applied to object-valued fields in Search Guard FLX configurations. 2. Implement the recommended workaround by adding exclusion rules for both the object fields and all their child attributes (e.g., ~object and ~object.*) to ensure complete exclusion of sensitive data. 3. Monitor vendor communications closely for official patches or updates and plan prompt upgrades to versions beyond 3.1.1 once available. 4. Conduct thorough testing of FLS policies in a staging environment to verify that sensitive fields are fully protected against unauthorized queries. 5. Restrict privileges of users and roles to the minimum necessary to reduce the risk of exploitation. 6. Enable detailed logging and alerting on search queries that access sensitive fields to detect potential abuse. 7. Consider additional data encryption at rest and in transit to mitigate data exposure risks. 8. Educate security and DevOps teams about this vulnerability and the importance of precise FLS configurations.
Description
In Search Guard FLX versions 3.1.1 and earlier, Field-Level Security (FLS) rules are improperly enforced on object-valued fields. When an FLS exclusion rule (e.g., ~field) is applied to a field which contains an object as its value, the object is correctly removed from the _source returned by search operations. However, the object members (i.e., child attributes) remain accessible to search queries. This exposure allows adversaries to infer or reconstruct the original contents of the excluded object. Workaround - If you cannot upgrade immediately and FLS exclusion rules are used for object valued attributes (like ~object), add an additional exclusion rule for the members of the object (like ~object.*).