Elastic Kibana up to 8.19.19/9.3.4/9.4.0/9.4.1 Cases uncaught exception

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.5$0-$5k0.50

Summaryinfo

A vulnerability was found in Elastic Kibana up to 8.19.19/9.3.4/9.4.0/9.4.1. It has been classified as problematic. Impacted is an unknown function of the component Cases. This manipulation causes uncaught exception. The identification of this vulnerability is CVE-2026-49096. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Elastic Kibana up to 8.19.19/9.3.4/9.4.0/9.4.1. It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component Cases. The manipulation with an unknown input leads to a uncaught exception vulnerability. The CWE definition for the vulnerability is CWE-248. An exception is thrown from a function, but it is not caught. As an impact it is known to affect availability. The summary by CVE is:

Uncaught Exception (CWE-248) in Kibana Cases can lead to denial of service via Input Data Manipulation (CAPEC-153). Malformed link syntax stored in a case comment was not rejected or sanitized when the comment was later formatted for display, and the resulting unhandled error prevented the affected case from being displayed. An authenticated user holding privileges to comment on a case could store such a comment, after which that case became inaccessible to every user who opened it until the stored comment was removed.

It is possible to read the advisory at discuss.elastic.co. This vulnerability is known as CVE-2026-49096 since 05/27/2026. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.5

VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uncaught exception
CWE: CWE-248
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

05/27/2026 CVE reserved
08/13/2026 +78 days Advisory disclosed
08/13/2026 +0 days VulDB entry created
08/13/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: discuss.elastic.co
Status: Confirmed

CVE: CVE-2026-49096 (🔒)
GCVE (CVE): GCVE-0-2026-49096
GCVE (VulDB): GCVE-100-389779

Entryinfo

Created: 08/13/2026 21:39
Changes: 08/13/2026 21:39 (52)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!