Extend CVE-2025-59250 trivyignore expiration#492
Merged
Conversation
The previous expiration (2026-02-20) has passed, causing the Docker vulnerability scan to fail on the liquibase-secure image. The CVE is still a false positive — Microsoft's mssql-jdbc JAR reports version 13.2.1 in pom.properties but the actual Maven artifact is 13.2.1.jre11 which contains the fix. Updated comments to reflect the current mssql-jdbc version (13.2.1.jre11) and Liquibase Secure 5.1.0. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jnewton03
deleted the
bugfix/extend-trivyignore-cve-2025-59250-expiration
branch
3 tasks
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.
Summary
.trivyignoreexpiration for CVE-2025-59250 from2026-02-20to2026-08-2013.2.1.jre11) and Liquibase Secure 5.1.0liquibase-secureimage (run #22316556674)Context
The previous expiration date (
2026-02-20) passed on Feb 20, causing the Trivy scan to start flagging CVE-2025-59250 again. This is a false positive — Microsoft's mssql-jdbc JAR reports version13.2.1in its internalpom.properties, but the actual Maven artifact is13.2.1.jre11which contains the fix. Trivy compares13.2.1 < 13.2.1.jre11and incorrectly flags it as vulnerable.References:
Test plan
Scan liquibase/liquibase-secure / vulnerability-scanpasses🤖 Generated with Claude Code