| Version | 5.12.0 |
|---|---|
| Release date | 19 Dec 2025 |
| Scope | Focused on new functionalities, enhancements and bug fixes |
Before upgrading MetaDefender ICAP Server to v5.10.0 or newer from v5.6.0 or earlier, make sure you review the Release Notes and the following Documentation:
New Features, Improvements and Enhancements
| Details | |
|---|---|
| Expanding processing history details | View a complete chronological timeline of each file's journey through the processing pipeline, including precise start and end times for every stage. Quickly identify bottlenecks and optimize performance by visualizing where files spend the most time, enabling faster troubleshooting and process optimization.
|
| Security Hardening for Block Page Content | Strengthen security with an option to disallow scripts and unsafe HTML tags in custom block pages.
To toggle the option, use the configuration flag global/blockpage_allow_script_or_unsafe_html_tag (refer to Configuration file) |
| Support for CIS Level 1 and 2 for Windows | MetaDefender ICAP Server now aligns with CIS Level 1 and Level 2 benchmarks for Windows Server 2022. This enhancement supports organizations that require stricter security controls. Refer to CIS Level 1 & 2 Guidelines - Windows |
| Security Enhancements | Upgraded third-party libraries for improved security:
Applied additional security hardening measures across the product to prevent vulnerabilities and strengthen overall protection. |
| Usability Improvements |
|
Bug Fixes
| Details | |
|---|---|
| Random crash issue on Linux | Resolved a rare crash issue on Linux environments that could occur when polling and webhook callbacks were combined. |
| Minor Fixes | Resolved various UI cosmetic issues and minor fixes |
Known Limitations
| Details | |
|---|---|
| Proxy Configuration | Currently, HTTPS proxy configuration is not supported. |
| SAML Directory (SSO Integration) Limitations | In v5.5.0, users cannot create a new SAML directory via the web UI.
|
| Stability Issues on Red Hat/CentOS (Kernel Version 372) | MetaDefender ICAP Server v5.1.0 or newer may encounter stability issues on Red Hat/CentOS systems running kernel version 372. Solution: Upgrade to kernel version 425, where Red Hat has resolved this issue. |
| MetaDefender ICAP Server's NGINX Web Server Fails to Start with Weak Cipher Suites for HTTPS | From v5.1.0, OpenSSL 1.x has been replaced with OpenSSL 3.x — across the product and its dependencies — to enhance security and address vulnerabilities. As part of this upgrade, NGINX's OpenSSL 3.x in MetaDefender ICAP Server now enforces stricter cipher policies and rejects all weak cipher suites. The web server now only accepts "HIGH" encryption cipher suites https://www.openssl.org/docs/man1.1.1/man1/ciphers.html (MD5 and SHA1 hashing based are also not accepted). As a result, if you have already configured MetaDefender ICAP Server for HTTPS using a weak SSL cipher with your certificate, the server will not start due to the enforced security policies in NGINX's OpenSSL 3.x. |
| no_proxy Configuration | Starting with MetaDefender ICAP Server v5.1.0, the no_proxy setting must support CIDR for IP addresses.
For more details, see No Proxy configuration. |
| TLS Connectivity to MetaDefender Core on Debian | On Debian OS, MetaDefender ICAP Server v5.1.0 requires the two following commands to enable TLS communication with MetaDefender Core:
Resolution: Upgrade to MetaDefender ICAP Server v5.1.1, where the issue is resolved. |
| TLS 1.3 Not Supported on Windows Server 2012 | TLS 1.3 is not supported on Windows Server 2012 due to limitations with Schannel SSP. Reference |







