Skip to content
Fencer Vulns
medium 6.5

CVE-2025-25010 json

Kibana privilege escalation via reporting_user role

published 2025-08-28 14 mo ago modified 2026-09-08 2 mo ago also BIT-elk-2025-25010 , BIT-kibana-2025-25010 , EUVD-2025-26116

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

Incorrect authorization in Kibana can lead to privilege escalation via the built-in reporting_user role which incorrectly has the ability to access all Kibana Spaces.

Patch / fix

  • bitnami elk 9.0.6, 9.1.3
  • bitnami kibana 9.0.6, 9.1.3
  • elastic kibana 9.0.6, 9.1.3
  • elasticsearch kibana 9.0.6, 9.1.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-25010 updated cvss 6.5

kibana: Kibana privilege escalation

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
14 mo ago

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami elk
>=9.0.0, <9.0.6
>=9.1.0, <9.1.3
9.0.6
9.1.3
bitnami kibana
>=9.0.0, <9.0.6
>=9.1.0, <9.1.3
9.0.6
9.1.3

Affected products

  • Elastic Kibana

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.