Title
Create new category
Edit page index title
Edit category
Edit link
Release notes
| Version | 2.6.0 |
|---|---|
| Release date | 15 April 2026 |
| Scope | This release focuses on centralized engine configuration, simpler MetaDefender Worker installation, and MetaDefender Aether integration. Enhanced audit log search and filtering, plus file size filtering for processing history. Configurable engine and MetaDefender Core instance requirements, redesigned distributed extraction with built-in compression, and performance and security improvements throughout. |
New Features, Improvements and Enhancements
Centralized engine configuration for MetaDefender Core
System administrators can now manage engine settings for all MD Core instances from a single location. They can enable, disable, or remove engines centrally, and any changes are automatically synchronized across all instances.

Simplified MetaDefender Worker installation
MetaDefender Cluster Worker is now bundled with MetaDefender Cluster Control Center. Users can install MetaDefender Cluster Worker through a single script available in Control Center.

Configurable minimum engine and MD Core instance requirements
Allow users to configure the minimum number of active MetaDefender Core, active AV engines, and required engines. This gives administrators more control over system readiness.

Redesigned distributed extraction flow
The distributed extraction flow has been redesigned to make better use of system resources while improving overall product stability.
Distributed compression
Distributed compression is now supported in MetaDefender Cluster, allowing archive files to be generated across multiple MetaDefender Core instances.
Further Enhancements
1. Faster MetaDefender Cluster File Storage
The new MetaDefender Cluster File Storage improves file upload and download speeds between the system and clients, resulting in better overall performance.
2. Faster executive report retrieval
Executive reports are now fetched more quickly.
3. Custom installation directory support
Users can now choose custom installation directories for instances deployed by MetaDefender Cluster Worker, including MetaDefender Core, MetaDefender Cluster API Gateway, and MetaDefender Callback Service.

4. Display of Total Extracted File Size
MetaDefender Cluster Control Center now displays the total size of the extracted file.

5. Display of stop reason
MetaDefender Cluster Control Center now displays the reason why the scanning of an archive file is stopped.

6. Improved audit log search and filtering
Users can now quickly find specific audit log details and filter results using multiple criteria such as destination, action taken, date, time, and more.

7. File size filter for Processing History
Processing history can now be filtered by file size, making it easier to narrow down relevant records.

8. MetaDefender Aether integration
MetaDefender Cluster now includes integration with MetaDefender Aether.

Security Enhancements
Upgraded library for vulnerability fixes:
- Nginx 1.29.7
- 7zip 26.0.0
- OpenSSL 3.5.6
- Sqlite 3.51.2
- PostgreSQL 14.22
- zlib 1.3.2
- Nghttp2 1.68.1
- tikio-rs/bytes 1.11.1
- quinn-proto 0.11.14
- webpki 0.103.10
Address a high-severity SQL injection vulnerability in the Control Center search functionality. The fix ensures that all search inputs are properly validated and handled using secure query mechanisms to prevent injection attacks.
Fix a Denial-of-Service (DoS) vulnerability affecting endpoints that support resource listing and allow clients to specify the number of resources to be returned in a single request.
Bug Fixes
- Fix an issue where some fields were missing in the JSON response of
GET /file/{batch_id}when the request was returned through MetaDefender Cluster API Gateway. - Fix a potential MetaDefender Cluster Worker crash that could occur when DEBUG logging is enabled.
- Fix an issue that prevented Proactive DLP engine from being deployed on Windows due to the long file path limitation.
Known Limitations
- MD Cluster Control Center does not detect duplicate workers when one is added using its IP address and another using its hostname (or vice versa). Registering the same worker multiple times may lead to incorrect license usage calculations.