Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-72630: Incorrect Authorization (CWE-863) in Kibana Fleet can lead to privilege escalation via Privilege Abuse (CAPEC-

31
Routine
HIGH 7.1UPGRADE

CVE-2026-72630 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.

Incorrect Authorization (CWE-863) in Kibana Fleet can lead to privilege escalation via Privilege Abuse (CAPEC-122). Fleet restricts some callers to managing integration policies for one specific integration. When an existing integration policy was updated, that restriction was evaluated against the integration recorded on the stored policy rather than against the replacement integration supplied with the update. An authenticated user holding only

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 77%)
CISA exploited listNo
WeaknessCWE-863
Published2026-08-13
Last modified2026-09-02
Publisher (CNA): Elastic · Vendor: elastic

Share: LinkedIn · X · Reddit

Last updated 2026-09-02 · 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.20 · >= 9.0.0 and < 9.4.5 · 9.5.0
Fixed in: 8.19.20, 9.4.5
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.20 (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-72630?

kibana: upgrade to 8.19.20, 9.4.5. Exact commands for each OS are on this page.

Is CVE-2026-72630 being exploited?

CVE-2026-72630 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-72630 affect?

CVE-2026-72630 affects kibana. Severity is high (CVSS 7.1). Incorrect Authorization (CWE-863) in Kibana Fleet can lead to privilege escalation via Privilege Abuse (CAPEC-122). Fleet restricts some callers to managing integration policies for one specific integration. When an existing integration pol

How urgent is CVE-2026-72630?

Priority 31/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.