CVE-2025-37728 json
Kibana Insufficiently Protected Credentials in the CrowdStrike Connector
published last yr. modified last mo. also BIT-elk-2025-37728 , BIT-kibana-2025-37728 , EUVD-2025-32080
- cvss
- 5.4
- 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
Insufficiently Protected Credentials in the Crowdstrike connector can lead to Crowdstrike credentials being leaked. A malicious user can access cached credentials from a Crowdstrike connector in another space by creating and running a Crowdstrike connector in a space to which they have access.
Patch / fix
- bitnami elk 8.18.8, 8.19.5, 9.0.8, 9.1.5
- bitnami kibana 8.18.8, 8.19.5, 9.0.8, 9.1.5
- elastic kibana 8.18.8, 8.19.5, 9.0.8, 9.1.5
- elasticsearch kibana 8.18.8, 8.19.5, 9.0.8, 9.1.5
Is CVE-2025-37728 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-37728 updated cvss 5.4
kibana: Kibana Insufficiently Protected Credentials in the CrowdStrike Connector
-
Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8affected: no fix available “Fix deferred”
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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- discuss.elastic.co https://discuss.elastic.co/t/kibana-crowdstrike-connector-8-18-8-8-19-5-9-0-8-and-9-1-5-security-update-esa-2025-19/382455 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| OSV | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | elk | <8.18.8 >=8.19.0, <8.19.5 >=9.0.0, <9.0.8 >=9.1.0, <9.1.5 |
8.18.8 8.19.5 9.0.8 9.1.5 |
| bitnami | kibana | <8.18.8 >=8.19.0, <8.19.5 >=9.0.0, <9.0.8 >=9.1.0, <9.1.5 |
8.18.8 8.19.5 9.0.8 9.1.5 |
Affected products
- Elastic Kibana
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
Sources
- CVE List CVE-2025-37728
- NVD CVE-2025-37728
- OSV BIT-elk-2025-37728
- OSV BIT-kibana-2025-37728
Fencer Intel 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.