# node-lodash security updates

Patch Radar has 15 security fixes for node-lodash, closing 6 CVEs. The newest security fix is DEBIAN-CVE-2026-4800 (4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1), released March 31, 2026.

- Web page: https://patchblox.com/security/product/linux/node-lodash
- Platform: Linux
- Supported: yes

## Security fixes, newest first

| Fix | Released | Fixed in | Priority | CVEs | Exploited |
|---|---|---|---|---:|---:|
| [DEBIAN-CVE-2026-4800](https://patchblox.com/security/data/fix/linux/debian-cve-2026-4800.md) | Mar 31, 2026 | Debian 12.15 (bookworm) 4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1 | Urgent | 1 | 0 |
| [DEBIAN-CVE-2026-4800](https://patchblox.com/security/data/fix/linux/debian-cve-2026-4800.md) | Mar 31, 2026 | Debian 14 4.18.1+dfsg-1 | Urgent | 1 | 0 |
| [DEBIAN-CVE-2026-4800](https://patchblox.com/security/data/fix/linux/debian-cve-2026-4800.md) | Mar 31, 2026 | Debian 13.5 (trixie) 4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1 | Urgent | 1 | 0 |
| [DEBIAN-CVE-2026-2950](https://patchblox.com/security/data/fix/linux/debian-cve-2026-2950.md) | Mar 31, 2026 | Debian 13.5 (trixie) 4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1 | Routine | 1 | 0 |
| [DEBIAN-CVE-2026-2950](https://patchblox.com/security/data/fix/linux/debian-cve-2026-2950.md) | Mar 31, 2026 | Debian 14 4.18.1+dfsg-1 | Routine | 1 | 0 |
| [DEBIAN-CVE-2026-2950](https://patchblox.com/security/data/fix/linux/debian-cve-2026-2950.md) | Mar 31, 2026 | Debian 12.15 (bookworm) 4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1 | Routine | 1 | 0 |
| [node-lodash 4.17.15+dfsg-2ubuntu0.1~esm1](https://patchblox.com/security/data/fix/linux/ubuntu-focal-node-lodash-4.17.15-dfsg-2ubuntu0.1-esm1.md) | Mar 31, 2026 | Ubuntu 20.04 LTS (focal) 4.17.15+dfsg-2ubuntu0.1~esm1 | Urgent | 6 | 0 |
| [node-lodash 4.17.4+dfsg-1ubuntu0.1~esm1](https://patchblox.com/security/data/fix/linux/ubuntu-bionic-node-lodash-4.17.4-dfsg-1ubuntu0.1-esm1.md) | Mar 31, 2026 | Ubuntu 18.04.6 LTS (bionic) 4.17.4+dfsg-1ubuntu0.1~esm1 | Urgent | 6 | 0 |
| [node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-5ubuntu0.1~esm1](https://patchblox.com/security/data/fix/linux/ubuntu-jammy-node-lodash-4.17.21-dfsg-cs8.31.198.20210220-5ubuntu0.1-esm1.md) | Mar 31, 2026 | Ubuntu 22.04.1 LTS (jammy) 4.17.21+dfsg+~cs8.31.198.20210220-5ubuntu0.1~esm1 | Urgent | 3 | 0 |
| [node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.24.04.1~esm1](https://patchblox.com/security/data/fix/linux/ubuntu-noble-node-lodash-4.17.21-dfsg-cs8.31.198.20210220-9ubuntu0.24.04.1-esm1.md) | Mar 31, 2026 | Ubuntu 24.04.5 LTS (noble) 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.24.04.1~esm1 | Urgent | 3 | 0 |
| [node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1](https://patchblox.com/security/data/fix/linux/ubuntu-questing-node-lodash-4.17.21-dfsg-cs8.31.198.20210220-9ubuntu0.25.10.1.md) | Mar 31, 2026 | Ubuntu 25.10 (questing) 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1 | Urgent | 3 | 0 |
| [node-lodash 4.17.23+dfsg-1ubuntu0.1~esm1](https://patchblox.com/security/data/fix/linux/ubuntu-resolute-node-lodash-4.17.23-dfsg-1ubuntu0.1-esm1.md) | Mar 31, 2026 | Ubuntu 26.04.1 LTS (resolute) 4.17.23+dfsg-1ubuntu0.1~esm1 | Urgent | 2 | 0 |
| [DEBIAN-CVE-2025-13465](https://patchblox.com/security/data/fix/linux/debian-cve-2025-13465.md) | Jan 21, 2026 | Debian 12.15 (bookworm) 4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1 | High | 1 | 0 |
| [DEBIAN-CVE-2025-13465](https://patchblox.com/security/data/fix/linux/debian-cve-2025-13465.md) | Jan 21, 2026 | Debian 13.5 (trixie) 4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1 | High | 1 | 0 |
| [DEBIAN-CVE-2025-13465](https://patchblox.com/security/data/fix/linux/debian-cve-2025-13465.md) | Jan 21, 2026 | Debian 14 4.17.21+dfsg+~cs8.31.198.20210220-10 | High | 1 | 0 |

---

Data as of 2026-11-07T12:40:37Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

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.