CVE-2026-49087 in Kibana
Allocation 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.
Quick answer
Elastic Kibana should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Kibana 8.0.0 through 8.19.14
- Kibana 9.0.0 through 9.3.3
Fixed versions
- Kibana 8.19.15 or 9.3.4 or later
How to fix it
CVE-2026-49087 affects Kibana. In simple terms, an attacker may be able to make the service slow or stop if the affected part is exposed or receives unsafe input. Update to Kibana 8.19.15 or 9.3.4 or later. If you cannot update now, limit access until the fix is installed.
- Find every Kibana install and check its version.
- Update to Kibana 8.19.15 or 9.3.4 or later.
- If you cannot update today, block public access to the risky feature or service.
- Review logs for strange access, crashes, deleted files, or failed requests.
- Rotate secrets if you think the issue may have been used.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is fixed or the mitigation is active.
- Test the affected feature with a normal user account.
- Confirm untrusted users cannot reach the risky path or service.
- Run a fresh Fixnx scan and keep the result with your change record.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-49087?
Elastic Kibana versions listed as affected should be reviewed: Kibana 8.0.0 through 8.19.14, Kibana 9.0.0 through 9.3.3.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.