CVE-2026-82293 json
Incorrect Authorization in Kibana Leading to Unauthorized Resource Consumption
published 2mo ago modified 2mo ago also BIT-elk-2026-82293 , BIT-kibana-2026-82293 , EUVD-2026-70067
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
Incorrect Authorization (CWE-863) in the Kibana machine learning feature can lead to unauthorized resource consumption via Exploiting Incorrectly Configured Access Control Security Levels (CAPEC-180). An authenticated user could invoke machine learning functionality beyond their authorization scope, consuming cluster resources they should not be able to reach.
Patch / fix
- bitnami elk 8.19.21, 9.4.6, 9.5.2
- bitnami kibana 8.19.21, 9.4.6, 9.5.2
- elastic kibana 8.19.21, 9.4.6, 9.5.2
- elasticsearch kibana 8.19.21, 9.4.6, 9.5.2
Is CVE-2026-82293 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | elk | >=8.0.0, <8.19.21 >=9.0.0, <9.4.6 >=9.5.0, <9.5.2 |
8.19.21 9.4.6 9.5.2 |
| bitnami | kibana | >=8.0.0, <8.19.21 >=9.0.0, <9.4.6 >=9.5.0, <9.5.2 |
8.19.21 9.4.6 9.5.2 |
Affected products
- Elastic Kibana
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
Sources
- CVE List CVE-2026-82293
- NVD CVE-2026-82293
- OSV BIT-elk-2026-82293
- OSV BIT-kibana-2026-82293
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.