Manual remediation for compromised eMudhra certificates in SAS® 9.4


Severity: Critical

Description: On October 20, 2026, eight Intermediate CA Certificates issued by the eMudhra Certificate Authority were publicly disclosed as compromised. These certificates were generated without sufficient randomness to protect their associated private keys. An attacker might use a forged certificate to impersonate servers and intercept traffic.

Table of Contents

Overview

This article describes how to remediate the two issues impacting SAS 9.4 resulting from the compromised certificates:

Part 1: SAS Private Java Runtime Environment (JRE) Remediation

Applies to SAS® 9.4M8 (TS1M8) and SAS® 9.4M9 (TS1M9)

These releases deliver a SAS Private Java Runtime Environment (JRE) that is used to install SAS Software, execute Java clients, and run middle-tier applications. In addition to the default keystore, the SAS Private JRE includes trusted certificate authority (CA) certificates provided by Mozilla to authenticate TLS-certificate chains provided by servers.  

SAS 9.4M8 and SAS 9.4M9 do not deliver the compromised intermediate eMudhra certificates. However, you can use the following interim procedure to automatically block the use of the eight compromised intermediate certificates. 

1. Open the SAS Private JRE security directory: 

Note: Identify the SAS installation directory that is represented by <SASHome> in this guide. Replace the placeholder with the actual path for your installation.

Linux/UNIX: cd "<SASHome>/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/security"

Windows: cd "<SASHome>\SASPrivateJavaRuntimeEnvironment\9.4\jre\lib\security"

2. Back up the existing blocked.certs file:

Linux/UNIX: cp blocked.certs orig.blocked.certs

Windows: copy blocked.certs orig.blocked.certs

 

3. Download the replacement file for your platform:

Platform

Download

Linux x64, 64-bit-enabled AIX,
Solaris SPARC, or Solaris x64

emudhra-block-unix.certs

Windows 32-bit or Windows 64-bit

emudhra-block-windows.certs

 

4. Save the downloaded file in the SAS Private JRE security directory:

Linux/UNIX: <SASHome>/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/security

Windows: <SASHome>\SASPrivateJavaRuntimeEnvironment\9.4\jre\lib\security
 

5. Rename the downloaded file to “blocked.certs” and preserve proper file permissions:

Linux/UNIX: mv emudhra-block-unix.certs blocked.certs

              chmod 644 blocked.certs

Windows: rename emudhra-block-windows.certs blocked.certs

Result: The SAS Private JRE blocks the eight compromised eMudhra intermediate certificates. Valid root certificates remain available for other, uncompromised certification paths.

Part 2: Remove Compromised Root Certificates from SAS truststores

(Windows, Linux/UNIX, z/OS USS)

Purpose: The Certificate Remediation Script removes only self-signed root certificates whose SHA-256 fingerprints match the known compromised list. It does not remove unrelated user-installed leaf and intermediate certificates.

Important: The script does not remove affected certificates that you added. Use  SAS® Deployment Manager to remove those certificates and then add clean replacements. For instructions, see Manage Certificates in the Trusted CA Bundle Using the SAS Deployment Manager.

Before You Begin

Be aware of the following before you begin the remediation:

What the Script Does

The script checks and updates truststores under SASHome/SASSecurityCertificateFramework/1.1/cacerts/

SAS release

Truststore files

SAS 9.4M9

cacerts.p12, trustedcerts.p12, cacerts.pem, trustedcerts.pem

SAS 9.4M8 and earlier

cacerts.jks, trustedcerts.jks, cacerts.pem, trustedcerts.pem

Select the Package for Your Operating System

Each ZIP package contains the Groovy script and the wrapper for the selected platform. Extract both files into the same working directory.

Groovy script that is included in every package: remove_compromised_emudhra_roots.groovy

Linux/UNIX

ZIP file: remove_compromised_emudhra_roots_linux.zip

Wrapper (in the ZIP file): run_remove_compromised_emudhra_roots.sh

Windows

ZIP file: remove_compromised_emudhra_roots_windows.zip

Wrapper (in the ZIP file): run_remove_compromised_emudhra_roots.bat

z/OS Unix System Services (USS)

ZIP file: remove_compromised_emudhra_roots_zos.zip

Wrapper (in the ZIP file): run_remove_compromised_emudhra_roots_ebcdic_cp1047.rexx

Linux/UNIX Instructions

1. Ensure that the script is executable (chmod +x):

chmod +x run_remove_compromised_emudhra_roots.sh

2. Run the script in dry-run mode:

./run_remove_compromised_emudhra_roots.sh --sashome "<SASHome>" --dry-run --verbose

3. Review the MATCH and SCAN lines. They identify the certificates that match and would be removed. No changes are made in dry-run mode.

4. Run the script in apply mode:

./run_remove_compromised_emudhra_roots.sh --sashome "<SASHome>" --apply --verbose

If you are not running as root, the wrapper re-runs with sudo for apply mode.

Windows Instructions

1. Open Command Prompt or Windows PowerShell.

2. Run the wrapper in dry-run mode:

run_remove_compromised_emudhra_roots.bat --sashome "<SASHome>" --dry-run --verbose

3. Review the MATCH and SCAN lines. They identify the certificates that match and would be removed. No changes are made in dry-run mode.

4. Run the wrapper in apply mode:

run_remove_compromised_emudhra_roots.bat --sashome "<SASHome>" --apply --verbose

If the wrapper is run in apply mode without administrator privileges, the wrapper requests elevation automatically.

 

z/OS Unix System Services (USS) Instructions

1. Extract all files from the ZIP into the same USS directory. Before running the utility, select and verify the Java version using java -version. Use Java 8 with SAS 9.4M8 and Java 21 with SAS 9.4M9. 

2. Run the utility with the following: 

./run_remove_compromised_emudhra_roots_ebcdic_cp1047.rexx --sashome <SASHome> --verbose --apply

Note: The --apply option makes the certificate changes and requires root privileges. To perform a dry run without changing the certificate stores, leave off --apply:

./run_remove_compromised_emudhra_roots_ebcdic_cp1047.rexx --sashome <SASHome> --verbose



Review the Expected Output

Use the console output and generated files to confirm what the script found and changed. The script emits the following information during execution:

After the run, the following items are present:

Optional Parameters

Parameter

Use

--storepass <password>

Use when the PKCS12 truststore password is not the default.

--backup-dir <path>

Write backups to a location other than the default certificate directory.

--audit-dir <path>

Write audit artifacts to a controlled location, such as a centralized evidence share. Recommended for environments with formal retention and audit collection requirements.

--verbose

Display detailed discovery and execution diagnostics, including SASHome, the Groovy JAR path, and Java runtime selection.

--dry-run

List matching certificates without making changes.

--apply

Remove matching certificates and write the updated truststores.

 

Retain Audit Evidence

Retain artifacts according to local policy (for example, ticket/CR attachment or regulated retention window). If no removals occur, keep dry-run artifacts as proof of verification.

Minimum evidence set per execution:

Final Steps

1. Restart SAS Applications and Servers

After the manual changes to the SAS Private JRE and after running the Certificate Remediation Script, restart all SAS Applications and Servers.

2. Replace affected certificates that you previously added.
The script does not remove these certificates. Use SAS Deployment Manager to remove each affected certificate and then add a clean replacement. For instructions, see Manage Certificates in the Trusted CA Bundle Using the SAS Deployment Manager.

3. Retain the remediation records.
Keep the run output, audit artifacts, and backups according to your organization’s change-control and retention requirements.

Planned Hot Fixes

SAS plans to provide a hot fix for the SAS Private Java Runtime that will make the Part 1 manual procedure unnecessary. SAS also plans to provide a hot fix for the SAS Certificate Framework to remove the compromised root certificate. This article will be updated when those hot fixes are available.

Related SAS Documentation