chore(deps): bump cel-go to v0.29.2 for GHSA-gcjh-h69q-9w9g - #756
Merged
Conversation
cel-go >=0.22.0,<=0.28.1 lets ext.NativeTypes(ParseStructTag("json")) expose
struct fields marked json:"-" via dyn(obj)["-"]. Fixed in 0.29.0.
Not exploitable here — cel-go/ext is linked in (via
buf.build/go/protovalidate/cel) but neither protovalidate nor openfga calls
NativeTypes or ParseStructTag, and neither does our code. Bumped anyway: the
fix is a version change and leaving a flagged advisory in the tree costs more
than it saves.
Note govulncheck does NOT cover this advisory yet — its only finding is the
pre-existing, unfixed GO-2026-5932 (x/crypto/openpgp). Its silence was not
evidence of safety here; reachability was checked by hand.
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.
Clears GHSA-gcjh-h69q-9w9g (CVSS 6.3), which affects
cel-go>=0.22.0,<=0.28.1. We were on0.28.1, pulled in transitively byopenfga v1.18.1. First patched version is0.29.0; this takesv0.29.2.The advisory
ext.NativeTypes(ParseStructTag("json"))does not honour JSON's skip directive. A field taggedjson:"-"gets registered in CEL's type system under the literal name"-"and becomes readable viadyn(obj)["-"]— so anyone who can submit a CEL expression can read fields the developer deliberately kept out of serialised output.Assessed as not exploitable here — but bumped anyway
The vulnerable package is linked into the binary:
github.com/google/cel-go/extappears in our build graph, imported bybuf.build/go/protovalidate/cel(v1.2.0).But the vulnerable function is never invoked:
NativeTypes/ParseStructTag?buf.build/go/protovalidateopenfga v1.18.1Exploitation also requires attacker-controlled CEL expressions. In this codebase CEL reaches two places — protovalidate evaluating compiled-in
buf.validateconstraints, and OpenFGA conditions from an authorization model, which only a super-admin can write.Bumped regardless: the fix is a version change, and leaving a flagged advisory in the tree costs more than it saves.
Worth recording, because it is the kind of thing that gets misread as an all-clear.
govulncheckreports 0 affected, and its single "modules you require" finding isGO-2026-5932(x/crypto/openpgp, unrelated, andFixed in: N/A) — not this cel-go issue. GHSA-gcjh-h69q-9w9g is not in the Go vulnerability database yet, so a clean govulncheck run was never evidence about it either way. The reachability analysis above was done by hand.Verified
go build ./.../go vet ./...make testinternal/authorization/...(OpenFGA, the main CEL consumer)make smoke(GraphQL + REST + gRPC + MCP)make lintcel-go v0.29.2Smoke was run deliberately rather than skipped: protovalidate evaluates
buf.validateconstraints through CEL on every gRPC request, so this bump sits on a live request path, not just in the build graph.