Quick answers
- Is CVE-2026-82298 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82298 being exploited in the wild.
- How severe is CVE-2026-82298?
- Medium severity, with a CVSS score of 4.3, published 3 September 2026.
- Which products and versions are affected?
- Elastic Kibana 8.0.0 to 8.19.20, 9.0.0 to 9.4.5, 9.5.0 to 9.5.2.
- Is there a fix for CVE-2026-82298?
- A patch was published on 2026-09-03: Patches released in versions 8.19.21, 9.4.6, and 9.5.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82298 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82298?
- Check whether you run Elastic Kibana at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an Incorrect Authorization (CWE-863) issue in Kibana that occurs when access control is improperly configured, specifically related to Fleet and agent communication message signing. An authenticated attacker (PR:L) can exploit this via the network to bypass access control security levels and trigger a denial of service condition. The vulnerability affects configurations with Fleet and agent communication message signing enabled across Kibana versions 8.0.0–8.19.20, 9.0.0–9.4.5, and 9.5.0–9.5.2. Patches are available in versions 8.19.21, 9.4.6, and 9.5.3. No workarounds exist for unpatched deployments.
Affected products
- Elastic Kibana 8.0.0 to 8.19.20, 9.0.0 to 9.4.5, 9.5.0 to 9.5.2
Timeline
- 2026-09-03: disclosed
- 2026-09-03: patched: Patches released in versions 8.19.21, 9.4.6, and 9.5.3