Release notes
| Version | 2.4.0 |
|---|---|
| Release date | 30 September 2025 |
| Scope | Support /readyz API endpoint, export scan result in JSON format, export processing history in STIX or CSV format, support grouping and removing abandoned engine packages, fix eventual crashes of services |
New Features, Improvements and Enhancements
Export scan result in JSON format
From MetaDefender Distributed Cluster (MDDC) Control Center, users can export scan result in JSON format.
Export processing history in STIX or CSV format
Processing history can be exported in STIX or CSV format from MDDC Control Center.
Remove abandoned module packages
Abandoned module packages can be selected and removed on web console of Control Center.
Customize the system health check
System administrators can enable the health check option and set the minimum number of required MetaDefender Core instances in the Health Check settings of the MDDC Control Center.
RESTful API
- Introduce a new API endpoint in MetaDefender Distributed Cluster API Gateway to verity if the system is ready for new scan requests
GET /readyz. - Introduce a new field,
dlp_wait_time, in the response ofGET /file/{data_id}API requested from MetaDefender Distributed Cluster API Gateway. - Include
usernamefield in the response ofGET /file/{data_id},GET /file/batch/{batch_id}andGET /hash/{md5|sha1|sha256|sha512}.
Further Enhancements
- Verify the minimum version requirement when adding a new instance of Redis, RabbitMQ, and PostgreSQL to MetaDefender Distributed Cluster Control Center.
- Improve storing scan results from AV engines to MetaDefender Distributed Cluster Data Lake.
Security Enhancements
Upgraded library for vulnerability fixes:
- OpenSSL 3.5.2
Bug Fixes
- Fixed the issue that caused occasional service crashes when halted.
- Fixed the issue that made it impossible to close a batch if its name contained special characters.
- Fixed the issue that led to the batch name not appearing in the UI of MDDC Control Center.
- Fixed the issue that caused the COO engine to fail or time out during installation.
- Fixed the issue that caused the executive report to eventually miss data.
Known Limitations
| Details | |
|---|---|
| MetaDefender Core becomes unlicensed following the MDDC Worker upgrade | This issue will be resolved in MDDC version 2.5.0. In version 2.4.0, MetaDefender Core instance that has already deployed and activated successfully with a valid license becomes unlicensed after its MDDC Worker is upgraded. Workaround:
|
