CVE-2026-4800

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.8%, top 15% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.6%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
2.6%
EPSS %ILE
85th
KEV
Not listed

Published

March 31, 2026

Last Modified

September 14, 2026

Advisory Details (11)

Auto-updated Oct 5, 2026
Patch available. Sources: github, github_commit.
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
github_commit Patch Available

commit 3469357cff39 (lodash/lodash)

Patch available: lodash/lodash 4.18.0 (contains commit 3469357cff39)

https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c
githubMentions a patch (unverified)

Command Injection in lodash · CVE-2021-23337 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-35jh-r3h4-6jhm
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions.

https://access.redhat.com/errata/RHSA-2026:11469
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions.

https://access.redhat.com/errata/RHSA-2026:11454
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:10713
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:10710
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:10175
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:10131
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHBA-2026:21387
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:11470

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-console-rhel9:17876313822026-09-03redhat
redhatopenshift4/ose-console:17867533872026-09-03redhat
redhatopenshift4/ose-console:17870285592026-08-26redhat
redhatopenshift4/ose-console:17870564032026-08-26redhat
redhatopenshift4/ose-console-rhel9:17870541592026-08-26redhat
redhatopenshift4/ose-console:17864777602026-08-20redhat
redhatopenshift4/ose-console-rhel9:17852785692026-08-05redhat
redhatopenshift4/ose-console-rhel9:17846348772026-07-29redhat
redhatopenshift4/ose-console-rhel9:17841480702026-07-21redhat
redhatodf4/rook-ceph-rhel9-operator:17836775332026-07-20redhat
redhatautomation-gateway-0:2.5.20260715-1.el9ap2026-07-20redhat
redhatodf4/rook-ceph-rhel9-operator:17836853752026-07-20redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatopenshift4/ose-networking-console-plugin-rhel9:17829340802026-07-16redhat
redhatrhem/flightctl-ui-rhel10:17841945742026-07-16redhat
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatrhem/flightctl-ui-rhel9:17841277362026-07-15redhat
redhatopenshift4/ose-console-rhel9:17835023382026-07-14redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17822697942026-07-09redhat
redhatrhem/flightctl-ui-rhel9:17835024382026-07-08redhat
redhatlodash2026-07-02redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-pf6-rhel9:17828399962026-07-01redhat
redhatopenshift4/ose-console-rhel9:17822243902026-06-30redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhatautomation-platform-ui-0:2.6.9-1.el9ap2026-06-09redhat
redhatcockpit-image-builder-0:94.3-1.el10_22026-06-08redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17798749672026-06-03redhat
redhatopenshift4/ose-networking-console-plugin-rhel9:17792563222026-05-27redhat
redhatcockpit-0:356.1-1.el9_82026-05-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(10 across 6 ecosystems)
npm(5)
PackageVulnerable rangeFix by version rangeDependents
lodash—
  • every version up to 4.17.21: fixed in 4.17.21
  • 4.0.0 up to 4.18.0: fixed in 4.18.0
—
lodash-amd—
  • 4.0.0 up to 4.18.0: fixed in 4.18.0
—
lodash-es—
  • every version up to 4.17.21: fixed in 4.17.21
  • 4.0.0 up to 4.18.0: fixed in 4.18.0
—
lodash-template—
  • every version through 1.0.0: no fix on record
—
lodash.template—
  • every version through 4.5.0: no fix on record
  • 4.0.0 up to 4.18.0: fixed in 4.18.0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash4.17.21+dfsg+~cs8.31.173-1
  • every version up to 4.17.21+dfsg+~cs8.31.173-1+deb11u1: fixed in 4.17.21+dfsg+~cs8.31.173-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash4.17.21+dfsg+~cs8.31.198.20210220-9
  • every version up to 4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1: fixed in 4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash4.17.21+dfsg+~cs8.31.198.20210220-9
  • every version up to 4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1: fixed in 4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-lodash4.17.21+dfsg+~cs8.31.198.20210220-10, 4.17.21+dfsg+~cs8.31.198.20210220-9, 4.17.23+dfsg-1
  • every version up to 4.18.1+dfsg-1: fixed in 4.18.1+dfsg-1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
lodash-rails0.10.0 ... 4.6.1 (55 versions)
  • every version up to 4.17.21: fixed in 4.17.21
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 286 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-03 22:28 UTCOSV refresh
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-26 00:27 UTCEPSS rescore
  14. 2026-09-23 17:53 UTCEPSS rescore
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-14 12:35 UTCEG score recompute
  20. 2026-09-14 12:35 UTCVendor advisory
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 13:41 UTCVendor advisory
  24. 2026-09-10 12:28 UTCEG score recompute
  25. 2026-09-10 12:28 UTCVendor advisory
Show 75 more
  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-09 13:42 UTCVendor advisory
  3. 2026-09-09 12:40 UTCEG score recompute
  4. 2026-09-09 12:40 UTCVendor advisory
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-07 14:00 UTCVendor advisory
  8. 2026-09-07 13:18 UTCEG score recompute
  9. 2026-09-07 13:18 UTCVendor advisory
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 13:30 UTCVendor advisory
  12. 2026-09-04 12:23 UTCEG score recompute
  13. 2026-09-04 12:23 UTCVendor advisory
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-03 13:21 UTCVendor advisory
  16. 2026-09-03 12:29 UTCEG score recompute
  17. 2026-09-03 12:29 UTCVendor advisory
  18. 2026-09-02 14:12 UTCEPSS rescore
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 12:23 UTCEG score recompute
  21. 2026-09-01 12:23 UTCVendor advisory
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-31 13:35 UTCVendor advisory
  24. 2026-08-31 12:31 UTCEG score recompute
  25. 2026-08-31 12:31 UTCVendor advisory
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 01:22 UTCEPSS rescore
  28. 2026-08-28 21:41 UTCEPSS rescore
  29. 2026-08-27 14:25 UTCEPSS rescore
  30. 2026-08-27 13:37 UTCVendor advisory
  31. 2026-08-27 13:03 UTCVendor advisory
  32. 2026-08-26 16:12 UTCEG score recompute
  33. 2026-08-26 16:12 UTCVendor advisory
  34. 2026-08-26 14:46 UTCEPSS rescore
  35. 2026-08-26 12:23 UTCEG score recompute
  36. 2026-08-26 12:23 UTCVendor advisory
  37. 2026-08-25 13:49 UTCEPSS rescore
  38. 2026-08-25 13:25 UTCVendor advisory
  39. 2026-08-25 12:22 UTCEG score recompute
  40. 2026-08-25 12:22 UTCVendor advisory
  41. 2026-08-24 13:31 UTCVendor advisory
  42. 2026-08-24 12:27 UTCEG score recompute
  43. 2026-08-24 12:27 UTCVendor advisory
  44. 2026-08-23 00:19 UTCEPSS rescore
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 13:23 UTCVendor advisory
  47. 2026-08-21 12:32 UTCEG score recompute
  48. 2026-08-21 12:32 UTCVendor advisory
  49. 2026-08-20 22:55 UTCEPSS rescore
  50. 2026-08-20 13:59 UTCVendor advisory
  51. 2026-08-20 12:45 UTCEG score recompute
  52. 2026-08-20 12:45 UTCVendor advisory
  53. 2026-08-19 17:04 UTCEPSS rescore
  54. 2026-08-19 12:28 UTCVendor advisory
  55. 2026-08-19 12:12 UTCEG score recompute
  56. 2026-08-19 12:12 UTCVendor advisory
  57. 2026-08-18 13:48 UTCEPSS rescore
  58. 2026-08-18 12:21 UTCEG score recompute
  59. 2026-08-18 12:21 UTCVendor advisory
  60. 2026-08-17 13:47 UTCEPSS rescore
  61. 2026-08-17 12:25 UTCVendor advisory
  62. 2026-08-17 12:13 UTCEG score recompute
  63. 2026-08-17 12:13 UTCVendor advisory
  64. 2026-08-16 14:56 UTCEPSS rescore
  65. 2026-08-16 09:37 UTCEG score recompute
  66. 2026-08-16 09:37 UTCVendor advisory
  67. 2026-08-16 02:14 UTCEPSS rescore
  68. 2026-08-15 01:30 UTCEPSS rescore
  69. 2026-08-14 23:13 UTCVendor advisory
  70. 2026-08-14 19:04 UTCVendor advisory
  71. 2026-08-14 14:18 UTCVendor advisory
  72. 2026-08-14 10:09 UTCVendor advisory
  73. 2026-08-14 06:00 UTCEG score recompute
  74. 2026-08-14 06:00 UTCVendor advisory
  75. 2026-08-13 22:00 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCthrealwinky/CVE-2026-4800-POC
    First seen Apr 1, 2026
    Open source ↗

Frequently asked(5)

What is CVE-2026-4800?
CVE-2026-4800 is a critical vulnerability published on March 31, 2026. 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…
When was CVE-2026-4800 disclosed?
CVE-2026-4800 was first published on March 31, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4800 actively exploited?
CVE-2026-4800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4800?
CVE-2026-4800 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-4800?
A fix for CVE-2026-4800 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4800 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4800

Explore →

Is Your Infrastructure Affected by CVE-2026-4800?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.