chore: add three published CVEs to openvex.json - #9787
Open
matthewmcneely wants to merge 1 commit into
Open
Conversation
This comment has been minimized.
This comment has been minimized.
All three are published advisories whose fixes are already on main, so nightly builds (Go pseudo-versions that sort below the fixed release tags) trip Trivy false positives without a VEX statement. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
matthewmcneely
force-pushed
the
matthewmcneely/openvex-published-cves
branch
from
July 27, 2026 17:47
2481128 to
d370fca
Compare
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
Adds VEX statements for the three published advisories that were missing from
openvex.json. All three fixes are already on main, but nightly builds embed a Go pseudo-version (v25.0.0-YYYYMMDDHHMMSS-<commit>) that sorts below the fixed release tags, so Trivy flags them as false positives without a statement.Changes
Also bumps the document
versionto 2 and refreshes the timestamp.Deliberately excluded: CVE-2023-31135 only affects the pre-
/v25module path below v23.0.0, so it can't match current builds.Side note for whoever owns the advisories: GHSA-33p8-wc97-5qcj records the affected package as
github.com/dgraph-io/dgraphwithout the/v25suffix and has no patched version, which is why version comparison can't clear it. Worth fixing on the GitHub side.🤖 Generated with Claude Code