Vulnerability in node-lodash (UBUNTU-CVE-2026-4800)
Summary
Vulnerability in node-lodash (UBUNTU-CVE-2026-4800). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1 or later.
Original description
The description as published by the source.
Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function(). Patches: Users should upgrade to version 4.18.0. Workarounds: Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2026-4800 has been found in node-lodash.
Successful exploitation can lead to full system takeover.
What to do: upgrade node-lodash to 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1 or later.
If unsure, ask your IT team or search "node-lodash UBUNTU-CVE-2026-4800" on the vendor's site.
UBUNTU-CVE-2026-4800 (node-lodash)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in node-lodash.
Check the vendor advisory for the affected versions of node-lodash.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'node-lodash' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'node-lodash' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
node-lodashを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade node-lodash to 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1ステージング環境で 4.17.21+dfsg+~cs8.31.198.20210220-9ubuntu0.25.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report cna.openjsf.org
- report github.com
- report github.com