> ## 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.47.1+2026.06.02

> Binarly v3.47.1 release notes: secret validity filtering GA, Mitigate detection for Insyde FDM misconfigurations, more finding identifier types, and Python analysis fixes.

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

* **Secret validity status**
  * Secrets now carry a validity status (valid, invalid, undetermined, or unspecified) that can be used to filter findings. The unspecified status applies to findings that are not secrets. The validity status replaces the previous "Secret | Validated" finding type.
  * The finding scope and type filters no longer include the legacy leaked-secret type.
  * Existing saved filters that referenced the old secret types are automatically migrated to the new secret type and validity combination.

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

* **Finding display names**: Findings now use the first identifier regardless of type when generating the display name. Previously, display names were derived only from BRLY or CVE identifiers, causing incorrect or inflated names for findings with other identifier types.

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

* **New Context-Aware Rule Detection (Mitigate)**
  * Added detection for Insyde FDM misconfigurations that could allow firmware flash modification. The check identifies unprotected secondary FDM regions and unprotected FvCnvUnCompact sections in Insyde-based UEFI firmware (CWE-354, CVSS 7.6).

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

### Findings

* **Insyde FDM checker findings**: Insyde FDM misconfiguration findings now display EFI region addresses in hexadecimal. The finding detail view correctly distinguishes the three region types (the misconfigured FDM entry, the FDM store region, and the targeted region), which were previously displayed as a flattened list.

### Analysis Engine

* **Non-deterministic Python package components**: Python package components extracted from firmware are now consistent across scans. Previously, the same firmware image could produce different component sets on separate scans.
* **Python package construction for generic inputs**: Fixed construction of Python package components for firmware unpacked via unblob with generic inputs.
* **CryptoScan: Python packages in tar archives**: Fixed extraction of Python package components packed in tar archives.
* **CryptoScan: Python package format compatibility**: Updated CryptoScan to process the revised python.package component format produced by the firmware normalizer.