Repository navigation
Conversation
github-actions
Bot
changed the base branch from
main
to
nazeeh111/advisory-improvement-10489
October 22, 2026 05:46
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.
The Go entry for CVE-2026-94603 currently uses
github.com/containers/podmanfor versions>=4.4.0, <5.8.8. The affected releases declare versioned module paths instead, so the record does not match those module identities.Replace that entry with:
github.com/containers/podman/v4>=4.4.0opsbadger.dev/containers/podman/v5<5.8.85.8.8The module declarations are explicit in the tagged
v4.4.0/go.mod,v5.0.0/go.mod, andv5.8.8/go.mod. The maintainer advisory identifies the feature's introduction in v4.4.0 and the fixed v5.8.8 release. The tagged v4 run implementation also contains the checkpoint-image restore dispatch.introduced: "0"for the v5 module includes its versions before the fixed release, including prereleases; it does not claim that the module existed before its first version. There is no invented v4 fixed release. The existinggo.podman.io/podman/v6entry and all narrative, references, severity and attribution remain unchanged.Validation: original and proposed records pass the OSV schema; 19 exact-module/range cases cover the v4 introduction, v5 fix and prereleases, unchanged v6 behavior, and unrelated modules. The original misses the actual v4/v5 module keys in the tested examples; the proposal matches them. Preservation and patch-reconstruction checks pass. These are metadata/SemVer checks, not a
govulncheckintegration run or container exploit reproduction.This corrects dependency matching for an already public vulnerability. No discovery, product-code fix, score change or advisory credit is claimed. Research and preparation were assisted by Codex.