---
id: CVE-2025-12147
title: >-
  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, th…
summary: >-
  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, th…
severity: none
cwe:
  - CWE-200
  - CWE-732
published: '2025-10-29'
updated: '2026-09-30'
sourceUpdated: '2026-09-30T23:10:00.237'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-12147'
references:
  - url: 'https://docs.search-guard.com/latest/changelog-searchguard-flx-3_1_2'
    label: security@search-guard.com
  - url: 'https://search-guard.com/cve-advisory/'
    label: security@search-guard.com
tags:
  - nvd
epss: 0.00274
epssPercentile: 0.17875
ingestedAt: '2026-09-30T23:29:32.457Z'
---

## Overview

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.*).

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.