Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-72669: The state that Kibana stores for an Observability Onboarding flow is not bound to the user who created the flo

33
Routine
HIGH 7.6UPGRADE

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

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

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.6 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 74%)
CISA exploited listNo
WeaknessCWE-862
Published2026-08-13
Last modified2026-09-04
Publisher (CNA): Elastic · Vendor: elastic

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

elastic kibana UPGRADE
Affected: >= 8.9.0 and < 8.19.19 · >= 9.0.0 and < 9.4.5
Fixed in: 8.19.19, 9.4.5
Safe to downgrade to: a release before 8.9.0
1. Check installed version
apt-cache policy kibana || rpm -q kibana || kibana --version
2. UPGRADE to 8.19.19 (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.9.0 (Debian / Ubuntu)
apt-cache madison kibana sudo apt install kibana=<VERSION_BEFORE_8.9.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.9.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-72669?

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

Is CVE-2026-72669 being exploited?

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

CVE-2026-72669 affects kibana. Severity is high (CVSS 7.6). 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 acces

How urgent is CVE-2026-72669?

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