STAC-25173 Add Jackson databind package VEX lookup#24
Open
LouisLotter wants to merge 1 commit into
Open
Conversation
viliakov
approved these changes
Jul 2, 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
2 participants
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
com.fasterxml.jackson.core:jackson-databind@2.22.0to the existing Jackson databind OpenVEX statement.index.jsonso Trivy can discover the statement by package PURL.Why
Trivy VEX repository lookup is package-PURL based. The existing image-scoped OCI entries document the product context, but Trivy does not use those entries when evaluating the Maven package finding. Maven Central still lists
2.22.0as the newest releasedjackson-databind2.x artifact as of 2026-07-01, while the advisory fixed lines include versions that are not currently resolvable.This keeps the VEX scoped by repository policy and statement text to SUSE Observability chart/image scans, while making the lookup shape usable by Trivy.
Companion S3Proxy image fix: https://github.com/StackVista/docker-images/pull/173
Jira: https://stackstate.atlassian.net/browse/STAC-25173
Validation
python3 tools/build_index.py --check3.2.0-so3with this VEX file:0active medium-or-higher findings