Skip to content
Fencer Intel
high 7.7

CVE-2026-33461 json

Incorrect Authorization in Kibana Fleet Leading to Information Disclosure

published 7mo ago modified last mo. also BIT-elk-2026-33461 , BIT-kibana-2026-33461 , EUVD-2026-20525

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

Incorrect Authorization (CWE-863) in Kibana can lead to information disclosure via Privilege Abuse (CAPEC-122). A user with limited Fleet privileges can exploit an internal API endpoint to retrieve sensitive configuration data, including private keys and authentication tokens, that should only be accessible to users with higher-level settings privileges. The endpoint composes its response by fetching full configuration objects and returning them directly, bypassing the authorization checks enforced by the dedicated settings APIs.

Patch / fix

  • bitnami elk 8.19.14, 9.2.8, 9.3.3
  • bitnami kibana 8.19.14, 9.2.8, 9.3.3
  • elastic kibana 8.19.14, 9.2.8, 9.3.3
  • elasticsearch kibana 8.19.14, 9.2.8, 9.3.3

Is CVE-2026-33461 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7mo ago

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami elk
>=8.0.0, <8.19.14
>=9.0.0, <9.2.8
>=9.3.0, <9.3.3
8.19.14
9.2.8
9.3.3
bitnami kibana
>=8.0.0, <8.19.14
>=9.0.0, <9.2.8
>=9.3.0, <9.3.3
8.19.14
9.2.8
9.3.3

Affected products

  • Elastic Kibana

Classification

Weakness

References

Sources

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.