The October 1, 2025, SAS Security Update for SAS^® 9.4M9 (TS1M9) contained misnamed .jar files. If you downloaded a SAS 9.4M9 Software Depot between October 1, 2025, and December 19, 2025, or installed the October 1, 2025, SAS Security Update for SAS^® 9.4M9 (TS1M9), complete the following instructions (based on your situation).

Scenario 1: You Downloaded the SAS Software Depot but Did NOT use It to Deploy SAS Software prior to December 19, 2025 

If you downloaded an affected SAS Software Depot but have not yet used it for deployment, update your SAS Software Depot to retrieve the latest hot fixes by completing the steps in the Hot Fixes and Your Deployment section of the SAS Guide to Software Updates and Product Changes.

Scenario 2: You Downloaded the Depot AND Used It to Deploy SAS Software

If you deployed SAS software using an affected SAS Software Depot, apply the latest SAS Security Updates and Hot Fixes for SAS 9.4M9 to the deployed environment and update your SAS Software Depot to retrieve the latest hot fixes by completing the steps in the Hot Fixes and Your Deployment section of the SAS Guide to Software Updates and Product Changes.

Scenario 3: You Installed the October 1, 2025, SAS Security Update for SAS^® 9.4M9 (TS1M9)

Download and install the latest SAS Security Update for SAS^® 9.4M9 (TS1M9) by completing the Applying SAS Security Updates and Hot Fixes - SAS 9.4M9 instructions.

A specific example of an issue caused by the misnamed .jar files is described in SAS KB0043974, "The Load Server Content step for SAS^® Visual Analytics Services fails during migration with "An error occurred while migrating the Blacklist Database"."