Skip to main content
CVE-2024-43707VulnerabilityPublished Updated

CVE-2024-43707: Kibana exposure of sensitive information to an unauthorized actor

Affects kibanaSource GCVE Database

0

Not known to be exploited : upgrade to 8.15.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.15.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Upgrade kibana to 8.15.0.

Affected software

ProductAffectedFixed in
Bitnamikibanapkg:bitnami/kibanaOther threatsAffected
  • >=8.0.0 <8.15.0
Fixed in
  • 8.15.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patch provided by the vendor to Kibana versions >=8.0.0 and <8.15.0 to remediate this vulnerability. Since a patch is available, updating to a fixed version is the recommended mitigation.

Description

A vulnerability in Kibana allows users without Fleet access to view Elastic Agent policies, which may contain sensitive information depending on enabled integrations and their versions. This exposure affects Kibana versions from 8.0.0 up to but not including 8.15.0. The issue has been assigned CVE-2024-43707 and is rated with high severity. A patch is available to address this vulnerability.

References

Community reviews

Loading reviews…