Lucent Sky AVM version 2509 release notes

2025/09/26 |

Lucent Sky AVM version 2509 releases

Lucent Sky AVM version 2509 MR

New features in 2509 MR

Weakness policies

  • Support for CWE 4.18
  • Improved mappings PCI DSS 4.0.1

Pre-analysis and build

  • General improvements in the ECMAScript and Swift parsers

Binary analysis

  • General improvements in the Java binary analysis engine

Source code analysis

  • General improvements in the C/C++, ECMAScript, Go, PHP, and Python source code analysis engines
  • Expanded support for Bicep, SQL, Terraform files
  • Improved analysis for minified ECMAScript files
  • Improved Intelligent Analysis algorithms and performance

Dependency analysis

  • Improved dependency identification and correlation algorithms
  • Improved license observation algorithms
  • Performance improvements on the dependency analysis engine

Remediation

  • General improvements in ML-augmented vulnerability remediation and explanations

Reporting

  • Secure score

    Secure score aggregates security findings from a scan into a single score to help developers and stakeholders assess the security posture of an application at a glance. The higher the score, the lower the application's identified risk level is.

    The algorithms take into account over 200 signals generated during the scan to calculate the secure score, including the risk identified vulnerabilities and the ease of remediation, the exploitability and reachability of vulnerable software components, and the general context of the application.

  • The CVSS score of a vulnerable dependency now includes the original CVSS base score of the vulnerability along with the calculated CVSS base score for the vulnerable dependency in the context of the application.

Interfaces

  • User experience enhancements in the Web UI

    • Streamlined navigation between different context, such as navigating from the vulnerability list of a scan to the dependency list of a scan.
    • The application list and scan list have been resigned application to improve information density.
    • The Efficiency Hub has been updated to show secure score trends.

  • The Dependency API is now generally available with additional enhancements

    • Additional context is available when viewing the details of a dependency on the Web UI, such as applications referencing the dependency, files where the dependency were discovered, vulnerabilities resulted from the dependency, and the observed licenses of the dependency.
    • Performance improvements for the Dependency interfaces of the API and the CLI.

  • The File API is now generally available with support for additional file types

    The File API supports retrieving the content of a specific file of a scan. On the Web UI, the File API enables viewing files related to a specific vulnerability or dependency, as well as highlighting relevant lines.

  • Support for recent versions of Eclipse IDE, InteliJ IDEA, and Visual Studio Code

Issues fixed in 2509 MR

  • We fixed a bug where the scan may fail when the source code archive contains certain license files
  • We fixed a bug where a file was parsed using an alternative parser
  • We fixed a bug where syntax highlighting on the Web UI is always set to dark mode
  • We fixed a bug where scan tags are not visible on the scan index page

Breaking changes in 2509 MR

  • The Project interface of the API

    Breaking change. The Clone method has been deprecated and removed. Developers should switch to the Duplicate method, which has the same parameters and return type but performs additional checks when duplicating an application.

  • The Scan Details API model

    Potentially breaking change. In 2506 MR and earlier, the AnalysisEngines field in the Scan Details API model returns the analysis engines that were configured to execute during a scan. In 2509 MR, it returns the analysis engines that were actually executed during a scan. As a result, when accessing scans created by an agent running versions earlier than 2509 MR, this field returns an empty list.

  • Preview configuration

    Potentially breaking change for on-premise instances. In 2506 MR and earlier, preview features are enabled by configuring the Preview CLEAR Engine setting. In 2509 MR, it is enabled by including the preview flag in the FeatureFlags CLEAR Engine setting.