ci: auto-suppress unfixed CVEs, trim trivyignore to exporter Go CVEs - #41
Merged
Merged
Conversation
The Trivy scan started failing as new 2026 CVEs landed in the vuln DB for packages that have no fix in Debian 12 (perl, ncurses, libssh2, libcurl, plus the existing zlib/openldap). - add 'ignore-unfixed: true' to the gating Trivy step so CVEs with no upstream fix no longer break CI; the SARIF step keeps full visibility in the Security tab - drop zlib/openldap/glibc entries from .trivyignore (now covered by ignore-unfixed) and the two Go CVEs that no longer fire (CVE-2025-61728, CVE-2025-61730) - .trivyignore now lists only the criteo/ocserv-exporter Go stdlib CVEs, which DO have an upstream fix but ship in the pre-built v0.2.2 binary (Go 1.25.4); tracked for a source rebuild in #39 Verified locally: trivy --ignore-unfixed with the new .trivyignore reports 0 HIGH/CRITICAL on the built 1.5.0 image.
This was referenced Jun 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Restores a green Trivy scan after the vuln DB picked up new 2026 CVEs in Debian-12 packages that have no upstream fix. (Re-created from #40, which auto-closed when its stacked base
feat/ocserv-1.5.0merged.)Changes
ignore-unfixed: trueon the gating Trivy step — CVEs with no fix in Debian 12 (perl, ncurses, libssh2, libcurl, zlib, openldap, …) no longer break CI. The SARIF step keeps reporting everything for the Security tab..trivyignoretrimmed to only the criteo/ocserv-exporter Go stdlib CVEs. These have an upstream fix (newer Go) but ship in the pre-built v0.2.2 binary (Go 1.25.4), soignore-unfixeddoes not cover them.ignore-unfixed) and two stale Go CVEs that no longer fire (CVE-2025-61728, CVE-2025-61730).Why not Debian 13 (trixie)
Measured:
trixie-slim(13.5, latest stable) still carries the 2 perl CRITICALs + ncurses CVE (allfix_deferredupstream) and adds 2 sqlite CVEs. No net benefit, plus migration risk. Staying on bookworm.Tracking
Exporter Go CVEs tracked for a from-source rebuild in #39.
Verified locally
trivy --ignore-unfixedwith the new.trivyignore→ 0 HIGH/CRITICAL on the built 1.5.0 image (debian 0, gobinary 0).