KibanaApplication · Elastic
CVE-2026-33462
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 · uneditedA path traversal vulnerability was identified in Kibana's dashboard management functionality. An authenticated user with limited permissions could create a dashboard with a specially crafted identifier. When an administrator subsequently attempts to delete this dashboard through the Kibana interface, the deletion request is redirected to an unintended internal endpoint, potentially resulting in the unauthorized deletion of user accounts or other resources. Exploitation requires an administrator to perform a delete action on the maliciously crafted dashboard object.
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 confidenceA path traversal vulnerability in Kibana's dashboard management allows an authenticated low-privilege user to create a dashboard with a specially crafted identifier. When an administrator attempts to delete this malicious dashboard, the deletion request gets redirected to an unintended internal endpoint due to insufficient input validation on the dashboard identifier, potentially enabling unauthorized deletion of user accounts or other internal resources.
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.16>= 9.0.0, < 9.3.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H
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.
-
Check Kibana versionRun `bin/kibana --version` or check the version in the Kibana log file (kibana.yml config path typically /etc/kibana/kibana.yml). Alternatively, query the Kibana API: `curl -s http://localhost:5601/api/status` and look for the 'version.number' field.Affected if The installed version falls within 8.0.0 to 8.19.15 (inclusive), or 9.0.0 to 9.3.4 (inclusive).
-
Verify dashboard feature is accessibleConfirm that the Kibana dashboard management functionality is enabled. Check the kibana.yml configuration file for any disabled dashboard-related plugins or permissions. Ensure authenticated users can access the dashboard creation UI or API endpoint at /api/kibana/dashboards.Affected if Dashboard management feature is enabled and accessible to authenticated users (including low-privilege users).
-
Inspect existing dashboards for path traversal patternsQuery the Kibana saved objects API to list all dashboards: `curl -s -u elastic:<password> http://localhost:5601/api/saved_objects/_find?type=dashboard`. Review each dashboard's ID or title for suspicious patterns such as '../', '..%2F', '%2E%2E/', or strings that may indicate attempts to manipulate deletion targets.Affected if Any dashboard object contains an identifier or title with path traversal characters (../, ..%2F, encoded dots, or unusual path-like strings).
-
Review audit logs for anomalous deletion requestsCheck Kibana audit logs (typically in /var/log/kibana/audit.json or via the audit API). Look for DELETE operations on dashboards where the target ID contains path traversal patterns, or where the deletion request was routed to unexpected internal endpoints. Search for entries with 'action': 'dashboard_delete' and unusual 'meta' or 'url' fields.Affected if Audit logs show dashboard deletion requests with path traversal patterns in the dashboard identifier, or deletions routing to unexpected API endpoints (not the standard /api/kibana/dashboards/{id} pattern).
You are affected if Kibana version is 8.0.0-8.19.15 or 9.0.0-9.3.4 AND the dashboard management feature is accessible to authenticated users AND suspicious dashboards with path traversal identifiers exist or anomalous deletion requests appear in audit logs.
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.169.3.5
Implement strict input validation on dashboard identifiers to reject path traversal patterns (e.g., ../, encoded slashes) and ensure all deletion requests are validated against the expected target resource before execution.
Kibana 8.19.16+ or 9.3.5+ (depending on major version)
- Upgrade Kibana 8.x installations to version 8.19.16 or later
- Upgrade Kibana 9.x installations to version 9.3.5 or later
- After upgrading, verify that the dashboard deletion functionality works correctly by testing with a normal dashboard
- Confirm that the path traversal vulnerability is no longer exploitable by attempting to create dashboards with special characters in identifiers
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Kibana
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33462 — 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-33462 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