Black Duck

Black Duck Coverity 2026.9.0: Broader Sigma analysis for Kotlin, Groovy, and modern languages

Black Duck Coverity 2026.9.0 moves Kotlin analysis to Sigma autocapture, with existing Kotlin findings reopened as new issues and prior triage data lost. It also makes Groovy generally available, adds ECMAScript 2026 and TypeScript 7 support, expands compiler coverage, and includes cumulative Sigma checker content.

By Chris CarpenterBlack DuckCoverityAppSecSAST
blackduck-logoBlack Duck Coverity
Black Duck Coverity 2026.9.0: Broader Sigma analysis for Kotlin, Groovy, and modern languages cover graphic
Back to Black Duck release updates
Release facts
VendorBlack Duck
ProductBlack Duck Coverity Static
Version2026.9.0
Published by MeritoSeptember 23, 2026
Upgrade pathKotlin analysis now uses Sigma autocapture only; Kotlin build capture and quality checkers are removed. Existing Kotlin issues will close and reopen as new issues, and their triage data will be lost. Java 17 support is removed; Java 26, Oracle/OpenJDK 1.8, and .NET 8 are deprecated for future removal.
Vendor release notesBlack Duck Coverity Static 2026.9.0 release notes
Release historyBlack Duck Coverity Static release history

Kotlin analysis now runs through the bundled Rapid Scan Static (Sigma) engine using autocapture, changing how teams scan Kotlin projects and handle existing findings. Kotlin build capture and quality checkers are removed. Existing Kotlin issues will be closed and reopened as new issues, and their triage data will not carry over.

Supported versions

Coverity on Polaris now supports Coverity 2026.9.0 and recommends it, alongside 2026.6.0 and 2026.3.0. Coverity 2025.12.0 remains supported but is deprecated, while Coverity 2025.9.0 is no longer supported.

The Coverity on Polaris CLI Scan Client supports the same set of versions: 2026.9.0, 2026.6.0, 2026.3.0, and deprecated 2025.12.0. Pipeline owners can use this list to check which scan-client versions remain within supported coverage.

Kotlin analysis moves to Sigma

Teams can analyze Kotlin with Sigma autocapture. The migration replaces Kotlin build capture and quality checkers. For developers and AppSec engineers, the immediate operational effect is that prior Kotlin findings reappear as new issues after existing ones are closed; former triage decisions are lost.

Treat the first results after this change as a new Kotlin finding set when reviewing ownership, status, and remediation work.

Groovy analysis is generally available

Teams can now use generally available Groovy analysis through Sigma autocapture. The included checker content adds Groovy checks and extends Groovy coverage in areas including TLS, CORS, cookies, XML handling, deserialization, cryptographic settings, authentication, and HTTP client behavior.

This gives teams with Groovy application code or Gradle-related configuration another supported analysis path in Coverity on Polaris.

Modern language and compiler coverage

Coverity 2026.9.0 adds ECMAScript 2026 support through Sigma 2026.7.0 and day-zero TypeScript 7 support through Sigma 2026.8.0. It also supports cc21k v8.15.1.0, MPLAB XC32 V5.00 on Windows and Linux, MPLAB XC8 V3.10 on Windows and Linux, HighTec Tricore V9.1.0, GCC 16, and NonStop c89.

Teams can align supported scans with these language and compiler versions where those are used in their builds.

Java and runtime lifecycle changes

Java 17 is no longer supported. Java 26, Oracle/OpenJDK 1.8, and .NET 8 are deprecated as of Coverity 2026.9.0 and are planned for removal in a future release.

AppSec engineers and build owners should distinguish the removed Java 17 support from the three newly deprecated runtime versions when checking pipeline compatibility.

Cumulative Sigma checker content

Coverity on Polaris 2026.9.0 includes cumulative Sigma-derived checker content from Sigma 2026.5.0, 2026.6.0, 2026.6.1, 2026.7.0, and 2026.8.0. The additions and updates span C#, Java, Kotlin, Groovy, Go, Python, PHP, Swift, Dart, Ruby, Scala, JavaScript, JSON, Android, Ansible IaC, and markup checks.

The content covers patterns such as exposed or hardcoded secrets, insecure TLS and certificate handling, CORS and cookie configuration, injection risks, weak cryptography, unsafe deserialization, authentication issues, and insecure framework settings. It also includes Ansible IaC finding enhancements.

What this means for your team

Developers working in Kotlin should expect new issue records and re-triage them after the Sigma migration. Teams with Groovy, ECMAScript 2026, TypeScript 7, or newly supported compiler builds can include those codebases in their normal Coverity analysis flow. In an AI-driven SDLC, human reviewers and coding agents can work from the expanded language and checker coverage when fixing generated or manually written code. CISOs and audit managers should account for Kotlin's lost triage history when interpreting finding trends and evidence.

Based on the official Black Duck release notes.

How Merito helps

Merito can help teams adopt and govern changed Coverity analysis workflows, including Kotlin re-triage and pipeline configuration. See Merito's Black Duck page for related expertise.

Merito is an authorized Black Duck reseller and services partner. Our Black Duck Coverity team helps you adopt the 2026.9.0 changes, with implementation services to configure them for your environment and training and enablement to bring your teams up to speed.

About Black Duck Coverity Static

Black Duck Coverity Static licenses, renewals, upgrades and implementation are available through Merito, an authorized Black Duck reseller and services partner.

Frequently Asked Questions