KibanaApplication · Elastic
CVE-2026-26939
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 · uneditedMissing Authorization (CWE-862) in Kibana’s server-side Detection Rule Management can lead to Unauthorized Endpoint Response Action Configuration (host isolation, process termination, and process suspension) via CAPEC-1 (Accessing Functionality Not Properly Constrained by ACLs). This requires an authenticated attacker with rule management privileges.
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 · high confidenceKibana's Detection Rule Management lacks proper server-side authorization checks, allowing authenticated users with rule management privileges to configure endpoint response actions (host isolation, process termination, and suspension) outside their intended authorization scope. This is a CWE-862 (Missing Authorization) vulnerability where the access control logic fails to properly constrain privileged actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
KibanaApplication
>= 8.0.0, < 8.19.12>= 9.0.0, < 9.2.6= 9.3.0CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Kibana versionRun `kibana --version` or check the Kibana package.json file, or query the Kibana API at `GET /api/status` to retrieve the version numberAffected if The installed version is 8.0.0 through 8.19.11, 9.0.0 through 9.2.5, or exactly 9.3.0
-
Confirm Detection Rule Management is accessibleLog into Kibana and navigate to the Detection Rules section (Security > Detection rules) or query the Kibana API endpoint for rules at `GET /api/detection_engine/rules`Affected if The Detection Rule Management interface is accessible and functional in the Kibana instance
-
Check for endpoint response actions configured in rulesReview existing detection rules via the Kibana UI or API (`GET /api/detection_engine/rules`) and inspect each rule's response actions configuration for host isolation, process termination, or suspension actionsAffected if Any detection rule has endpoint response actions (host_isolation, process_execution, or suspension) enabled
-
Audit user roles with rule management privilegesUse Kibana's role management (`GET /api/security/role`) or check the Elasticsearch roles (`GET /xpack/security/role`) to identify users granted the "manage_detection_engine" or equivalent rule management privilegeAffected if More than the intended minimal set of users have rule management privileges, particularly users who should not have endpoint response capabilities
You are affected if your Kibana version falls within the affected ranges AND Detection Rule Management with endpoint response actions is in use by users outside the intended authorization scope.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.19.129.2.6
Apply the vendor-supplied patch for CVE-2026-26939 to Kibana, which adds proper authorization validation for endpoint response action configuration in Detection Rule Management. Restrict rule management privileges to only those users who require endpoint response capabilities until the patch is deployed.
Kibana 8.19.12 (for 8.x branches) or Kibana 9.2.6/9.3.1+ (for 9.x branches)
- 1. Review the Elastic Stack upgrade documentation to understand the upgrade path and prerequisites
- 2. Ensure you have a complete backup of your Kibana and Elasticsearch data and configuration
- 3. Test the upgrade in a staging environment before deploying to production
- 4. For Kibana 8.x users: Upgrade to Kibana version 8.19.12 or later
- 5. For Kibana 9.x users: Upgrade to Kibana version 9.2.6 or later (or 9.3.1+ if on 9.3.0)
- 6. After upgrade, verify that the Detection Rule Management functionality works correctly
- 7. Review user privileges and role definitions to ensure the principle of least privilege is applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Kibana
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26939 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26939 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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