CVE-2026-66921

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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, secondary
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Pivotick’s Markdown node-reference renderer failed to HTML-escape the attacker-controlled nodeName value before interpolating it into both the data-node-name attribute and the body of a generated element.

Because the node-reference tokenizer rejected only square brackets, a crafted node name could still contain quotation marks, angle brackets, or other HTML metacharacters. An attacker could therefore terminate the quoted attribute or inject additional HTML elements and event-handler attributes.

When malicious node-reference content is rendered by a consumer that does not apply DOMPurify or equivalent sanitization, arbitrary JavaScript may execute in the victim’s browser in the security context of the application. Successful exploitation requires a victim to open or render a crafted graph or note and could allow the attacker to access same-origin information, modify displayed content, or perform actions using the victim’s session.

The patch resolves the issue by applying context-appropriate HTML escaping to node names before inserting them into either HTML text or quoted attribute values. The shared escaping function now encodes ampersands, angle brackets, and both types of quotation marks.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

July 28, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 4c13ff2b0ec7 (Pivotick/Pivotick)

Fix landed in Pivotick/Pivotick commit 4c13ff2b0ec7 — awaiting tagged release

https://github.com/Pivotick/Pivotick/commit/4c13ff2b0ec769881b5526feddef37c0c5a08885

Vendor Advisories for CVE-2026-66921(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 15× in last 7d / 81× 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.

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

Frequently asked(5)

What is CVE-2026-66921?
CVE-2026-66921 is a medium vulnerability published on July 28, 2026. Pivotick’s Markdown node-reference renderer failed to HTML-escape the attacker-controlled nodeName value before interpolating it into both the data-node-name attribute and the body of a generated <span> element. Because the node-reference tokenizer rejected only square brackets, a crafted node name…
When was CVE-2026-66921 disclosed?
CVE-2026-66921 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66921 actively exploited?
CVE-2026-66921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.3% of all scored CVEs.
What is the CVSS score of CVE-2026-66921?
CVE-2026-66921 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-66921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66921, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-66921?

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