v0.72.0

[github-actions[bot]]

📑 Table of Contents

• ⚠️ Breaking changes ⚡
  • APT repository publishes .deb packages only to the generic distribution
  • Container images no longer publish architecture-specific tags
• 🚀 What's new? 🚀
  • Vulnerability detection for Bottlerocket OS
  • Detect bundled runtime in self-contained .NET deployments
  • License detection for JAR packages
  • GitHub App token rule updated for new stateless token format
  • New secret-scanning rules for OpenAI API keys
  • CloudFront check now supports v2 logging
• 🏎️ Performance 🏎️
• 👷‍♂️ Notable Fixes 🛠️

⚠️ Breaking changes ⚡

APT repository publishes .deb packages only to the generic distribution

Starting with v0.72.0, the official Trivy APT repository publishes new releases only to the generic distribution. Per-codename distributions (jammy, noble, bookworm, focal, …) are no longer updated.
If your /etc/apt/sources.list.d/trivy.list points at a specific codename, switch it to generic to keep receiving updates — nothing breaks immediately, but such setups stay frozen at v0.71.2.

See #10819 for details.

Container images no longer publish architecture-specific tags

Starting with v0.72.0, Trivy container images no longer publish architecture-specific tags (e.g. 0.71.0-amd64, latest-arm64) across docker.io/aquasec/trivy, ghcr.io/aquasecurity/trivy, and public.ecr.aws/aquasecurity/trivy. The release pipeline now builds and pushes the multi-arch manifest list directly via docker buildx, without separate per-arch tags.

If you use the plain tag (e.g. aquasec/trivy:0.71.0), nothing changes. If you pin a suffixed tag, switch to the plain tag, or pull by digest via docker buildx imagetools inspect - nothing breaks immediately, but suffixed tags stay frozen at v0.71.0.

See #10824 for details.

🚀 What's new? 🚀

Vulnerability detection for Bottlerocket OS

Trivy can now detect vulnerabilities in Bottlerocket OS.
It matches the installed package versions from the Bottlerocket software inventory against the Bottlerocket security advisories

➜  trivy --scanners vuln bottlerocket-1.34.0

2026-06-26T16:09:28+02:00	INFO	[vuln] Vulnerability scanning is enabled
2026-06-26T16:09:28+02:00	INFO	Detected OS	family="bottlerocket" version="1.34.0"
2026-06-26T16:09:28+02:00	INFO	[bottlerocket] Detecting vulnerabilities...	pkg_num=147
2026-06-26T16:09:28+02:00	INFO	Number of language-specific files	num=0

Report Summary

┌───────────────────────────────────────────┬──────────────┬─────────────────┐
│                  Target                   │     Type     │ Vulnerabilities │
├───────────────────────────────────────────┼──────────────┼─────────────────┤
│ bottlerocket-1.34.0 (bottlerocket 1.34.0) │ bottlerocket │       135       │
└───────────────────────────────────────────┴──────────────┴─────────────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)
...

Thanks to @0intro

Detect bundled runtime in self-contained .NET deployments

Trivy now detects the .NET runtime bundled into self-contained deployments (dotnet publish --self-contained).
Previously the runtime packed into the app's own *.deps.json (a runtimepack library) was dropped, so vulnerabilities in Microsoft.NETCore.App / Microsoft.AspNetCore.App were never matched.
Self-contained apps are now consistent with framework-dependent apps — their runtime is reported (e.g. Microsoft.NETCore.App.Runtime.linux-x64) and runtime CVEs are detected.

Thanks to @jetersen

License detection for JAR packages

Trivy now detects licenses for JAR packages from two sources, in this order:

• Embedded POM — the <licenses> block of the embedded META-INF/maven/<groupId>/<artifactId>/pom.xml. Works for thin, uber/shaded and nested (war, Spring Boot) jars.
• License files — LICENSE, LICENCE or COPYRIGHT files (including variants like LICENSE.txt) at the JAR root or under META-INF/.

Coverage is limited: many JARs declare a license only in a parent POM (not expanded in the embedded pom.xml) or ship no Maven descriptor at all.

GitHub App token rule updated for new stateless token format

GitHub is rolling out a new stateless format for ghs_ GitHub App installation tokens, replacing the old fixed-length ghs_<36 chars> token with a longer one that embeds a JWT (ghs_<APPID>_<JWT>) (see https://github.blog/changelog/2026-04-24-notice-about-upcoming-new-format-for-github-app-installation-tokens/).

The github-app-token secret-scanning rule now detects both the old and the new token format.

New secret-scanning rules for OpenAI API keys

Trivy now detects OpenAI API keys via new built-in secret-scanning rules:

Rule	Severity	Format
OpenAI Project API Key	CRITICAL	sk-proj-...
OpenAI Service Account Key	CRITICAL	sk-svcacct-...
OpenAI Admin API Key	CRITICAL	sk-admin-...
OpenAI Legacy User API Key	HIGH	sk-...
OpenAI Service API Key	HIGH	sk-service-<name>-...
OpenAI Realtime Client Secret	MEDIUM	ek_<32 hex>

CloudFront check now supports v2 logging

The CloudFront access logging check AWS-0010 now also recognizes standard logging v2 (CloudWatch vended logs delivery), in addition to the existing legacy (v1) logging support.

Thanks to @Aakarsh133

🏎️ Performance 🏎️

👷‍♂️ Notable Fixes 🛠️

• fix: correct format verbs in diagnostic messages #10805 Thanks to @eran132
• Non-deterministic OS package deduplication for images with embedded SBOMs #10778
• fix(image): lookup origin layer for custom resources in merged layers #10788 Thanks to @nimitjohri
• fix(server): propagate package repository class in client/server mode #10874
• bug(spdx): panic on Marshal when BOM has no root component #10764 Thanks to @sapirbaruch
• fix: use random suffix for process temp directory instead of PID #10431 Thanks to @dcoppa
• fix(nodejs): parse project dependencies from multi-document pnpm-lock.yaml #10861
• fix(misconf): support github_repository_vulnerability_alerts resource #10680
• fix(terraform): avoid data race on global getter.Getters in remote module resolver #10843 Thanks to @arpitjain099