dbcve.org
KibanaApplication · Elastic

CVE-2026-4498

HIGH · 7.7 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 8.19.14 / 9.2.8 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Execution with Unnecessary Privileges (CWE-250) in Kibana’s Fleet plugin debug route handlers can lead reading index data beyond their direct Elasticsearch RBAC scope via Privilege Abuse (CAPEC-122). This requires an authenticated Kibana user with Fleet sub-feature privileges (such as agents, agent policies, and settings management).

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 confidence

Kibana's Fleet plugin debug route handlers execute with unnecessary privileges (CWE-250), allowing authenticated users with Fleet sub-feature privileges (agents, agent policies, settings management) to bypass Elasticsearch RBAC restrictions and read index data outside their authorized scope via privilege abuse (CAPEC-122).

MitigationApply vendor patches for CVE-2026-4498 when released; in the interim, restrict access to Fleet debug routes and audit user Fleet privilege assignments to limit exposure.

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
Affected:>= 8.0.0, < 8.19.14>= 9.0.0, < 9.2.8>= 9.3.0, < 9.3.3

CVSS 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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kibana version
    Check the installed Kibana version (typically via kibana --version, package metadata, or the /api/status endpoint)
    Affected if The 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
  2. Verify Fleet plugin is enabled
    Confirm the Fleet plugin is installed and active in Kibana (check plugin list via GET /api/plugins or Kibana configuration)
    Affected if Fleet plugin is present and enabled in the Kibana instance
  3. Confirm debug route accessibility
    Identify if Fleet debug endpoints are accessible (commonly /api/fleet/debug/* or similar debug paths under the Fleet API namespace)
    Affected if Fleet debug routes are exposed and reachable by authenticated users
  4. Review Fleet sub-feature privilege assignments
    Examine user or role configurations for assignments to Fleet sub-features (agents, agent policies, or settings management) within Elasticsearch RBAC
    Affected if Any users possess Fleet sub-feature privileges that grant broader access than intended
  5. Audit Elasticsearch index access patterns
    Review Kibana/Fleet audit logs or access logs for cross-tenant or out-of-scope index read operations originating from Fleet debug routes
    Affected if Users with Fleet sub-feature privileges have accessed index data outside their authorized scope

A user is affected if their Kibana version is in the vulnerable range, Fleet is enabled, and users with Fleet sub-feature privileges can access index data beyond their defined Elasticsearch RBAC scope.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.19.14 / 9.2.8 / 9.3.3 or later
Fixed in 8.19.149.2.89.3.3
Interim mitigation

Apply vendor patches for CVE-2026-4498 when released; in the interim, restrict access to Fleet debug routes and audit user Fleet privilege assignments to limit exposure.

Recommended fix High confidence

8.19.14 for Kibana 8.x; 9.2.8 for Kibana 9.0-9.2.x; 9.3.3 for Kibana 9.3.x

  1. Identify your current Kibana major version (8.x or 9.x)
  2. If running Kibana 8.x: Upgrade to version 8.19.14 or later
  3. If running Kibana 9.0.x through 9.2.x: Upgrade to version 9.2.8 or later
  4. If running Kibana 9.3.x: Upgrade to version 9.3.3 or later
  5. After upgrading, verify that Fleet plugin functionality works correctly and that the debug route handlers now properly enforce RBAC boundaries

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kibana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4498 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4498 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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