Insertion of Sensitive Information Into Sent Data in Kibana Observability onboarding can lead to disclosure
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 3 Nov 2026, 19:46 UTC
Thin evidence
One scorer or none| CNA (elastic) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 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 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ElasticKibana | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict onboarding privileges to trusted users only and review Kibana configuration to avoid embedding sensitive credentials in URLs where possible.
Description
A vulnerability in Kibana Observability onboarding allows insertion of sensitive information into sent data, exposing credentials used by Kibana to connect to Elasticsearch. Authenticated users with privileges to onboard Observability data can retrieve these credentials embedded in Elasticsearch host URLs, potentially gaining unauthorized access to Elasticsearch with Kibana service account privileges.