# CVE-2025-12148: Unauthorized access to fields protected by Field Masking (FM) for fields of type IP

> Attackers can reconstruct masked IP addresses in Search Guard by exploiting search result leaks, bypassing field masking protections.

- **Severity:** Medium 6.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-p868-4f8c-8pq7

## What is CVE-2025-12148?

CVE-2025-12148 is a medium-severity vulnerability in floragunn Search Guard FLX, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-12148?


## How do I fix CVE-2025-12148?

No fix has been published for CVE-2025-12148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12148 being exploited?

There is no known exploitation of CVE-2025-12148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12148 and fix it if it is affected.

What it is: CVE-2025-12148 is a medium-severity vulnerability in floragunn Search Guard FLX, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12148 in the wild and no public exploit code.

Affected product: floragunn Search Guard FLX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12148/ (Markdown: https://insights.sbomify.com/CVE-2025-12148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12148
- OSV: https://osv.dev/vulnerability/CVE-2025-12148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12148/
Summaries are generated and may contain mistakes; the official description above is the record.