CVE-2026-27837

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: 0.4% (30th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.3 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-02-26) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-8788 (ENISA EUVD) · GHSA-r5mx-6wc6-7h9w (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Dottie provides nested object access and manipulation in JavaScript. Versions 2.0.4 through 2.0.6 contain an incomplete fix for CVE-2023-26132. The prototype pollution guard introduced in commit 7d3aee1 only validates the first segment of a dot-separated path, allowing an attacker to bypass the protection by placing __proto__ at any position other than the first. Both dottie.set() and dottie.transform() are affected. Version 2.0.7 contains an updated fix to address the residual vulnerability.

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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
0.4%
EPSS %ILE
30th
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
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 60 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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

February 26, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Oct 31, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Incomplete fix for CVE-2023-26132: Prototype pollution bypass via non-first path segments in set() and transform() · Advisory · mickhansen/dottie.js · GitHub

https://github.com/mickhansen/dottie.js/security/advisories/GHSA-r5mx-6wc6-7h9w
GitHub commit

commit 7e8fa1345a4b (mickhansen/dottie.js)

Fix landed in mickhansen/dottie.js commit 7e8fa1345a4b — awaiting tagged release

https://github.com/mickhansen/dottie.js/commit/7e8fa1345a4b46325f0eab8d7aeb1c4deaefdb14
GitHub advisoryMentions a patch (unverified)

dottie vulnerable to Prototype Pollution · CVE-2023-26132 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-4gxf-g5gf-22h4

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmdottie @ 2.0.7 (fixes >= 2.0.4, <= 2.0.6)—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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-dottie2.0.2-1 ... 2.0.7+~2.0.7-1 (8 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-dottie2.0.2-4, 2.0.2-4+deb12u1, 2.0.6+~2.0.5-1, 2.0.6+~2.0.5-2, 2.0.7+~2.0.7-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-dottie2.0.6+~2.0.5-2, 2.0.7+~2.0.7-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-dottie2.0.6+~2.0.5-2
  • every version up to 2.0.7+~2.0.7-1: fixed in 2.0.7+~2.0.7-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
dottie—
  • 2.0.4 up to 2.0.7: fixed in 2.0.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 60× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 96 of 125 refreshes 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-11-02 14:30 UTCEG score recompute
  3. 2026-11-02 14:30 UTCGHSA enrichmentGHSA-r5mx-6wc6-7h9w · GitHub severity MODERATE · GitHub CVSS 6.3
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-11-01 13:48 UTCGHSA enrichmentGHSA-r5mx-6wc6-7h9w · GitHub severity MODERATE · GitHub CVSS 6.3
  6. 2026-11-01 07:56 UTCGHSA enrichmentGHSA-r5mx-6wc6-7h9w · GitHub severity MODERATE · GitHub CVSS 6.3
  7. 2026-11-01 07:56 UTCEG score recompute
  8. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-31 13:06 UTCEG score recompute
  10. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-30 12:21 UTCEG score recompute
  12. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-29 11:40 UTCEG score recompute
  14. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-28 10:57 UTCEG score recompute
  16. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-27 09:20 UTCEG score recompute
  18. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-26 08:15 UTCEG score recompute
  20. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-25 14:38 UTCEG score recompute
  22. 2026-10-25 07:34 UTCEG score recompute
  23. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  24. 2026-10-24 06:52 UTCEG score recompute
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 45th percentile
Show 71 more
  1. 2026-10-23 06:10 UTCEG score recompute
  2. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-10-22 05:25 UTCEG score recompute
  4. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-10-21 04:43 UTCEG score recompute
  6. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-20 04:01 UTCEG score recompute
  8. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-19 03:18 UTCEG score recompute
  10. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-18 03:51 UTCEG score recompute
  12. 2026-10-18 02:35 UTCEG score recompute
  13. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-17 01:52 UTCEG score recompute
  15. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-16 01:08 UTCEG score recompute
  17. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-14 20:11 UTCEG score recompute
  19. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-13 16:20 UTCEG score recompute
  22. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-12 15:37 UTCEG score recompute
  24. 2026-10-11 19:59 UTCEG score recompute
  25. 2026-10-11 17:12 UTCEG score recompute
  26. 2026-10-11 14:43 UTCEG score recompute
  27. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-10-09 14:25 UTCOSV refresh
  31. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  35. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  41. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  42. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  43. 2026-09-19 21:50 UTCOSV refresh
  44. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  45. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  48. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  52. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  56. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  57. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  58. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  59. 2026-09-01 01:04 UTCOSV refresh
  60. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  61. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  62. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  63. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  64. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  65. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  66. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  68. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  69. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  70. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  71. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Related CVEs(same product + same CWE)

Same product

1 shown

Debian:11:node-dottie

Frequently asked(5)

What is CVE-2026-27837?
CVE-2026-27837 is a critical-severity vulnerability; its CVE record was published on February 26, 2026. Dottie provides nested object access and manipulation in JavaScript. Versions 2.0.4 through 2.0.6 contain an incomplete fix for CVE-2023-26132. The prototype pollution guard introduced in commit 7d3aee1 only validates the first segment of a dot-separated path, allowing an attacker to bypass the…
When was the CVE record for CVE-2026-27837 published?
The CVE record for CVE-2026-27837 was published on February 26, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-27837 actively exploited?
CVE-2026-27837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27837?
CVE-2026-27837 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-27837?
A fix for CVE-2026-27837 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-27837?

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

Book a Demo →Browse All CVEs