› ›

Kibana 8.19.25

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

The 8.19.25 release includes the following fixes.

Alerting

Fix the rules list failing to load when Kibana can’t read the parameters of one rule. The list now shows the other rules and a warning that names the rules that couldn’t be loaded (#300110).

Data ingestion and Fleet

Fix the full agent policy APIs returning policy details without checking for Integrations read access. GET /api/fleet/agent_policies/<agentPolicyId>/full and GET /api/fleet/agent_policies/<agentPolicyId>/download now require read access to Agent policies and Integrations, and the View policy, View agent policy, and Run standalone options are turned off without it (#301951).
Fix Fleet bulk agent action APIs not validating the agents input consistently. Invalid input now returns a 400 error instead of running the action. A KQL query can reference only agent fields and is limited to 500,000 characters, and each agent ID is limited to 512 characters (#299837).
Fix integration upgrades failing with a 400 error from a proxy in front of Elasticsearch when the data stream namespace contains non-ASCII characters (#301496).

Data management

Fix creating and fetching data views with allowNoIndex: true that target a nonexistent remote cluster failing with a 400 error (#299790).

Elastic Security solution

For the Elastic Security 8.19.25 release information, refer to Elastic Security release notes.

Kibana platform

Fix bin/kibana-plugin install finishing before the last file in the plugin archive is fully written, which could leave the installed plugin directory with that file missing or empty (#301845).