CVE-2026-72726

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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

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

Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, an authenticated user could eavesdrop on private AI bot conversations through the AI bot reply stream. The issue is fixed in 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 10, 2026

Advisory Details (5)

Auto-updated Aug 10, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Unauthorized eavesdropping on private AI bot conversations. · Advisory · discourse/discourse · GitHub

https://github.com/discourse/discourse/security/advisories/GHSA-gw88-2jw8-jf2h
github_commit

commit b56b98232aa4 (discourse/discourse)

Fix landed in discourse/discourse commit b56b98232aa4 — awaiting tagged release

https://github.com/discourse/discourse/commit/b56b98232aa4dad4a30500a65e31db0c9080c8f5
github_commit

commit 9247666f8359 (discourse/discourse)

Fix landed in discourse/discourse commit 9247666f8359 — awaiting tagged release

https://github.com/discourse/discourse/commit/9247666f8359f3cf214b8aea3d396e8a8237ed38
github_commit

commit 1fb2026eb800 (discourse/discourse)

Fix landed in discourse/discourse commit 1fb2026eb800 — awaiting tagged release

https://github.com/discourse/discourse/commit/1fb2026eb8004dfeb12553014cc534dfd8083fbc
github_commit

commit 01faa889830f (discourse/discourse)

Fix landed in discourse/discourse commit 01faa889830f — awaiting tagged release

https://github.com/discourse/discourse/commit/01faa889830f56e02fba2f6c1731811d319c5e81

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 40× 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 09:58 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-28 04:03 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 04:41 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-26 05:24 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 06:10 UTCEG score recompute
  11. 2026-08-23 07:39 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 08:25 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 09:11 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-20 09:56 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-19 10:42 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 11:21 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 12:05 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 15 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 12:49 UTCEG score recompute
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 13:35 UTCEG score recompute
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-14 14:20 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 15:51 UTCEG score recompute
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 16:37 UTCEG score recompute
  11. 2026-08-10 17:22 UTCEG score recompute
  12. 2026-08-10 17:10 UTCEG score recompute
  13. 2026-08-10 16:29 UTCEG score recompute
  14. 2026-08-10 16:10 UTCEG score recompute
  15. 2026-08-10 16:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72726?
CVE-2026-72726 is a medium vulnerability published on August 10, 2026. Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, an authenticated user could eavesdrop on private AI bot conversations through the AI bot reply stream. The issue is fixed in 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.
When was CVE-2026-72726 disclosed?
CVE-2026-72726 was first published in the National Vulnerability Database on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72726 actively exploited?
CVE-2026-72726 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 74.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72726?
CVE-2026-72726 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-72726?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72726, 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-72726

Explore →

Is Your Infrastructure Affected by CVE-2026-72726?

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

Start Free Scan →Browse All CVEs