KibanaApplication · Elastic
CVE-2026-26936
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 · uneditedInefficient Regular Expression Complexity (CWE-1333) in the AI Inference Anonymization Engine in Kibana can lead Denial of Service via Regular Expression Exponential Blowup (CAPEC-492).
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 confidenceA regular expression denial of service (ReDoS) vulnerability exists in Kibana's AI Inference Anonymization Engine where an inefficient regex pattern can cause exponential backtracking when processing specially crafted input strings, leading to excessive CPU consumption and potential service unavailability.
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.11>= 9.0.0, < 9.2.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check Kibana versionRun `kibana --version` or inspect the Kibana startup logs, or query the Kibana API endpoint `/api/status`Affected if The installed version is >= 8.0.0 and < 8.19.11, OR >= 9.0.0 and < 9.2.5
-
Verify AI Inference Anonymization Engine is configuredCheck Kibana configuration files (kibana.yml) and look for settings related to AI assistant, inference, or anonymization features, or inspect the saved objects API for AI-related configurationsAffected if The AI Inference Anonymization Engine or AI Assistant with anonymization capabilities is enabled in the Kibana configuration
-
Confirm the vulnerability trigger path is accessibleReview Kibana logs and network access controls to determine if users can access the AI Assistant or inference endpoints that process input through the anonymization engineAffected if Users or automated processes can send requests to Kibana AI features that utilize the anonymization engine
You are affected if your Kibana version falls within the vulnerable ranges AND the AI Inference Anonymization Engine is enabled and accessible to users.
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.119.2.5
Apply the appropriate Kibana security update or patch from Elastic to address the inefficient regex in the AI Inference Anonymization Engine; until patched, implement request rate limiting and input validation as compensating controls.
Kibana 8.19.11+ or 9.2.5+
- Identify all Kibana instances in the environment and determine their current versions
- If running Kibana 8.x: Plan an upgrade to version 8.19.11 or later during a maintenance window
- If running Kibana 9.x: Plan an upgrade to version 9.2.5 or later during a maintenance window
- Execute the upgrade following standard Elastic upgrade procedures
- Verify the upgrade was successful by checking the Kibana version and health status
- Confirm the AI Inference Anonymization Engine functions correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Kibana
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26936 — 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-26936 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