fix(deps): update dependency serialize-javascript to v7 [security]#138
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency serialize-javascript to v7 [security]#138renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
5b3ca77 to
c7dd0eb
Compare
c7dd0eb to
b7ef530
Compare
b7ef530 to
b8a29a2
Compare
b8a29a2 to
a18bdc1
Compare
964eeff to
385d640
Compare
There was a problem hiding this comment.
Review verdict
APPROVE — dependency-only security update; adversarial review skipped per policy.
This PR contains only a serialize-javascript version bump (security fix). No source files, tests, contracts, or generated artifacts are modified. The code-review orchestrator is configured to skip dependency-only updates immediately.
Sent by Cursor Automation: Flatbread PR Review
385d640 to
9ac80db
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:
^6.0.2→^7.0.0Serialize JavaScript is Vulnerable to RCE via RegExp.flags and Date.prototype.toISOString()
GHSA-5c6j-r48x-rmvq
More information
Details
Impact
The serialize-javascript npm package (versions <= 7.0.2) contains a code injection vulnerability. It is an incomplete fix for CVE-2020-7660.
While
RegExp.sourceis sanitized,RegExp.flagsis interpolated directly into the generated output without escaping. A similar issue exists inDate.prototype.toISOString().If an attacker can control the input object passed to
serialize(), they can inject malicious JavaScript via the flags property of a RegExp object. When the serialized string is later evaluated (viaeval,new Function, or<script>tags), the injected code executes.Patches
The fix has been published in version 7.0.3. https://github.com/yahoo/serialize-javascript/releases/tag/v7.0.3
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Serialize JavaScript has CPU Exhaustion Denial of Service via crafted array-like objects
CVE-2026-34043 / GHSA-qj8w-gfj5-8c6v
More information
Details
Impact
What kind of vulnerability is it?
It is a Denial of Service (DoS) vulnerability caused by CPU exhaustion. When serializing a specially crafted "array-like" object (an object that inherits from
Array.prototypebut has a very largelengthproperty), the process enters an intensive loop that consumes 100% CPU and hangs indefinitely.Who is impacted?
Applications that use
serialize-javascriptto serialize untrusted or user-controlled objects are at risk. While direct exploitation is difficult, it becomes a high-priority threat if the application is also vulnerable to Prototype Pollution or handles untrusted data via YAML Deserialization, as these could be used to inject the malicious object.Patches
Has the problem been patched?
Yes, the issue has been patched by replacing
instanceof Arraychecks withArray.isArray()and usingObject.keys()for sparse array detection.What versions should users upgrade to?
Users should upgrade to
v7.0.5or later.Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
There is no direct code-level workaround within the library itself. However, users can mitigate the risk by:
serialize()function.v7.0.5as soon as possible.Acknowledgements
Serialize JavaScript thanks Tomer Aberbach (@TomerAberbach) for discovering and privately disclosing this issue.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
yahoo/serialize-javascript (serialize-javascript)
v7.0.5Compare Source
Fixes
For more details, please see GHSA-qj8w-gfj5-8c6v.
v7.0.4Compare Source
What's Changed
Full Changelog: yahoo/serialize-javascript@v7.0.3...v7.0.4
v7.0.3Compare Source
2e609d042b7cdbv7.0.2Compare Source
What's Changed
Full Changelog: yahoo/serialize-javascript@v7.0.1...v7.0.2
v7.0.1Compare Source
What's Changed
New Contributors
Full Changelog: yahoo/serialize-javascript@v7.0.0...v7.0.1
v7.0.0Compare Source
Breaking Changes
What's Changed
New Contributors
Full Changelog: yahoo/serialize-javascript@v6.0.2...v7.0.0
Configuration
📅 Schedule: (UTC)
🚦 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.