CVE-2026-33387

MEDIUMPre-NVD 4.64.6
EchelonGraph scoreMEDIUM confidence

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

Score 4.6 from GitHub Security Advisory (severity: MODERATE) published 2026-09-08. A secondary CVSS source baseline 4.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-72761 (ENISA EUVD) · GHSA-xp2q-mg9h-jmmm (GitHub Security Advisories)Source: ENISA EUVD

4.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.6Exploit: None knownExposed services: Not assessed

Upgrade to v26.3.0 or later (from the CVE record's solution, Nozomi Networks Inc.) — apply it.

A template injection vulnerability was discovered in the Dashboards functionality due to improper validation of an input parameter. An authenticated user with the required privileges can define a dashboard containing a malicious payload, or a victim can be socially engineered into importing a malicious dashboard. When the victim views or imports the dashboard, the payload executes in their browser context, allowing the attacker to modify application data or disrupt application availability.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity46% × 45%
Impact severity (EG Severity): CVSS 4.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: Upgrade to v26.3.0 or later (from the CVE record's solution, Nozomi Networks Inc.). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
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 (4.6): severity, escalated by confirmed exploitation. This CVE's 4.6 is its impact severity (EG Severity), not escalated.

EG Severity
4.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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 every mission impact level.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 every mission impact level.

Upgrade to v26.3.0 or later (from the CVE record's solution, Nozomi Networks Inc.). Apply it within your standard update timelines.

Exploitation none (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

September 8, 2026

Last Modified

October 15, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
Fix named in the CVE record's solution (Nozomi Networks Inc.).
Web page

NN-2026:16-01 - Insufficient sanitization of Dashboards in Guardian/CMC before 26.3.0 - CVE-2026-33387 | Product Security Incident Response Portal

https://security.nozominetworks.com/NN-2026:16-01

Vendor Advisories for CVE-2026-33387(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 134 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 34 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-33387?
CVE-2026-33387 is a medium-severity vulnerability; its CVE record was published on September 8, 2026. A template injection vulnerability was discovered in the Dashboards functionality due to improper validation of an input parameter. An authenticated user with the required privileges can define a dashboard containing a malicious payload, or a victim can be socially engineered into importing a…
When was CVE-2026-33387 made public?
CVE-2026-33387 was made public on September 8, 2026: that is the date its CVE record's CNA, Nozomi Networks Inc., gives for when the vulnerability was made public. The CVE record itself was published on September 8, 2026. 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-33387 actively exploited?
CVE-2026-33387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33387?
CVE-2026-33387 has a CVSS base score of 4.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-33387?
The CVE record's solution for CVE-2026-33387, written by its CNA Nozomi Networks Inc., names the fix: "Upgrade to v26.3.0 or later." The vendor advisories EchelonGraph has for CVE-2026-33387 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-33387

Explore →

Is Your Infrastructure Affected by CVE-2026-33387?

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