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

> Authenticated attackers can exploit SSRF and path traversal in the Kibana Google Gemini connector to disclose arbitrary files and make internal network requests.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2026
- **Updated:** 14 Sep 2026
- **Also known as:** BIT-elk-2026-0532, BIT-kibana-2026-0532, GHSA-pgjq-pwjv-wjpx, MINI-55jv-jc63-6mfw, MINI-789q-rv6c-c7m8, MINI-8982-5qpp-qgf2, MINI-gprr-wxcf-fx4h, MINI-q8wv-9p4m-gh5h, MINI-vqj4-jhc3-g8mj

## What is CVE-2026-0532?

CVE-2026-0532 is a high-severity server-side request forgery vulnerability in Elastic Kibana, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-0532?

2 open source packages ship an affected version, including kibana and elk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kibana` | Bitnami | All versions | 8.19.10, 9.1.10, 9.2.4 |
| `elk` | Bitnami | All versions | 8.19.10, 9.1.10, 9.2.4 |

## How do I fix CVE-2026-0532?

Upgrade kibana to a fixed version for your release line: 8.19.10, 9.1.10 or 9.2.4.

## Is CVE-2026-0532 being exploited?

There is no known exploitation of CVE-2026-0532 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0532 and fix it if it is affected.

What it is: CVE-2026-0532 is a high-severity server-side request forgery vulnerability in Elastic Kibana, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0532 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected all versions; fixed in 8.19.10, 9.1.10, 9.2.4
- elk (Bitnami): affected all versions; fixed in 8.19.10, 9.1.10, 9.2.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0532/ (Markdown: https://insights.sbomify.com/CVE-2026-0532/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0532
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0532
- OSV: https://osv.dev/vulnerability/CVE-2026-0532

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0532/
Summaries are generated and may contain mistakes; the official description above is the record.