# CVE-2025-12149: Missing authorization in Search Guard FLX

> Attackers can bypass Document-Level Security in Search Guard FLX via Signals watches to read protected documents.

- **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:** 14 Nov 2025
- **Updated:** 14 Nov 2025
- **Also known as:** GHSA-mj54-9pv2-7pc5

## What is CVE-2025-12149?

CVE-2025-12149 is a medium-severity missing authorization vulnerability in floragunn Search Guard FLX, published on 14 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Search Guard FLX versions 3.1.2 and earlier, while Document-Level Security (DLS) is correctly enforced elsewhere, when the search is triggered from a Signals watch, the DLS rule is not enforced, allowing access to all documents in the queried indices.

Weakness: CWE-863 (Incorrect Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-12149 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12149 is a medium-severity missing authorization vulnerability in floragunn Search Guard FLX, published on 14 Nov 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-12149 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-12149/ (Markdown: https://insights.sbomify.com/CVE-2025-12149/index.md)
```

## Sources

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

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