# CVE-2026-56152: Incorrect Authorization in Kibana Leading to Information Disclosure

> A low-privileged authenticated user can access unauthorized response action data in Kibana due to incorrect authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-vvj5-p4vc-v5q3

## What is CVE-2026-56152?

CVE-2026-56152 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect Authorization (CWE-863) in Kibana can lead to unauthorized information disclosure via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). Under certain conditions, a low-privileged authenticated user can access response action data that they are not authorized to view.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Elastic Endpoint Security.

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

No fix has been published for CVE-2026-56152 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56152 being exploited?

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

## Other vulnerabilities in Elastic Kibana

- [CVE-2022-38775](https://insights.sbomify.com/CVE-2022-38775/): Privilege escalation in Elastic Endpoint Security (high 7.8)
- [CVE-2022-23714](https://insights.sbomify.com/CVE-2022-23714/): Privilege escalation in Endpoint Security (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56152 is a medium-severity missing authorization vulnerability in Elastic Kibana, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56152 in the wild and no public exploit code.

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-56152/ (Markdown: https://insights.sbomify.com/CVE-2026-56152/index.md)
```

## Sources

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

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