CVE-2026-4800

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.8% (86th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-01) is not newer than that change (2026-10-15), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — Patch released this weekElevated

Also known asEUVD-2026-17610 (ENISA EUVD) · GHSA-r5fr-rjxr-66jc (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.8%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names, and 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, so if Object.prototype has been polluted by another vector the polluted keys are copied into the imports object and passed to Function(). The issue is fixed in 4.18.1 for lodash, lodash-es, lodash-amd, and lodash.template. As a workaround, do not pass untrusted input as key names in options.imports; use only 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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
2.8%
EPSS %ILE
86th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 31, 2026

Last Modified

October 15, 2026

Advisory Details (19)

Auto-updated Nov 7, 2026
Patch available. Sources: github, redhat.
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:11470
Red HatMentions a patch (unverified)

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

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

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

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

Affected: Red Hat Enterprise Linux 10.

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

Affected: Red Hat Enterprise Linux 9.

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

Affected: Red Hat Enterprise Linux 9.

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

lodash vulnerable to Code Injection via `_.template` imports key names · Advisory · lodash/lodash · GitHub

https://github.com/lodash/lodash/security/advisories/GHSA-r5fr-rjxr-66jc
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:24331
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:17789
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:24762
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:42078
Red HatMentions a patch (unverified)

2453496 – (CVE-2026-4800) CVE-2026-4800 lodash: lodash: Arbitrary code execution via untrusted input in template imports

Affected: Red Hat Enterprise Linux 9

https://bugzilla.redhat.com/show_bug.cgi?id=2453496
Red HatMentions a patch (unverified)

CVE-2026-4800 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-4800
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
GitHub advisoryMentions a patch (unverified)

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

https://github.com/advisories/GHSA-35jh-r3h4-6jhm

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcockpit-machines-0:355-1.el92026-11-10redhat
redhatcockpit-machines-0:355-1.el102026-11-10redhat
redhatcockpit-podman-0:129-1.el102026-11-10redhat
redhatcockpit-podman-0:129-1.el92026-11-10redhat
redhatsubscription-manager-cockpit-0:17-1.el92026-11-10redhat
redhatcockpit-files-0:43-1.el92026-11-10redhat
redhatsubscription-manager-cockpit-0:17-1.el102026-11-10redhat
redhatcockpit-files-0:43-1.el102026-11-10redhat
redhatodf4/rook-ceph-rhel9-operator:17919675402026-10-15redhat
redhatrhtas/rekor-search-ui-rhel9:17915343392026-10-15redhat
redhatodf4/rook-ceph-rhel9-operator:17918890632026-10-15redhat
redhatdevspaces/pluginregistry-rhel9:17888831792026-09-17redhat
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
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatrhem/flightctl-ui-rhel10:17841945742026-07-16redhat
redhatrhem/flightctl-ui-rhel9:17841277362026-07-15redhat
redhatopenshift4/ose-console-rhel9:17835023382026-07-14redhat
npmlodash @ 4.18.0 (fixes >= 4.0.0, <= 4.17.23)—ghsa

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

(8 across 5 ecosystems)
npm(4)
PackageVulnerable rangeFix by version rangeDependents
lodash—
  • 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—
  • 4.0.0 up to 4.18.0: fixed in 4.18.0
—
lodash.template—
  • 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
—

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 19× in last 7d / 71× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 399 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 299 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 19:53 UTCEchelonGraph re-scored
  2. 2026-11-12 19:53 UTCVendor advisory
  3. 2026-11-12 19:53 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-12 16:34 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  5. 2026-11-11 17:36 UTCEchelonGraph re-scored
  6. 2026-11-11 17:36 UTCVendor advisory
  7. 2026-11-11 17:36 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-11-11 16:39 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  9. 2026-11-10 16:44 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  10. 2026-11-10 15:18 UTCEchelonGraph re-scored
  11. 2026-11-10 15:18 UTCVendor advisory
  12. 2026-11-10 15:18 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-11-09 16:35 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  14. 2026-11-09 12:59 UTCEchelonGraph re-scored
  15. 2026-11-09 12:59 UTCVendor advisory
  16. 2026-11-09 12:59 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-11-08 16:39 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  18. 2026-11-08 10:42 UTCEchelonGraph re-scored
  19. 2026-11-08 10:42 UTCVendor advisory
  20. 2026-11-08 10:42 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-11-07 16:39 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  22. 2026-11-07 08:24 UTCEchelonGraph re-scored
  23. 2026-11-07 08:24 UTCVendor advisory
  24. 2026-11-07 08:24 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-11-06 16:38 UTCEPSS rescoreEPSS 2.8% · 86th percentile
Show 75 more
  1. 2026-11-06 10:25 UTCOSV refresh
  2. 2026-11-06 06:08 UTCEchelonGraph re-scored
  3. 2026-11-06 06:08 UTCVendor advisory
  4. 2026-11-06 06:07 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-11-05 16:38 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  6. 2026-11-05 03:50 UTCEchelonGraph re-scored
  7. 2026-11-05 03:50 UTCVendor advisory
  8. 2026-11-05 03:50 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-11-04 16:35 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  10. 2026-11-04 01:32 UTCEchelonGraph re-scored
  11. 2026-11-04 01:32 UTCVendor advisory
  12. 2026-11-04 01:32 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-11-03 16:48 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  14. 2026-11-02 23:15 UTCEchelonGraph re-scored
  15. 2026-11-02 23:15 UTCVendor advisory
  16. 2026-11-02 23:15 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-11-02 16:45 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  18. 2026-11-01 20:57 UTCEchelonGraph re-scored
  19. 2026-11-01 20:57 UTCVendor advisory
  20. 2026-11-01 20:57 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-11-01 16:34 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  22. 2026-11-01 07:47 UTCGHSA enrichmentGHSA-r5fr-rjxr-66jc · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-11-01 07:47 UTCEchelonGraph re-scored
  24. 2026-10-31 18:41 UTCEchelonGraph re-scored
  25. 2026-10-31 18:41 UTCVendor advisory
  26. 2026-10-31 16:33 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  27. 2026-10-30 16:34 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  28. 2026-10-30 16:23 UTCEchelonGraph re-scored
  29. 2026-10-30 16:23 UTCVendor advisory
  30. 2026-10-29 16:33 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  31. 2026-10-29 14:06 UTCEchelonGraph re-scored
  32. 2026-10-29 14:06 UTCVendor advisory
  33. 2026-10-28 16:32 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  34. 2026-10-28 11:49 UTCEchelonGraph re-scored
  35. 2026-10-28 11:49 UTCVendor advisory
  36. 2026-10-27 16:32 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  37. 2026-10-27 09:23 UTCEchelonGraph re-scored
  38. 2026-10-27 09:23 UTCVendor advisory
  39. 2026-10-26 16:31 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  40. 2026-10-26 06:52 UTCEchelonGraph re-scored
  41. 2026-10-26 06:52 UTCVendor advisory
  42. 2026-10-25 16:33 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  43. 2026-10-25 14:23 UTCEchelonGraph re-scored
  44. 2026-10-25 04:31 UTCEchelonGraph re-scored
  45. 2026-10-25 04:31 UTCVendor advisory
  46. 2026-10-24 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  47. 2026-10-24 02:15 UTCEchelonGraph re-scored
  48. 2026-10-24 02:15 UTCVendor advisory
  49. 2026-10-23 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  50. 2026-10-22 23:58 UTCEchelonGraph re-scored
  51. 2026-10-22 23:58 UTCVendor advisory
  52. 2026-10-22 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  53. 2026-10-21 21:39 UTCEchelonGraph re-scored
  54. 2026-10-21 21:39 UTCVendor advisory
  55. 2026-10-21 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  56. 2026-10-20 19:01 UTCEchelonGraph re-scored
  57. 2026-10-20 19:01 UTCVendor advisory
  58. 2026-10-20 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  59. 2026-10-19 16:43 UTCEchelonGraph re-scored
  60. 2026-10-19 16:43 UTCVendor advisory
  61. 2026-10-19 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  62. 2026-10-18 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  63. 2026-10-18 14:23 UTCVendor advisory
  64. 2026-10-18 03:35 UTCEchelonGraph re-scored
  65. 2026-10-17 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  66. 2026-10-17 12:05 UTCEchelonGraph re-scored
  67. 2026-10-17 12:05 UTCVendor advisory
  68. 2026-10-16 16:42 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  69. 2026-10-16 09:46 UTCEchelonGraph re-scored
  70. 2026-10-16 09:46 UTCVendor advisory
  71. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  72. 2026-10-15 07:28 UTCVendor advisory
  73. 2026-10-15 06:59 UTCEchelonGraph re-scored
  74. 2026-10-15 06:59 UTCVendor advisory
  75. 2026-10-14 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

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

Frequently asked(5)

What is CVE-2026-4800?
CVE-2026-4800 is a critical-severity vulnerability; its CVE record was published on March 31, 2026. The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names, and both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker…
When was the CVE record for CVE-2026-4800 published?
The CVE record for CVE-2026-4800 was published on March 31, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-4800 actively exploited?
CVE-2026-4800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% probability of exploitation in the next 30 days (86th 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.