Conversation
github-actions
Bot
changed the base branch from
main
to
khamon/advisory-improvement-10090
October 1, 2026 20:08
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 affected range and patched version of this advisory do not match the maintainers' advisory or the code.
What this changes
fixed:0.29.0to0.30.0last_known_affected_version_range:<= 0.28.1to<= 0.29.2Why
The repository advisory published by cel-expr/cel-go for this GHSA lists the vulnerable range as v0.22.0 through v0.29.2 and the patched version as v0.30.0:
GHSA-gcjh-h69q-9w9g
The Go vulnerability database entry for the same advisory, GO-2026-6094, also gives 0.30.0 as the fixed version:
https://pkg.go.dev/vuln/GO-2026-6094
The code agrees.
ext/native.gois byte-identical at v0.28.0, v0.28.1, v0.29.0 and v0.29.2 (git blobc30f26ad3122). The fix, theisSkippedFieldNamecheck that skips fields taggedjson:"-", first appears at v0.30.0 (blobd9f5fab0decc).As the entry stands, a project that upgrades to 0.29.x has its Dependabot alert closed while the vulnerable code is still present.