chore(deps): update dependency lodash to v4.18.1 [security]#388
chore(deps): update dependency lodash to v4.18.1 [security]#388renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📦 Next.js Bundle Analysis for next-enterpriseThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
716f1d6 to
2a469a9
Compare
📦 Next.js Bundle Analysis for next-enterpriseThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
1 similar comment
📦 Next.js Bundle Analysis for next-enterpriseThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
2a469a9 to
56b1839
Compare
📦 Next.js Bundle Analysis for next-enterpriseThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
56b1839 to
6b67c56
Compare
📦 Next.js Bundle Analysis for next-enterpriseThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
6b67c56 to
f4d6dac
Compare
📦 Next.js Bundle Analysis for next-enterpriseThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This PR contains the following updates:
4.17.23→4.18.1lodash vulnerable to Prototype Pollution via array path bypass in
_.unsetand_.omitCVE-2026-2950 / GHSA-f23m-r3pf-42rh
More information
Details
Impact
Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the
_.unsetand_.omitfunctions. The fix for CVE-2025-13465 only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such asObject.prototype,Number.prototype, andString.prototype.The issue permits deletion of prototype properties but does not allow overwriting their original behavior.
Patches
This issue is patched in 4.18.0.
Workarounds
None. Upgrade to the patched version.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
lodash vulnerable to Code Injection via
_.templateimports key namesCVE-2026-4800 / GHSA-r5fr-rjxr-66jc
More information
Details
Impact
The fix for CVE-2021-23337 added validation for the
variableoption in_.templatebut did not apply the same validation tooptions.importskey names. Both paths flow into the sameFunction()constructor sink.When an application passes untrusted input as
options.importskey names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time.Additionally,
_.templateusesassignInWithto merge imports, which enumerates inherited properties viafor..in. IfObject.prototypehas been polluted by any other vector, the polluted keys are copied into the imports object and passed toFunction().Patches
Users should upgrade to version 4.18.0.
The fix applies two changes:
importsKeysagainst the existingreForbiddenIdentifierCharsregex (same check already used for thevariableoption)assignInWithwithassignWithwhen merging imports, so only own properties are enumeratedWorkarounds
Do not pass untrusted input as key names in
options.imports. Only use developer-controlled, static key names.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 OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
lodash/lodash (lodash)
v4.18.1Compare Source
v4.18.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.