Linux · 
Ubuntu · Package update · March 31, 2026
Ubuntu · Package update · March 31, 2026node-lodash 4.17.4+dfsg-1ubuntu0.1~esm1: node-lodash 4.17.4+dfsg-1ubuntu0.1~esm1 for Ubuntu 18.04.6 LTS (bionic)
node-lodash 4.17.4+dfsg-1ubuntu0.1~esm1, released March 31, 2026, fixes 6 CVEs in node-lodash. None of them is reported as exploited. Patch Radar priority: Urgent. The product is no longer supported.
UrgentUnsupported product
CVEs closed
6
1 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.2016
97th percentile
Priority of the 6 CVEs
Patch now 0
Urgent 1
High 1
Routine 4
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| node-lodash | Ubuntu 18.04.6 LTS (bionic) | 4.17.4+dfsg-1ubuntu0.1~esm1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2026-4800 | node-lodash: The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validati... | 9.8 | 0.0281 | None reported |
| High | CVE-2025-13465 | golang-github-prometheus-node_exporter: Bump lodash package to version 4.17.23 to fix prototype pollution vulnerability (bsc#1257329) | 8.8 | 0.0182 | None reported |
| Routine | CVE-2021-23337 | libjs-lodash: Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. | n/a | 0.2016 | None reported |
| Routine | CVE-2020-28500 | libjs-lodash: Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, tri... | n/a | 0.0742 | None reported |
| Routine | CVE-2020-8203 | libjs-lodash: Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. | n/a | 0.0521 | None reported |
| Routine | CVE-2026-2950 | cockpit: Impact: Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions | 6.5 | 0.0034 | None reported |
Showing 1 to 6 of 6
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.