Release Notes
v2.5.2
Search this version
Release Notes
Release Notes
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Release notes
Copy Markdown
Open in ChatGPT
Open in Claude
| Version | 2.5.2 |
|---|---|
| Release date | 26 January 2026 |
| Scope | This release focuses on improving overall product performance, ensuring consistent processing results across MD Core instances, supporting a new engine package, enhancing compatibility with modern networks, and adding new response fields. It also addresses security vulnerabilities and resolves issues related to licensing. |
New Features, Improvements and Enhancements
RESTful API
- Added support for the
current_finished_filesfield in the responses ofGET /batch/{batch_id}andGET /file/{batch_id}.
Further Enhancements
- Optimized data lake queries to speed up retrieval of processing history records.
- Prevented multi-platform MD Core deployment to ensure consistent processing results.
- Added IPv6 support for essential MD Cluster services to improve modern network compatibility.
- Enabled fetching and installing OPSWAT Predictive Alin AI packages on MD Core for automated engine setup.
Security Enhancements
- Upgraded Nginx to 1.29.4 for vulnerability fixes.
- Addressed a security vulnerability that could permit unauthenticated remote code execution within MD Cluster Control Center and API Gateway.
- Addressed a vulnerability in user management operations that could allow SQL injection and potentially cause Denial of Service.
Bug Fixes
- Corrected inaccurate display of outdated scan engines in System Health.
- Resolved a problem that allowed selection of the License Management Service Activation rule even when using an invalid token.
- Fixed an issue where an MD Core instance’s active license could become permanently inactive after switching to a different license.
- Corrected a problem that allowed system admins to deactivate an online license that had already expired.
Known Limitations
- The DLP engine fails to install on MD Core instances that are deployed as part of MD Cluster. This issue will be resolved in the next MD Cluster release (2.6.0).
- 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.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
Next to read:
Archived release notesDiscard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message
