KibanaApplication · Elastic
CVE-2026-49087
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 · uneditedAllocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user can submit a specially crafted bulk deletion request that causes excessive resource consumption, which may render Kibana unavailable.
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 confidenceKibana contains a resource exhaustion vulnerability (CWE-770) where an authenticated user can submit specially crafted bulk deletion requests that cause excessive memory and CPU consumption, potentially rendering the Kibana instance unavailable. The vulnerability stems from a lack of resource limits or throttling on bulk deletion operations.
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.15>= 9.0.0, < 9.3.4CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Kibana versionRun `kibana --version` or check the version file in the Kibana installation directory, or query the Kibana API endpoint `GET /api/status`Affected if The installed version falls within >= 8.0.0 and < 8.19.15, or >= 9.0.0 and < 9.3.4
-
Verify bulk deletion API exposureConfirm that the bulk deletion endpoint (typically `/api/delete_by_query` or similar bulk operation APIs) is accessible to authenticated non-admin users by reviewing Kibana user role permissions and API route configurationsAffected if Authenticated users have permissions to invoke bulk deletion operations without restrictive role constraints
-
Check for rate limiting on deletion APIsReview Kibana configuration files (kibana.yml) and any reverse proxy or API gateway settings for rate limiting rules targeting bulk deletion endpointsAffected if No rate limiting, throttling, or request size limits are configured for bulk deletion operations
-
Inspect current resource consumptionMonitor Kibana process memory usage and CPU utilization, and review Kibana logs for patterns of bulk deletion requests causing elevated resource consumptionAffected if Kibana is experiencing high memory or CPU usage correlated with bulk deletion API activity
-
Review API access logs for anomalous deletion patternsExamine Kibana and/or Elasticsearch audit logs for sudden spikes in bulk deletion requests from individual authenticated usersAffected if Audit logs show excessive bulk deletion requests from one or more authenticated users exceeding normal operational patterns
A user is affected if their Kibana version is 8.0.0 through 8.19.14 or 9.0.0 through 9.3.3, and authenticated users have access to bulk deletion APIs without rate limiting configured.
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.159.3.4
Apply the vendor patch when released by Elastic. In the interim, implement API request rate limiting on bulk deletion endpoints and monitor for anomalous deletion patterns from authenticated users.
Kibana 8.19.15 or later (for 8.x branch); Kibana 9.3.4 or later (for 9.x branch)
- Identify your current Kibana major version (8.x or 9.x)
- For Kibana 8.x users: Upgrade to version 8.19.15 or later
- For Kibana 9.x users: Upgrade to version 9.3.4 or later
- Test the upgrade in a staging environment before deploying to production
- Verify that bulk deletion requests no longer cause excessive resource consumption after upgrade
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49087 — 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-49087 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