3.56.2+2026.07.09

Hero Features

Risk score
- Every finding now carries a single risk score that folds exploitation, impact, decision, and finding-type signals into one number, so you can work the list from most to least urgent instead of weighing CVSS, EPSS, KEV, and reachability by hand.
- The global and image findings grids order by risk score by default. Switch between three profiles, Balanced, Exploitability, and Actionable Risk (the default), to match a baseline review, threat hunting, or remediation planning.
- Learn more in Prioritizing with the Risk Score and Binarly Risk Score.
Code and Environment Reachability
- Two reachability columns replace the legacy Reachable column. Code Reachability shows whether the vulnerable code is reachable inside its binary; Environment Reachability shows whether the component runs or loads in the deployed environment. Read together, they scope the grid to the findings that actually execute.
- Reachability also appears on each finding’s details page, with the components the reachability comes from. Filter and combine both columns to build a reachable-findings triage view. See Filtering findings by reachability and Reachability analysis (ASAP).

Code Reachability in the findings grid API: The findings grid API now returns Code Reachability, so you can query and filter findings by reachability programmatically.

Vulnerability Database Service
- Added Alpine as a vulnerability advisory data source.

Dashboard charts: Fixed a cross-site scripting (XSS) vulnerability in the dashboard’s charting library.
Findings report download: Fixed an error that caused findings report downloads to fail when a risk filter was applied.
Aggregation refreshes: A server restart could leave a product’s aggregation refresh stranded, so aggregated finding data stayed stale. These operations are now reclaimed and reprocessed.

Git repository scans: Scans of images containing corrupted or invalid git repositories no longer fail with processing exceptions.