Elastic Kibana is widely deployed; unauthorized config modification can disable monitoring, tamper logs, expose data, and enable further compromise across organizations.
CVE-2026-82302
Kibana improper authorization allows unauthorized configuration changes.
Is CVE-2026-82302 being exploited?
Not confirmed. CVE-2026-82302 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-82302?
CVE-2026-82302 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82302?
Yes. A fix has been recorded for CVE-2026-82302. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82302 affect?
CVE-2026-82302 affects Elastic Kibana (versions prior to 8.19.22, 9.4.7, 9.5.3). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82302?
Apply vendor patch immediately; restrict Kibana access and audit configs/logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can modify Kibana configs via flawed access controls, enabling log/dashboard tampering, data exposure, and potential privilege escalation.
Patch when possible
- affected>= 8.0.0 and <= 8.19.20
- affected>= 9.0.0 and <= 9.4.5
- affected>= 9.5.0 and <= 9.5.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.