> ## Documentation Index
> Fetch the complete documentation index at: https://docs.binarly.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 3.113.0+2026.10.06

> Binarly v3.113.0 release notes: CPE and PURL on finding details, VulHunt detection for CVE-2026-18922 and CVE-2026-56132, ML-KEM and ML-DSA in CryptoScan.

## <Icon icon="hand" size={32} /> Features

* **CPE and PURL on the finding details page**: The dependency card on the finding details page now shows the dependency's CPE and PURL, the same identifiers the dependencies grid already displays.

## <Icon icon="rocket" size={32} /> Binarly Analysis Engine

* **New Context-Aware Rule Detection (VulHunt)**
  * Added VulHunt detection for CVE-2026-18922 in 389 Directory Server.
  * Added VulHunt detection for CVE-2026-56132 in libexpat.
* **Analysis Framework Enhancements**
  * CryptoScan detection quality was improved for AES, Camellia, DES, XTEA, MD5 and SHA algorithms.
  * CryptoScan now detects implementations of the CAST5 cipher.
  * CryptoScan now detects implementations of BLAKE, MD2, MD4 and RIPEMD-160 hashes, and more SHA-512 variants.
  * CryptoScan now detects implementations of ML-KEM key encapsulation.
  * CryptoScan now detects implementations of the Poly1305 MAC.
  * CryptoScan now detects implementations of the ML-DSA, SLH-DSA, Ed25519 and LMS signature schemes. LMS detection previously covered Dell firmware only and is now generic.
  * The analysis tools use an updated binary analysis core with performance improvements.

## <Icon icon="bug" size={32} /> Bug Fixes

### Scans

* **Scan completion on large images**: At the end of a scan, the platform loaded all component and property records of a file into memory before writing them, so scan completion could run out of memory on large images with many partitions. Records are now streamed and written in batches, which lowers peak memory use.

### Reports

* **Key establishment recommendations in the compliance report**: Fixed the recommendations given for non-compliant key establishment in the compliance report.

### Vulnerability data

* **PySec synchronization**: PySec advisories stopped synchronizing after the source began publishing CWE data with them. The source synchronizes again.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.