Elastic Kibana Updates Address Authorization, Privilege, and Availability Risks

P1 — VALIDATE AND UPDATEMedium to High · 6.3 / 6.5 / 7.3 (official CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

These four Kibana advisories do not share one affected-version range. Check Agent Builder and Workflows, Timeline, Synthetics, and the listed resource-consumption issue separately. Choose a supported release that fixes every issue applicable to your deployment, not just the first version named in the table.

Confirm Scope And Apply The Supported Fix

Next step: Record the Kibana branch, enabled features, spaces, and relevant roles. Compare that inventory with all four Elastic advisories and plan a compatible stack upgrade.

Open the authoritative advisory

Last verified: 2026-09-26 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeKibana 7.x, 8.x, and 9.x branches and features enumerated in ESA-2026-85, 103, 139, and 181
AdvisoryESA-2026-85 / ESA-2026-103 / ESA-2026-139 / ESA-2026-181
CVEsCVE-2026-72662, CVE-2026-72668, CVE-2026-78582, CVE-2026-94400
Authoritative release date2026-09-25 08:31:59 UTC
Authority revision dateNo separate revision date published
Affected versionsAdvisory-specific Kibana scope: ESA-2026-85 affects Agent Builder and Workflows in 9.4.0 through 9.4.6; ESA-2026-103 affects 8.0.0 through 8.19.21 and 9.4.0 through 9.4.5; ESA-2026-139 affects 7.12.0 through 7.17.29, 8.0.0 through 8.19.21, 9.0.0 through 9.4.6, and 9.5.0 through 9.5.2; ESA-2026-181 affects 8.0.0 through 8.19.21, 9.0.0 through 9.4.6, and 9.5.0 through 9.5.2.
Fixed versionthe exact authority-listed branch release: Kibana 9.4.7 / 9.5.0 for ESA-2026-85; 8.19.22 / 9.4.6 for ESA-2026-103; and 8.19.22 / 9.4.7 / 9.5.3 for ESA-2026-139 and ESA-2026-181
CVSS base score6.3 / 6.5 / 7.3 (official CVSS v3.1)
CVSS severityMedium to High
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

The notices cover a confused-deputy privilege problem, Timeline authorization, cross-space Synthetics monitor deletion, and denial of service. Feature and role conditions differ. A working dashboard does not demonstrate that cross-space access or agent privileges are enforced correctly.

What To Validate Now

  1. Inventory. Locate Kibana 7.x, 8.x, and 9.x branches and features enumerated in ESA-2026-85, 103, 139, and 181 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: Advisory-specific Kibana scope: ESA-2026-85 affects Agent Builder and Workflows in 9.4.0 through 9.4.6; ESA-2026-103 affects 8.0.0 through 8.19.21 and 9.4.0 through 9.4.5; ESA-2026-139 affects 7.12.0 through 7.17.29, 8.0.0 through 8.19.21, 9.0.0 through 9.4.6, and 9.5.0 through 9.5.2; ESA-2026-181 affects 8.0.0 through 8.19.21, 9.0.0 through 9.4.6, and 9.5.0 through 9.5.2. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply the exact authority-listed branch release: Kibana 9.4.7 / 9.5.0 for ESA-2026-85; 8.19.22 / 9.4.6 for ESA-2026-103; and 8.19.22 / 9.4.7 / 9.5.3 for ESA-2026-139 and ESA-2026-181 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Use disposable objects and controlled roles to verify allowed and denied Timeline and Synthetics actions across spaces. Test approved Agent Builder workflows and normal dashboards, watching resource use and errors. Do not use production monitors or privileged credentials for destructive regression tests.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.