CVE-2026-33461: Elastic Kibana incorrect authorization in Fleet component

CVE-2026-33461 · Severity: high · CVSS 7.7 · Published 2026-04-08

Kibana is a data visualization and management platform for the Elastic Stack. A security flaw in the Fleet management component allows users with low-level permissions to access sensitive configuration data they should not be able to see. This could result in the exposure of private keys and authentication tokens, potentially allowing an attacker to further compromise the environment or intercept data.

Technologies: Elastic Kibana. Vendors: Elastic.

Quick answers

Is CVE-2026-33461 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33461 being exploited in the wild.
How severe is CVE-2026-33461?
High severity, with a CVSS score of 7.7, published 8 April 2026.
Which products and versions are affected?
Elastic Kibana 8.0.0 to 8.19.13, 9.0.0 to 9.2.7, 9.3.0 to 9.3.2.
Is there a fix for CVE-2026-33461?
A patch was published on 2026-04-08. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33461 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-33461?
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

An incorrect authorization vulnerability (CWE-863) exists in Kibana's Fleet component. The flaw resides in an internal API endpoint that fails to properly enforce authorization checks when fetching configuration objects. Specifically, the endpoint returns full configuration objects directly, bypassing the stricter access controls implemented in dedicated settings APIs. An authenticated attacker with 'Fleet Agents' privileges but lacking 'Fleet Settings' privileges can exploit this to disclose sensitive secrets like private keys and tokens. The issue is resolved in Kibana versions 8.19.14, 9.2.8, and 9.3.3.

Affected products

  • Elastic Kibana 8.0.0 to 8.19.13, 9.0.0 to 9.2.7, 9.3.0 to 9.3.2

Timeline

  • 2026-04-08: disclosed
  • 2026-04-08: advisory
  • 2026-04-08: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.