| Version | 2.7.0 |
|---|---|
| Release date | 30 June 2026 |
| Scope | MetaDefender Cluster v2.7.0 introduces Active Directory (AD) and LDAP authentication, integration with OPSWAT AI Content Inspector, and simplified service configuration through Ignition and YAML files. This release also improves usability with additional filtering and certificate management features, strengthens platform security through API hardening and dependency upgrades, extends the REST API, and includes multiple stability and reliability fixes across MD Core services and distributed processing. |
New Features, Improvements and Enhancements
Active Directory (AD) and LDAP Authentication
MD Cluster 2.7.0 now supports user authentication through Active Directory (AD) and LDAP. Users authenticated via AD/LDAP can also generate and manage their own API keys.
Service Connection Configuration via Ignition File
MD Cluster 2.7.0 allows service connections to be configured through the Ignition file during MD Cluster Control Center installation, simplifying automated deployments and initial setup.
OPSWAT AI Content Inspector Integration
MD Cluster 2.7.0 introduces integration with OPSWAT AI Content Inspector, enabling AI-powered content analysis as part of the MD Cluster workflow.
Further Enhancements
1. Service Connection Import via YAML
MD Cluster 2.7.0 allows administrators to import service connection settings by uploading a YAML file, simplifying service configuration and updates.
2. Processing History Filtering by File Extension
MD Cluster 2.7.0 adds the ability to filter processing history by file extension, making it easier to locate specific files.
3. Certificate Renaming
MD Cluster 2.7.0 allows users to rename both existing certificates and newly submitted certificates.
4. Heartbeat Support for All Services
MD Cluster 2.7.0 extends heartbeat monitoring to all services, improving service health monitoring and availability.
Security Enhancements
- Introduced a more secure API key format. API keys are now 36 hexadecimal characters (
0-9,a-f), containing at least 10 letters, at least 10 digits, and no more than three consecutive characters of the same type. - Fixed a potential denial-of-service issue caused by unlimited worker addition.
- Restricted local file paths when reading certificates to improve security.
- Fixed potential SQL injection vulnerabilities.
- Restricted callback destinations to help prevent unauthorized callback requests.
- Upgraded NGINX to v1.30.3.
- Upgraded OpenSSL to v3.5.7.
RESTful API
- Added support for API endpoints to retrieve blocked leaves:
GET /file/{data_id}/blocked-leavesAPI andGET /hash/{md5|sha1|sha256|sha512}/blocked-leavesAPI. - The
POST /fileAPI API endpoint now accepts only requests with theapplication/octet-streamcontent type.
Bug Fixes
- Fixed an issue where a deployed MD Core could fail to start after being forcefully stopped or when its master Nginx process was terminated.
- Fixed an issue that could cause distributed archive extraction to hang when processing certain archive files.
- Fixed an issue where MD Cluster Control Center and Identity Service could fail to start if the PostgreSQL password contained special characters.
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.