dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-12149

MEDIUM · 6.0 CVSS v4.0 Published 2025-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In Search Guard FLX versions 3.1.2 and earlier, Document-Level Security (DLS) is correctly enforced for normal search queries but is bypassed when searches originate from a Signals watch, allowing unauthorized access to all documents in the targeted indices regardless of DLS rules.

MitigationUpgrade to a version newer than 3.1.2 when available, and audit existing Signals watch configurations to ensure they only query indices with appropriate access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Search Guard FLX version
    Check the installed Search Guard FLX version in your Elasticsearch environment (typically via the Search Guard admin API, kibana plugin, or package version). Compare this version number to 3.1.2.
    Affected if The installed version is 3.1.2 or earlier.
  2. Confirm Signals watch is in use
    Review your Search Guard configuration to determine if the Signals watch feature is enabled or has been configured. Check for any existing watch definitions in the Search Guard signals index or configuration.
    Affected if Signals watches are created or the Signals feature is enabled.
  3. Verify Document-Level Security is configured
    Inspect your Search Guard role definitions to identify which roles have DLS (Document-Level Security) queries configured. Use the Search Guard admin tools or REST API to list roles with DLS filters.
    Affected if DLS is defined on any role that restricts access to certain documents.
  4. Identify watches targeting DLS-protected indices
    Examine all Signals watch configurations to see which indices they query. Cross-reference these with indices protected by DLS rules.
    Affected if Any Signals watch queries an index that has DLS rules applied to the requesting user's role.

You are affected if you run Search Guard FLX version 3.1.2 or earlier, have Signals watches configured, and those watches query indices protected by Document-Level Security rules.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version newer than 3.1.2 when available, and audit existing Signals watch configurations to ensure they only query indices with appropriate access controls.

Recommended fix Moderate confidence

Search Guard FLX version newer than 3.1.2 (contact vendor for exact fixed release)

  1. 1. Identify all Search Guard FLX installations currently running version 3.1.2 or earlier in your environment
  2. 2. Review the Search Guard FLX release notes or contact Search Guard support to identify the specific version that addresses CVE-2025-12149
  3. 3. Plan the upgrade during a maintenance window to minimize service disruption
  4. 4. Before upgrading, backup your current Search Guard configuration
  5. 5. Upgrade Search Guard FLX to the version that includes the DLS fix for Signals watch
  6. 6. After upgrading, verify that Document-Level Security is properly enforced when searches are triggered from Signals watches
  7. 7. Test that the fix does not introduce regressions in other Search Guard functionality
Caveat Review release notes for any configuration or feature changes between 3.1.2 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12149 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data