How to Fix CVE-2026-33461: Kibana (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-33461 is a sibling vulnerability in the same Elastic Kibana advisory bundle as CVE-2026-4498. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-33461 matches the primary write-up.

What is different about CVE-2026-33461?

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 en...

Impact is consistent with the bundle: disclosure of sensitive information. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-33461

Apply the patched build per the primary write-up: How to Fix CVE-2026-4498.

For a quick check, confirm the running version of Kibana:

# Confirm the installed version via your package manager
dpkg -l | grep -i kibana   # Debian/Ubuntu
rpm -qa | grep -i kibana   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-33461 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-33461?

CVSS rates it 7.7 (High). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take Kibana offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-33461 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://discuss.elastic.co/t/kibana-8-19-14-9-2-8-9-3-3-security-update-esa-2026-24/385812
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-33461
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-4498

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Elastic Kibana advisory bundle. Full procedure at how-to-fix-cve-2026-4498.*