CVE-2026-81753

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

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

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

Affected versions of Flowintel render Mermaid blocks contained in stored case notes without sufficiently neutralizing attacker-controlled markup. Because Mermaid note content is persisted and later rendered for other users, an attacker with permission to create or edit a note could store a crafted Mermaid payload that results in JavaScript execution when another user views the affected case note.

The patch adds explicit Mermaid detection and HTML escaping around the token content before the generated Mermaid wrapper is returned. It also moves the wrapping logic earlier in page initialization so Markdown instances are protected consistently.

Version impacted >= 3.3.0

CVSS v3
5.1
EG Score
5.1(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
Severity51% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

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

commit 61c97e67f5d0 (flowintel/flowintel)

Fix landed in flowintel/flowintel commit 61c97e67f5d0 — awaiting tagged release

https://github.com/flowintel/flowintel/commit/61c97e67f5d04030f26e7900c470b52f9f37da06

Vendor Advisories for CVE-2026-81753(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 9× in last 7d / 9× 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 15:03 UTCEG score recompute
  3. 2026-08-29 15:03 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 15:45 UTCGHSA enrichment
  6. 2026-08-27 17:27 UTCGHSA enrichment
  7. 2026-08-27 13:32 UTCEG score recompute
  8. 2026-08-27 12:59 UTCEG score recompute
  9. 2026-08-27 12:58 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81753?
CVE-2026-81753 is a medium vulnerability published on August 27, 2026. Affected versions of Flowintel render Mermaid blocks contained in stored case notes without sufficiently neutralizing attacker-controlled markup. Because Mermaid note content is persisted and later rendered for other users, an attacker with permission to create or edit a note could store a crafted…
When was CVE-2026-81753 disclosed?
CVE-2026-81753 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81753 actively exploited?
CVE-2026-81753 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 72.0% of all scored CVEs.
What is the CVSS score of CVE-2026-81753?
CVE-2026-81753 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-81753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81753, 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-81753

Explore →

Is Your Infrastructure Affected by CVE-2026-81753?

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