KibanaApplication · Elastic
CVE-2026-33461
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn Kibana's Fleet feature, an internal API endpoint bypasses authorization checks by directly returning full configuration objects (including private keys and authentication tokens) instead of applying the same filtering logic used by the dedicated settings APIs. This allows users with limited Fleet privileges to retrieve sensitive configuration data that should require higher-level settings privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
KibanaApplication
>= 8.0.0, < 8.19.14>= 9.0.0, < 9.2.8>= 9.3.0, < 9.3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Kibana versionRun 'kibana --version' or check the version from the Kibana welcome page, or query the Kibana status API at /api/statusAffected if The installed version falls within >= 8.0.0 and < 8.19.14, or >= 9.0.0 and < 9.2.8, or >= 9.3.0 and < 9.3.3
-
Verify Fleet is enabledCheck if the Fleet plugin is enabled in Kibana by navigating to Management > Fleet or querying the Fleet settings API at /api/fleet/settingsAffected if Fleet is enabled and configured in the Kibana instance
-
Check for limited Fleet user privilegesReview user roles and permissions in Kibana under Security > Users or Stack Management > Roles to identify users with limited Fleet-specific privileges (such as Fleet read-only or restricted Fleet roles)Affected if Users exist with limited Fleet privileges who should not have access to sensitive configuration data
-
Test internal API endpoint accessAttempt to access the internal configuration endpoint (typically under /api/fleet/* internal paths) using a test account with limited Fleet privileges to see if full configuration objects including private keys or tokens are returned without proper authorization checksAffected if A user with limited Fleet privileges can retrieve sensitive configuration data (private keys, authentication tokens) through internal API endpoints that the dedicated settings APIs would restrict
Your environment is affected if Kibana version is within the affected ranges AND Fleet is enabled AND users with limited Fleet privileges can access sensitive configuration through internal API endpoints that bypass authorization checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.19.149.2.89.3.3
Apply the vendor patch from Elastic when available. Until then, restrict network access to Kibana to trusted administrators only and monitor for unauthorized access to Fleet configuration endpoints.
Kibana 8.19.14+ (8.x branch), 9.2.8+ (9.0-9.2 branch), or 9.3.3+ (9.3.x branch)
- 1. Identify your current Kibana version by checking the Kibana about page or your deployment configuration
- 2. Determine which version branch you are on (8.x, 9.0-9.2, or 9.3.x)
- 3. For Kibana 8.x users: Upgrade to version 8.19.14 or later
- 4. For Kibana 9.0-9.2 users: Upgrade to version 9.2.8 or later
- 5. For Kibana 9.3.x users: Upgrade to version 9.3.3 or later
- 6. Test the upgrade in a non-production environment first, verifying Fleet functionality and that the application works as expected
- 7. Create a backup of your Kibana configuration and dashboards before upgrading
- 8. Apply the upgrade in production during a scheduled maintenance window
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Kibana
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33461 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data