CVE-2026-49096: kibana · Uncaught Exception
Affects kibanaSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium · fixed in 9.4.2 : update kibana when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.4.2, 9.3.5, 8.19.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade kibana to 9.4.2, 9.3.5 or 8.19.20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikibanapkg:bitnami/kibanaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should upgrade Kibana to versions 8.19.20 or later, 9.3.5 or later, or 9.4.2 or later as appropriate. Until patched, administrators should monitor and remove any malformed comments causing this issue. No other mitigation steps are indicated by the vendor advisory.
Description
A vulnerability in Kibana Cases allows an authenticated user with commenting privileges to cause a denial of service by submitting a malformed link syntax in a case comment. This malformed comment is not sanitized or rejected and triggers an unhandled exception when the case is viewed, rendering the case inaccessible to all users until the comment is removed. The issue affects multiple Kibana versions prior to specific fixed releases.