Aqua Security shipped Trivy v0.76.0 on 2026-10-14. Trivy is widely used in Terraform pipelines as a misconfiguration scanner (trivy config) alongside its container and dependency scanning capabilities. This article covers what the release notes actually state, how to upgrade, and how to confirm the new version works correctly against your Terraform code.
The published release notes for v0.76.0 are unusually thin: they point to a GitHub Discussion thread marked "Highlights" and to the CHANGELOG.md entry for 0.76.0, but no concrete feature names, flags, or PR/issue numbers are included in the notes provided here.
Because this article only reports details that are explicitly present in the supplied release notes, no specific new checks, new flags, deprecations, or breaking changes can be listed for Terraform scanning in this write-up. If you rely on Trivy for IaC scanning in CI, check the linked CHANGELOG and discussion directly before assuming behavior is unchanged, since policy/check updates (new or removed Terraform misconfiguration rules, rego policy changes) are common in Trivy point releases even when the GitHub release body is sparse.
Recommended next step: open the release page and the CHANGELOG link above and skim for any config/terraform scoped entries before rolling this out broadly in CI/CD.
There is no Terraform provider or module version constraint to change here since Trivy itself is not a Terraform provider; the upgrade is purely at the tool/binary/image level.
Confirm the installed version and run a quick scan against a Terraform directory to confirm misconfiguration checks still execute:
trivy --version# Should report Version: 0.76.0trivy config ./terraform/ --severity HIGH,CRITICAL
Compare the number and IDs of findings against your previous Trivy version's output on the same codebase (keep a baseline report with trivy config ./terraform/ -f json -o before.json prior to upgrading) to catch any silent rule additions or removals that aren't called out in the release notes.
v0.76.0 is available now, but the release notes shared here don't list concrete Terraform-relevant changes, flags, or fixes. Treat this as a routine version bump: pin the new version in CI, re-run scans against a known Terraform codebase, and diff the results against your previous baseline before trusting it in production pipelines. For authoritative details, consult the linked CHANGELOG and discussion thread directly.