Sage Alerting Systems has released Rev96-2 (96-02), a mandatory firmware update for U.S. Digital ENDEC model 3644 units already running Rev96 or Rev96-1. The free release removes compromised eMudhra root certificates from the trust store used to validate TLS connections, including servers that provide audio referenced by emergency alerts. Sage says the appliance does not update automatically, so operators must download and install the firmware themselves.
The certificate problem extends beyond broadcast equipment. Sage says weak private keys appeared within the eMudhra certificate hierarchy, creating a path for forged certificates that could impersonate arbitrary domains under affected trust chains. The practical risk for an alert encoder is not a change to the alert protocol itself, but misplaced trust during HTTPS retrieval. Removing the affected roots prevents those chains from remaining valid on the ENDEC after other operating systems and browsers have already updated their trust stores.
Rev96-2 also fixes SMTP attachment compatibility with some mail servers and allows ampersand and plus characters in web-interface passwords. The release carries forward changes from Rev96-1, including the Missing and Endangered Persons event code, configurable week starts for conformance reports, Broadcast Tools MSRP-3 control over TCP/IP, NTP improvements and a refreshed CA bundle. The update therefore touches both security and routine station operations around logging, timing and automation control.
The FCC's 2026 EAS security rule requires participants to install manufacturer security patches promptly, while allowing testing that begins promptly and finishes within an industry-consistent period. Sage has not published the exact removed certificate list, a CVE mapping for the appliance, installation downtime, rollback behaviour or results from interoperability testing with alert-audio servers. Stations should therefore verify backups, alert reception, audio retrieval, logs and automation interfaces in their own environment rather than treating firmware installation alone as proof of readiness.