dbcve.org
KibanaApplication · Elastic

CVE-2025-25015

CRITICAL · 9.9 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 8.16.6 / 8.17.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Prototype pollution in Kibana leads to arbitrary code execution via a crafted file upload and specifically crafted HTTP requests. In Kibana versions >= 8.15.0 and < 8.17.1, this is exploitable by users with the Viewer role. In Kibana versions 8.17.1 and 8.17.2 , this is only exploitable by users that have roles that contain all the following privileges: fleet-all, integrations-all, actions:execute-advanced-connectors

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 · high confidence

Kibana versions 8.15.0 through 8.17.2 contain a prototype pollution vulnerability that allows authenticated users to achieve arbitrary code execution through specially crafted file uploads combined with specific HTTP requests. The vulnerability stems from insufficient sanitization of object properties during file processing, enabling attackers to modify JavaScript prototype objects.

MitigationUpgrade Kibana to version 8.17.3 or later. For versions 8.17.1 and 8.17.2, ensure users do not have the combination of fleet-all, integrations-all, and actions:execute-advanced-connectors privileges unless the upgrade is applied.

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.15.0, < 8.16.6>= 8.17.0, < 8.17.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
High
Availability
High

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

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

  1. Identify Kibana version
    Run `kibana --version` or check the Kibana logs at startup, or query the Kibana API endpoint `GET /api/status`
    Affected if Version is >= 8.15.0 and < 8.16.6, OR >= 8.17.0 and < 8.17.3
  2. Confirm Viewer role assignment
    Review Kibana role mappings in Management > Security > Roles, or query the security API, to identify users assigned the Viewer role
    Affected if Any authenticated user has the Viewer role assigned in versions 8.15.0 through 8.17.0
  3. Check for elevated privileges in 8.17.x
    Review role configurations for users to determine if any role includes all three privileges: fleet-all, integrations-all, and actions:execute-advanced-connectors
    Affected if Any user has a role containing all three privileges in versions 8.17.1 or 8.17.2
  4. Verify file upload capability
    Check if the upload feature for saved objects, reports, or files is enabled in the Kibana configuration under `xpack.reporting.enabled` or similar settings
    Affected if File upload features are accessible to the roles identified above

User is affected if Kibana version falls within the vulnerable ranges AND authenticated users have Viewer role (8.15.0-8.17.0) or the specific privilege combination (8.17.1-8.17.2) with file upload access enabled.

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.16.6 / 8.17.3 or later
Fixed in 8.16.68.17.3
Interim mitigation

Upgrade Kibana to version 8.17.3 or later. For versions 8.17.1 and 8.17.2, ensure users do not have the combination of fleet-all, integrations-all, and actions:execute-advanced-connectors privileges unless the upgrade is applied.

Recommended fix High confidence

8.16.6 (for 8.15.x/8.16.x) or 8.17.3 (for 8.17.x)

  1. 1. Identify the current Kibana version by checking the Kibana about page or running `bin/kibana --version`
  2. 2. If running 8.15.x or 8.16.x (less than 8.16.6), plan upgrade to version 8.16.6
  3. 3. If running 8.17.x (less than 8.17.3), plan upgrade to version 8.17.3
  4. 4. Create a full backup of the Kibana configuration directory (usually `kibana.yml` and any custom settings)
  5. 5. Create a snapshot of Elasticsearch indices if Kibana stores state there, or ensure data can be restored
  6. 6. Stop the Kibana service
  7. 7. Upgrade Kibana to the appropriate fixed version: 8.16.6 (for 8.15.x/8.16.x branches) or 8.17.3 (for 8.17.x branch)
  8. 8. Start the Kibana service
Caveat Review Elastic Stack 8.16 and 8.17 release notes for any breaking changes; minor version upgrades typically have minimal breaking changes

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25015 — 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-2025-25015 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