All Release Notes Reporter for Cisco Firepower 1.0.3.106 (2026-06-08)

Scheduled Reports: Fixed an issue introduced in 1.0.3.105 that could cause the Reporter service to crash while generating many scheduled reports.
Security update: Updated Log4j to 2.25.4 to address CVE-2025-68161 (Apache Log4j Core: missing TLS hostname verification in the Socket appender).
Printing: The sidebar is no longer included when printing a report or a private report directly from the browser.

Filtering interface: A range of refinements to the Microsoft 365 filtering interface in Settings > Microsoft 365. Filter options are now shown immediately instead of a blocking ‘loading’ panel, and section headings clearly indicate that User and Group filters only apply to Emails and Chat messages, not Teams and Channels.
Subject line matches: Fixed an issue where emails with a keyword match in the Subject line were not appearing in the Safeguarding Report.
Keyword Groups: Fixed an issue where the same email or chat message could be attributed to the wrong Keyword Group when the Subject matched one group and the Message Body matched another. Both matches are now reflected correctly in the Safeguarding Report.
Import size: When only the Subject (Email or Channel Subject) matches a keyword, the imported Message Body is now correctly limited to 250 characters, reducing unnecessary import size and storage.
Keyword highlighting: Fixed issues with keyword highlighting in the full message context view for Microsoft 365 messages and emails.
Group filters: Fixed an ‘Invalid Object Identifier’ error that could occur when filtering Microsoft 365 imports by multiple Groups.
Import errors: Fixed errors that could occur during Microsoft 365 import, specifically ‘An item with the same key has already been added’ when gathering users for a tenant, and ‘has to be unique in a batch’ when importing emails.

Videos do not display in the Safeguarding Report. Fixed in 1.0.3.107.
On some Linux instances, Elasticsearch indexes can get stuck in a ‘semi-recovered’ state on startup with unassigned shards, requiring manual intervention. Fixed in 1.0.3.107.

Download Latest Update