fix(deps): update dependency devalue to v5.6.3 [security]#263
Merged
renovate[bot] merged 1 commit intotrunkfrom Feb 21, 2026
Merged
fix(deps): update dependency devalue to v5.6.3 [security]#263renovate[bot] merged 1 commit intotrunkfrom
renovate[bot] merged 1 commit intotrunkfrom
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
f3db710 to
1806327
Compare
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.
This PR contains the following updates:
5.6.2→5.6.3GitHub Vulnerability Alerts
GHSA-33hq-fvwr-56pm
Under certain circumstances, serializing sparse arrays using
unevalorstringifycould cause CPU and/or memory exhaustion. When this occurs on the server, it results in a DoS. This is extremely difficult to take advantage of in practice, as an attacker would have to manage to create a sparse array on the server — which is impossible in every mainstream wire format — and then that sparse array would have to be run throughunevalorstringify.GHSA-8qm3-746x-r74r
Under certain circumstances,
unevaling untrusted data can produce output code that will create objects with polluted prototypes when laterevaled, meaning the output data can be a different shape from the input data.Release Notes
sveltejs/devalue (devalue)
v5.6.3Compare Source
Patch Changes
0f04d4d: fix: Properly handle__proto__819f1ac: fix: better encoding for sparse arraysConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.