[Security] 8.19.20 release notes - #7197
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
natasha-moore-elastic
requested review from
NicholasPeretti,
PhilippeOberti,
agusruidiazgd,
denar50,
dhurley14,
gogochan and
maximpn
August 7, 2026 09:57
PhilippeOberti
approved these changes
Aug 7, 2026
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
gogochan
reviewed
Aug 7, 2026
gogochan
reviewed
Aug 7, 2026
gogochan
reviewed
Aug 7, 2026
4 tasks
Co-authored-by: gogochan <5281995+gogochan@users.noreply.github.com>
bmorelli25
reviewed
Aug 7, 2026
| * Fixes an issue where the **Source event** link in an alert's **Highlighted fields** section failed to open the document when it lived in a hidden restored or partial index ({kibana-pull}282272[#282272]). | ||
| * Fixes a privilege bypass that allowed users with detection rule privileges to attach {elastic-defend} or Osquery response actions through the generic Alerting API without the required Endpoint or Osquery privileges ({kibana-pull}280430[#280430]). | ||
| * Fixes the analyzer alert-hits query so it honors the `securitySolution:excludeColdAndFrozenTiersInAnalyzer` setting, which previously excluded cold and frozen tiers only from other analyzer queries ({kibana-pull}278972[#278972]). | ||
| * Fixes a crash when opening the rule panel flyout for a deleted rule caused by missing `severity_mapping` or `risk_score_mapping` fields ({kibana-pull}278545[#278545]). |
Member
There was a problem hiding this comment.
This one already exists in 8.19.19 rn's.
bmorelli25
reviewed
Aug 7, 2026
| * Fixes a privilege bypass that allowed users with detection rule privileges to attach {elastic-defend} or Osquery response actions through the generic Alerting API without the required Endpoint or Osquery privileges ({kibana-pull}280430[#280430]). | ||
| * Fixes the analyzer alert-hits query so it honors the `securitySolution:excludeColdAndFrozenTiersInAnalyzer` setting, which previously excluded cold and frozen tiers only from other analyzer queries ({kibana-pull}278972[#278972]). | ||
| * Fixes a crash when opening the rule panel flyout for a deleted rule caused by missing `severity_mapping` or `risk_score_mapping` fields ({kibana-pull}278545[#278545]). | ||
| * Fixes an issue where {kib} assets from an installed integration package (such as dashboards used by prebuilt detection rules) could remain stale across a {kib} upgrade because {fleet} never overwrote existing assets on reinstall ({kibana-pull}277953[#277953]). |
bmorelli25
reviewed
Aug 7, 2026
| * Fixes a crash when opening the rule panel flyout for a deleted rule caused by missing `severity_mapping` or `risk_score_mapping` fields ({kibana-pull}278545[#278545]). | ||
| * Fixes an issue where {kib} assets from an installed integration package (such as dashboards used by prebuilt detection rules) could remain stale across a {kib} upgrade because {fleet} never overwrote existing assets on reinstall ({kibana-pull}277953[#277953]). | ||
| * Fixes a crash in index fields formatting when a field or index is named after an `Object.prototype` property such as `constructor`, `toString`, or `__proto__` ({kibana-pull}277851[#277851]). | ||
| * Fixes an error when opening a source event from the **Highlighted fields** section of the alert details flyout when the source index had been restored, and renamed, from a cold or frozen tier ({kibana-pull}277703[#277703]). |
Contributor
Author
There was a problem hiding this comment.
Hmm all of these originally had the 8.19.19 label, which was later replaced with 8.19.20.
Looking at the 8.19.19 build, none of these actually made it into 8.19.19, so I'll remove them from there.
Thanks for flagging!
nastasha-solomon
approved these changes
Aug 7, 2026
nastasha-solomon
left a comment
nastasha-solomon
left a comment
Member
There was a problem hiding this comment.
Approving to unblock (if needed)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolves elastic/docs-content#7837: adds the 8.19.20 Security and Endpoint release notes.
Made with Cursor