chore(patch): update devalue to 5.6.4 #patch

[public-glueops-renovatebot]

This PR contains the following updates:

Package	Change	Age	Confidence
devalue	5.6.2 → 5.6.4

---

devalue unevaled code can create objects with polluted prototypes when evaled

GHSA-8qm3-746x-r74r

More information

Details

Under certain circumstances, unevaling untrusted data can produce output code that will create objects with polluted prototypes when later evaled, meaning the output data can be a different shape from the input data.

Severity

• CVSS Score: 2.1 / 10 (Low)
• Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

References

• https://github.com/sveltejs/devalue/security/advisories/GHSA-8qm3-746x-r74r
• https://github.com/sveltejs/devalue/commit/0f04d4d678eac39ad5d7a07d1956275d7874e81c
• https://github.com/sveltejs/devalue/releases/tag/v5.6.3
• https://github.com/advisories/GHSA-8qm3-746x-r74r

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

devalue has prototype pollution in devalue.parse and devalue.unflatten

CVE-2026-30226 / GHSA-cfw5-2vxh-hr84

More information

Details

In devalue v5.6.3, devalue.parse and devalue.unflatten were susceptible to prototype pollution via maliciously crafted payloads. Successful exploitation could lead to Denial of Service (DoS) or type confusion.

Severity

• CVSS Score: 6.3 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/sveltejs/devalue/security/advisories/GHSA-cfw5-2vxh-hr84
• https://nvd.nist.gov/vuln/detail/CVE-2026-30226
• https://github.com/advisories/GHSA-cfw5-2vxh-hr84

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Sveltejs devalue's devalue.parse and devalue.unflatten emit objects with __proto__ own properties

GHSA-mwv9-gp5h-frr4

More information

Details

In some circumstances, devalue.parse and devalue.unflatten could emit objects with __proto__ own properties. This in and of itself is not a security vulnerability (and is possible with, for example, JSON.parse as well), but it can result in prototype injection if downstream code handles it incorrectly:

const result = devalue.parse(/* input creating an object with a __proto__ property */);
const target = {};
Object.assign(target, result); // target's prototype is now polluted

Severity

• CVSS Score: 2.7 / 10 (Low)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

References

• https://github.com/sveltejs/devalue/security/advisories/GHSA-mwv9-gp5h-frr4
• https://github.com/sveltejs/devalue/releases/tag/v5.6.4
• https://github.com/advisories/GHSA-mwv9-gp5h-frr4

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

sveltejs/devalue (devalue)

v5.6.4

Compare Source

Patch Changes

• 87c1f3c: fix: reject __proto__ keys in malformed Object wrapper payloads

  This validates the "Object" parse path and throws when the wrapped value has an own __proto__ key.

• 40f1db1: fix: ensure sparse array indices are integers

• 87c1f3c: fix: disallow __proto__ keys in null-prototype object parsing

  This disallows __proto__ keys in the "null" parse path so null-prototype object hydration cannot carry that key through parse/unflatten.

v5.6.3

Compare Source

Patch Changes

• 0f04d4d: fix: Properly handle __proto__
• 819f1ac: fix: better encoding for sparse arrays

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[public-glueops-renovatebot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.