[GHSA-q63x-9pfm-mjx4] Feast before 0.63.0 contains an unsafe deserialization... - #9191
Open
PercevalFox wants to merge 1 commit into
Open
Conversation
github-actions
Bot
changed the base branch from
main
to
PercevalFox/advisory-improvement-9191
August 23, 2026 01:59
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.
Updates
Comments
This advisory is unreviewed and has no package mapping, so it does not surface to users of the affected package.
The repository feast-dev/feast publishes the PyPI package
feast.The advisory describes the registry server deserializing the user_defined_function.body field of an OnDemandFeatureView via dill.loads() before any authorization check. The fix commit (835cda8e) adds a skip_udf parameter to the from_proto methods and passes skip_udf=True from sdk/python/feast/registry_server.py for FeatureView, OnDemandFeatureView and StreamFeatureView, so the registry server no longer deserializes caller-supplied UDFs. The commit message is generic ("Fix issue with apply feature view") but the diff is unambiguous on this point.
I verified the boundary against the published PyPI wheels:
This matches the "before 0.63.0" wording in the description and the release tag already listed in the references (https://github.com/feast-dev/feast/releases/tag/v0.63.0).
Proposed range: introduced 0, fixed 0.63.0.
The CVSS v4 vector was rewritten to omit the trailing Not Defined (X) metrics, which the form's validator rejects. Semantically identical per the CVSS v4.0 specification, no change to the severity assessment. CVSS v3 left untouched.
The advisory also had no title. The proposed one follows the database's naming convention and reflects the existing CWE-502 classification.