-
Mend.io might modify this page retroactively from time to time.
-
To stay informed about hotfixes, modifications, and additions to Mend.io's products, check this page from time to time in between official releases or use our RSS Feed:
-
Mend CLI release notes are listed under the “Mend Developer Integrations Release Notes” page.
-
Access all release notes for Mend.io’s products.
Version 26.10.2 (15-November-2026)
Resolved Issues
-
Fixed an issue where Azure Container Registry (ACR) scans failed to identify and process selected images during scheduled or manual scans. The scanning logic was updated to ensure all specified tags are correctly recognized, even when sharing manifests with other tags. Additionally, the system now provides clearer logging for scans that result in no images and returns appropriate error codes when a manual scan is initiated without selecting a registry.
Version 26.10.1 (01-November-2026)
New Features and Updates
-
Mend Container now supports detecting and scanning vulnerabilities in standalone binaries within container images. This new Binary package type identifies software such as Node.js, Nginx, PHP, and more that were manually installed or built from source rather than through an OS package manager. The system provides comprehensive security analysis and reporting for these components, ensuring full visibility into source-built packages.
Version 26.9.3 (18-October-2026)
Resolved Issues
-
Fixed an issue where Container Image SBOM reports were downloaded with a `.txt` extension and a truncated filename, despite containing a valid ZIP archive. The reports now download with the correct `.zip` extension and a descriptive filename, ensuring they can be opened immediately without manual renaming.
Version 26.9.2 (04-October-2026)
New Features and Updates
-
The image scan size limit for Mend Container has been increased from 2GB to 4GB. This update allows for the successful pulling, extraction, and scanning of larger container images across all registry integrations, including ECR. Scans for images exceeding the new 4GB limit will now provide a clear error message. Additionally, scanner stability and timeouts have been optimized to accommodate the increased data volume, ensuring accurate reporting of vulnerabilities, licenses, and components in the platform UI.
Resolved Issues
-
Fixed an issue where the severity distribution in the `mend image` JSON report did not match the Platform UI for the same scan. This discrepancy, which caused some findings to be reported at a higher severity level in the JSON output, has been resolved to ensure consistency across all reporting interfaces.
Version 26.9.1 (27-September-2026)
Resolved Issues
-
Fixed an issue where certain vulnerabilities in RHEL8/Rocky8-based images were not correctly identified during filesystem scans. The scanner now properly surfaces OS-level CVEs even when no official fix is available from the distribution. Additionally, the matching logic has been enhanced to identify vulnerabilities in third-party and custom-rebuilt RPM packages by falling back to upstream ecosystem advisories when distribution-specific data is unavailable.
-
Fixed an issue where the CLI local JSON export picked the CVSS score source at random. The score now comes from NVD's own score, otherwise from a reviewed GitHub advisory (GHSA). For Red Hat-based images, the Red Hat score is used first. Distro data for Ubuntu, Debian and Alpine has no CVSS score. The severity label is the distro vendor's rating, so its band can differ from the CVSS score.
-
Fixed an issue where Container Image SBOM reports requested via the Reports API remained in a pending state for several hours. This delay was caused by an incorrect routing logic that skipped processing for cloud-native solution reports. The dispatch mechanism has been corrected to ensure that API-triggered report requests are promptly picked up and processed by the appropriate service, aligning the performance with UI-triggered requests.
-
Fixed an issue where the Containers Findings tab incorrectly displayed a "No Findings were found" message despite the Project and Scan Summary pages reporting existing container findings. This fix ensures that the findings list accurately reflects the summary counts.
-
Fixed an issue where specific vulnerabilities in Chainguard and Wolfi images were not correctly identified. This fix ensures accurate detection of Python packages on Wolfi base layouts and improves the matching logic for OpenSSL subpackages in Chainguard advisories.
-
Fixed an issue where container scans failed to report CVE-2026-18963 for keycloak-services versions in the 26.4.x and 26.6.x branches. The vulnerability data synchronization for container scanning was updated to correctly ingest and match Maven package ranges across all affected backport branches, ensuring critical vulnerabilities are accurately identified in container images.
-
Fixed an issue where the Containers view displayed outdated scan data because the latest scan pointer failed to advance upon scan completion. The logic has been corrected to ensure the Containers view consistently reflects the most recently finished scan.
-
Fixed an issue where `mend image --tar` failed to scan container image tarballs exported in pure OCI format. The scanner previously required a Docker-specific `manifest.json` file, which is not present in spec-compliant OCI image layouts. The CLI now correctly handles OCI-layout archives, including `index.json` and OCI-compliant blob structures, ensuring successful SBOM generation and vulnerability scanning for OCI-format exports.
-
Fixed an issue where updating a registry integration could overwrite stored service-user credentials with invalid data, causing subsequent scheduled scans to fail. The fix ensures that service-user state is managed server-side and includes a recovery mechanism to automatically refresh credentials if authentication failures occur during a scan.
Version 26.8.2 (06-September-2026)
Resolved Issues
-
Fixed an issue where the Container Attribution Report export endpoint returned an empty report regardless of the number of scanned container images. The export now correctly includes attribution data for the organization's container scans.
-
Fixed an issue where container scans incorrectly matched CVEs to package versions outside their affected range and reported inconsistent vulnerability counts for unchanged images. The fix ensures that vulnerability matching strictly adheres to documented version ranges and provides stable, reliable results across consecutive scans.
-
Fixed an issue where Docker Hardened Image (DHI) VEX statements were not correctly attached to Go-language application package findings. While VEX data was successfully applied to OS-level packages, it was missing for language-specific dependencies. This fix ensures that version-matched VEX statements are accurately reflected as risk factors for Go packages, providing a more precise security posture for container scans.
Version 26.8.1 (23-August-2026)
New Features and Updates
-
Chainguard is now supported as part of Mend Container’s hardened image detection, enhancing container security by incorporating Chainguard-specific vulnerability data and VEX information. This update includes the detection of Chainguard image layers and base images. Users can now view Chainguard VEX status and branding directly within the risk factors columns across the UI, providing clearer insights into the security posture of Chainguard-based images and findings.
Version 26.7.2 (09-August-2026)
New Features and Updates
-
Mend Container now supports SBOM import, allowing you to ingest container inventory and risk data from CycloneDX and SPDX files to create a new project. This new capability, available via the Platform UI and platform API, enables teams to manage security for air-gapped builds or third-party images by identifying OS-level packages and language ecosystems. Imported projects are automatically matched against the Mend vulnerability database to ensure accurate risk assessment without requiring a live image scan.
Resolved Issues
-
Fixed an issue where large image scans would occasionally fail to complete within a reasonable timeframe. This update optimizes the scanning process for high-capacity images, ensuring consistent performance and reliable completion of security assessments.
Version 26.6.2 (12-July-2026)
New Features and Updates
-
Introducing an Echo integration for managing hardened images in the Mend Platform. The integration allows users to connect their Echo environments to the Mend Platform, facilitating automated security scanning and centralized management of container image vulnerabilities, including VEX data and dedicated risk factor chips in the UI.
-
Minor improvements to the Malicious Package management user experience.
Version 26.6.1 (28-June-2026)
New Features and Updates
-
Malicious package detection capabilities have been extended to container images, providing the same end-to-end protection and workflows currently available for SCA. This update enables users to detect, assess, and respond to malicious packages embedded within container layers, ensuring consistent security coverage and visibility across all deployment artifacts.
-
Updated the Containers Findings Search tab to align with the Dependencies findings search design, providing a consistent and streamlined user interface across the platform.
Resolved Issues
-
Fixed an issue where project exclusions defined in workflow scope conditions were not being honored during container image scans. This resulted in policy violations being incorrectly generated for projects that should have been excluded from evaluation. The fix ensures that excluded projects are correctly identified and bypassed, preventing unnecessary violations and streamlining scan results.
Version 26.5.2 (14-June-2026)
Resolved Issues
-
Fixed an issue where workflow violations were incorrectly triggered for suppressed findings during CLI image scans. Suppressed vulnerabilities are now properly excluded from workflow evaluation, ensuring that automated policies and CLI exit codes accurately reflect the project's security status.
-
Fixed an issue where the total number of container findings in the Project Summary did not match the totals shown in the Security > Containers > Findings page, ensuring consistent and accurate reporting across views.
Version 26.4.2 (03-May-2026)
Resolved Issues
-
Fixed an issue where the
bsonpackage version was incorrectly detected as UNKNOWN, resulting in a false positive for CVE-2020-7610. The scanner now accurately identifies bson@1.1.4 and avoids reporting this vulnerability when the correct version is present.
Version 26.3.2 (12-April-2026)
Resolved Issues
-
Fixed an issue where Azure Container Registry (ACR) integrations would intermittently fail with 401 Unauthorized errors after successful credential validation and initial scans, preventing subsequent scans from running as expected.
Version 26.3.1 (22-March-2026)
New Features and Updates
-
Introduced a new risk factor based on Docker VEX data, highlighting when vulnerabilities are not applicable to Docker packages, with improved visibility and filtering in the Containers view.
-
Added support for Docker Hardened Images (DHI), including a clear badge and filtering options for DHI packages.
-
Added a “Suppression Comment” column to the CSV export of suppressed container findings.
Resolved Issues
-
Fixed an issue where the java-17-amazon-corretto-headless package was falsely flagged with multiple CVEs, caused by identical software versions being incorrectly flagged as different.
-
Fixed an issue where the total findings count in the summary page did not match the findings listed under Containers > Findings, ensuring consistent and accurate reporting across both views.
-
Fixed an issue where the "Total Findings by Severity" widget in the Security Dashboard displayed inconsistent numbers compared to the detailed application view after findings were suppressed. The dashboard now accurately reflects the correct number of findings for each severity level.
-
Improved CVE detection for RPM packages.
-
Fixed an issue where CycloneDX SBOMs generated from container image scans did not include license information for certain NuGet components. Now, all detected NuGet dependencies will have their license data properly reflected in the SBOM when available.
Version 26.2.2 (08-March-2026)
Resolved Issues
-
Fixed an issue where registry URLs were not being validated correctly, leading to errors during ECR integration.
Version 26.1.2 (08-February-2026)
New Features and Updates
-
Kubernetes system namespaces can now be included in the scan using a dedicated toggle in the configuration of your Kubernetes integration in the Mend AppSec Platform UI.
-
Added support for updating credentials for existing Registry and Kubernetes integrations.
-
Optimized the scanner to clean up image files during the scan process, significantly reducing storage usage and improving resource efficiency.
Version 25.12.2 (11-January-2026)
Resolved Issues
-
Fixed an issue where an old version of Oracle Linux package qemu-guest-agent was specified as a remediation suggestion. The version comparison logic has been updated to ensure only newer package versions are recommended for remediation.
-
Fixed an issue where scanning the official Grafana Docker image incorrectly identified the component version, resulting in false-positive vulnerability reports. The scan now accurately detects the correct Grafana version and matches CVEs accordingly.
Version 25.12.1 (28-December-2025)
New Features and Updates
-
A new Kubernetes Integration is available for Google Kubernetes Engine (GKE).
Resolved Issues
-
Fixed an issue where some vulnerabilities in Container scans displayed an incorrect detection date of "01/01/2000" and were not included in the summary page count. Now, all vulnerabilities show accurate detection dates and are properly counted.
Version 25.11.2 (14-December-2025)
New Features and Updates
-
Mend Container registry integration now supports Google Artifact Registry (GAR).
Resolved Issues
-
Fixed an issue where long package names in the Container package name column were not fully visible, allowing users to view the entire package name without limitation.
-
Fixed an issue where the findings count displayed in the scans section and project overview did not always match the actual number of findings, ensuring accurate and consistent vulnerability counts across all views.