[system] Prevent prototype pollution in cssVarsParser#48822
Open
Janpot wants to merge 5 commits into
Open
Conversation
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
Janpot
marked this pull request as ready for review
July 20, 2026 16:45
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
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.
assignNestedKeyswalked and wrote through key paths without guarding__proto__/constructor/prototype, so a theme containing such a nested key (e.g. one parsed from untrusted JSON) could write ontoObject.prototype. Added the same key blocklist already used byfastDeepAssign(#48580).Blast radius is very small in practice: the theme passed to
createTheme/extendTheme/cssVarsParseris developer-authored config and essentially never comes from user input — this is defensive hardening on the exportedunstable_cssVarsParsersurface.