[BESAdmin-Announcements] BigFix Compliance: Availability of BigFix Compliance Analytics version 2.0 Patch 19

[Announcements for BES Administrators]

Product: BigFix Compliance
Title: Availability of BigFix Compliance Analytics version 2.0 Patch 19
Published site: SCM Reporting TBD
Overview:
HCL BigFix is pleased to announce the release of BigFix Compliance
Analytics version 2.0
Patch 19.
This release includes
 PSIRTS:
o PRB0173949 - CVE-2026-8646, CVE-2026-9320, CVE-2026-9071
o PRB0175667 - CVE-2026-10842
o PRB0169739 - CVE-2025-14917, CVE-2026-1561
o PRB0171626 - CVE-2026-22016, CVE-2026-22021, CVE-2026-22013,
o CVE-2026-22018, CVE-2026-34268, CVE-2026-22007
o PRB0174368 - CVE-2026-11541
o PRB0173933 - CVE-2026-47240, CVE-2026-47242
o PRB0175990 - CVE-2026-15057, CVE-2026-11897
o PRB0176510 - CVE-2026-14529, CVE-2026-14981, CVE-2026-15064, CVE-2026-
15328, CVE-2026-15325
 Upgrade to Sumeru Java 21.0.12.1
 Upgrade to IBM WebSphere Liberty 26.0.0.9
 Upgrade to Rails 8.1.3.1
 Support for Windows 2025
 Support for MS SQL2025
 API's support for bulk Exception deletion
This release also includes the below Minor enhancement:
DA # Title
NA E-mail notification upon data import failure
NA Improved Rollup Table handling
NA API's support for bulk Exception deletion
Classification: Internal
Actions to take:
1. Upgrade BigFix Compliance Analytics to version 2.0.18 to take advantage
of the fixes.
For first-time installations:
1. In the License Overview Dashboard in the BigFix console (BigFix
Management domain),
enable the SCM Reporting site.
2. In the Security Configuration domain in the console, open the
Configuration Management
navigation tree.
3. Select the Fixlet named BigFix Compliance Server 2.0 - First-time
Install Fixlet under the
BigFix Compliance Install/Upgrade menu tree node.
4. Follow the Fixlet instructions and take the associated action to install
your BigFix
Compliance deployment.
For upgrade installations: Refer to the below upgrade steps for the BigFix
Compliance version
that you are using.
IMPORTANT: Before you start any upgrade process, perform a server and
database backup.
A. For BigFix Compliance Analytics versions 1.9.x, 1.10.x and 2.0.x:
1. Make sure that you complete the server and database backup.
2. It is recommended to stop the BigFix Compliance Server or at least
disable scheduled
Data Imports to ensure that Data Import is not in progress during the
upgrade.
3. In the Security Configuration domain in the console, open the
Configuration Management
navigation tree.
4. Under the BigFix Compliance Install/Upgrade menu tree item, select the
BigFix
Compliance Server 2.0 - Upgrade Fixlet which automatically installs and
upgrades to the
new version.
5. Follow the Fixlet instructions and take the associated action to upgrade
your BigFix
Compliance deployment.
6. Update the data schema. To do this, log in to the BigFix Compliance web
interface from
the host server and proceed with configuration. Upgrading the data scheme
is expected
and it will take some time to complete. NOTE: Automatic upgrade
installation only affects
installations running under the LocalSystem account. Follow the Fixlet
instructions to
install the update manually if this fix cannot be applied.
B. For BigFix Compliance Analytics versions before 1.9:
1. Manually upgrade to version 1.10.1.48. The 1.10.1.48 installer can be
found here
http://software.bigfix.com/download/bfc/server/1.10/bfc-server-1.10.1.48.exe

2. After manually upgrading to version 1.10.1.48, use the BigFix Compliance
Server 2.0
Upgrade Fixlet to upgrade to version 2.0 (See step A).
More information:
● BigFix Compliance Guide:
https://help.hcl-software.com/bigfix/11.0/compliance/Compliance/SCA_Users_Guide/

securityandcomplianceanalyticsuserguide.html
Classification: Internal
● BigFix Forums - Release Announcements Channel:
https://forum.bigfix.com/c/release
announcements/compliance
BigFix Compliance team
HCL BigFix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bigmail.bigfix.com/pipermail/besadmin-announcements/attachments/20260918/a43b5b68/attachment.html>