Skip to content
Fencer Vulns
high 8.6

CVE-2026-0532 json

External Control of File Name or Path and Server-Side Request Forgery (SSRF) in Kibana Google Gemini Connector

published 2026-01-14 9 mo ago modified 2026-09-14 55 d ago also BIT-elk-2026-0532 , BIT-kibana-2026-0532 , EUVD-2026-2517

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

Summary

External Control of File Name or Path (CWE-73) combined with Server-Side Request Forgery (CWE-918) can allow an attacker to cause arbitrary file disclosure through a specially crafted credentials JSON payload in the Google Gemini connector configuration. This requires an attacker to have authenticated access with privileges sufficient to create or modify connectors (Alerts & Connectors: All). The server processes a configuration without proper validation, allowing for arbitrary network requests and for arbitrary file reads.

Patch / fix

  • bitnami elk 8.19.10, 9.1.10, 9.2.4
  • bitnami kibana 8.19.10, 9.1.10, 9.2.4
  • elastic kibana 8.19.10, 9.1.10, 9.2.4
  • elasticsearch kibana 8.19.10, 9.1.10, 9.2.4

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-2026-0532 updated cvss 8.6

Kibana: Kibana: Arbitrary file disclosure via specially crafted connector configuration

  • Red Hat OpenShift distributed tracing 3 rhosdt/tempo-jaeger-query-rhel8
    affected: workaround, no fix available
  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8, openshift-logging/elasticsearch-rhel9-operator, openshift-logging/cluster-logging-rhel9-operator Red Hat JBoss Enterprise Application Platform 8 kibana Red Hat JBoss Enterprise Application Platform Expansion Pack kibana
    not affected: vulnerable code not present
  • Red Hat OpenStack Platform 16.2 puppet-kibana3
    not affected: component 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
yes
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami elk
<8.19.10
>=9.0.0, <9.1.10
>=9.2.0, <9.2.4
8.19.10
9.1.10
9.2.4
bitnami kibana
<8.19.10
>=9.0.0, <9.1.10
>=9.2.0, <9.2.4
8.19.10
9.1.10
9.2.4

Affected products

  • Elastic Kibana
  • Red Hat Logging Subsystem for Red Hat OpenShift
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Red Hat Red Hat OpenShift distributed tracing 3
  • Red Hat Red Hat OpenStack Platform 16.2

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

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.