Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-56147: Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized information disc

32
Routine
HIGH 7.1UPGRADE

CVE-2026-56147 is a high-severity flaw (CVSS 7.1) affecting kibana. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized information disclosure and case attachment integrity compromise via Privilege Abuse (CAPEC-122). An inconsistency in Kibana's file access authorization logic allows a low-privileged authenticated user to retrieve, modify, and delete case attachments that belong to feature areas they are not authorized to access. Because the access control check and the r

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.1 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 73%)
CISA exploited listNo
WeaknessCWE-639
Published2026-07-21
Last modified2026-10-24
Publisher (CNA): Elastic · Vendor: elastic

Share: LinkedIn · X · Reddit

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

elastic kibana UPGRADE
Affected: >= 8.19.0 and < 8.19.18 · >= 9.3.0 and < 9.3.7 · >= 9.4.0 and < 9.4.3
Fixed in: 8.19.18, 9.3.7, 9.4.3
Safe to downgrade to: a release before 8.19.0
1. Check installed version
apt-cache policy kibana || rpm -q kibana || kibana --version
2. UPGRADE to 8.19.18 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade kibana
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade kibana
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 8.19.0 (Debian / Ubuntu)
apt-cache madison kibana sudo apt install kibana=<VERSION_BEFORE_8.19.0> sudo apt-mark hold kibana
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list kibana sudo dnf downgrade kibana-<VERSION_BEFORE_8.19.0> sudo dnf versionlock add kibana
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-56147?

kibana: upgrade to 8.19.18, 9.3.7, 9.4.3. Exact commands for each OS are on this page.

Is CVE-2026-56147 being exploited?

CVE-2026-56147 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-56147 affect?

CVE-2026-56147 affects kibana. Severity is high (CVSS 7.1). Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized information disclosure and case attachment integrity compromise via Privilege Abuse (CAPEC-122). An inconsistency in Kibana's file access authoriz

How urgent is CVE-2026-56147?

Priority 32/100. High severity

Software pages

Kibana vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.