Kibana, Fleet Server: restore access controls

At a glance

Kibana, Fleet Server: security control bypass. This 2026-07-02 case examines 15 version entries and 11 CVEs, documented releases and checks suited to runtime platforms, using CERTFR-2026-AVI-0826.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-07-02, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-0826, published on 2026-07-02. Its scope includes Kibana, Fleet Server, Elastic Defend, Elasticsearch. Reported consequences are denial of service, data integrity compromise, security control bypass, loss of confidentiality. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case contains 15 version entries; CVE identifier count: 11. Track remediation by component: a successful overall update does not demonstrate that Kibana and Elasticsearch each received their respective fix.

Products and versions to examine

Reference
CERTFR-2026-AVI-0826
Source first published
2026-07-02
Latest source revision available for this day
2026-07-02
Named components
Kibana, Fleet Server, Elastic Defend, Elasticsearch
CVE identifiers
CVE-2026-49091, CVE-2026-56150, CVE-2026-56151, CVE-2026-49090, CVE-2026-32283, CVE-2026-56149, CVE-2026-56152, CVE-2026-56148, CVE-2026-49089, CVE-2026-49088, CVE-2026-49087
ComponentPublished condition
Kibana8.17.x : < 8.17.2
Kibana8.19.x : < 8.19.17
Fleet Server8.x : < 8.19.15
Elastic Defend9.3.x : < 9.3.2
Kibana8.18.x : < 8.18.9
Elasticsearch9.4.x : < 9.4.3
Kibana8.x : < 8.16.3
Elastic Defend9.x : < 9.2.7
Elasticsearch8.x : < 8.19.17
Elasticsearch9.x : < 9.3.5
Elasticsearch7.x : < 7.17.24
Elastic Defendpostérieures à 8.6.x : < 8.19.13
Kibana7.x : < 7.17.15
Fleet Server9.x : < 9.3.4

For Kibana, the published condition is “8.17.x : < 8.17.2”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Kibana, Fleet Server does not close this case.

Mechanism and prerequisites

A security bypass challenges a trust boundary. Verify server-side authorisation decisions and alternative paths; hiding an interface is not an access restriction.

The primary record CVE-2026-49091, published by elastic, covers Kibana. The retained revision is dated 2026-07-02. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-0826.

The published metric for CVE-2026-49091 is CVSS 3.1, 8/10. The vector below describes technical prerequisites; it does not measure attack frequency or the likelihood that your deployment is compromised.

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

Attack vector
network
Prior privileges
low
User interaction
required
Complexity
high
Weakness
CWE-116

Choose the appropriate intervention

  1. Locate Kibana instances, running releases and service owners. Record condition 8.17.x : < 8.17.2 in the ticket alongside reference CERTFR-2026-AVI-0826.
  2. Compare the installed branch with the vendor’s Kibana release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing Kibana, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for Kibana, Fleet Server: For Kibana, capture the version loaded by the process or active kernel, then restart only as required by maintenance instructions. Check a dependent workflow and look for embedded copies in distributed images or executables. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-0826: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for Kibana?

Advisory CERTFR-2026-AVI-0826 states: Kibana — 8.17.x : < 8.17.2. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

Why not use one fix for Kibana and Elasticsearch?

CERTFR-2026-AVI-0826 distinguishes these components within a scope containing 15 entries. Match each branch to its own update documentation and functional check.

Which prerequisites does record CVE-2026-49091 specify?

For CVE-2026-49091, the published vector is CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H. Verify those conditions on Kibana before applying them to an integration named in CERTFR-2026-AVI-0826.

Sources and related reading

Practical guide : Prioritize vulnerabilities and verify remediation

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-0826
Advisory revision : · Checked on :

Affected systems · 15

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. Kibana versions 8.17.x antérieures à 8.17.2
  2. Kibana versions 8.19.x antérieures à 8.19.17
  3. Fleet Server versions 8.x antérieures à 8.19.15
  4. Elastic Defend versions 9.3.x antérieures à 9.3.2
  5. Kibana versions 8.18.x antérieures à 8.18.9
  6. Elasticsearch versions 9.4.x antérieures à 9.4.3
  7. Kibana versions 8.x antérieures à 8.16.3
  8. Elastic Defend versions 9.x antérieures à 9.2.7
  9. Elasticsearch versions 8.x antérieures à 8.19.17
  10. Elasticsearch versions 9.x antérieures à 9.3.5
  11. Elasticsearch versions 7.x antérieures à 7.17.24
  12. Elastic Defend versions postérieures à 8.6.x antérieures à 8.19.13
  13. Kibana versions 7.x antérieures à 7.17.15
  14. Kibana versions 9.x antérieures à 9.0.8, 9.1.6, 9.3.6 ou 9.4.3
  15. Fleet Server versions 9.x antérieures à 9.3.4
CVE identifiers · 11