CVE-2026-73059

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-16. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
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.

stoatchat before 0.15.0 contains a permission bypass vulnerability in the message_fetch route that checks only ViewChannel permission instead of requiring ReadMessageHistory. Attackers with ViewChannel access but ReadMessageHistory denied can retrieve individual message content by ID, bypassing the intended history restriction enforced by bulk read routes.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
34(Track)
EG Risk 34/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 16, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

stoatchat before 0.15.0 Permission Bypass via message_fetch | Advisories | VulnCheck

https://www.vulncheck.com/advisories/stoatchat-before-permission-bypass-via-message-fetch
github Patch Available🟡 PoC Available

fetching a single message checks only ViewChannel, not ReadMessageHistory (bypasses a view-without-history channel restriction) · Advisory · stoatchat/stoatchat · GitHub

Affected: 0.8.2). That fix is actually why message_query and message_search now carry the R

https://github.com/stoatchat/stoatchat/security/advisories/GHSA-8qp4-h9xf-2vqr

Vendor Advisories for CVE-2026-73059(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 16× in last 7d / 16× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 18:25 UTCGHSA enrichment
  3. 2026-08-19 18:21 UTCEG score recompute
  4. 2026-08-19 18:21 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 16:59 UTCEG score recompute
  7. 2026-08-18 16:59 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-17 16:24 UTCGHSA enrichment
  11. 2026-08-17 14:39 UTCEG score recompute
  12. 2026-08-17 14:39 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:36 UTCEG score recompute
  15. 2026-08-16 13:27 UTCEG score recompute
  16. 2026-08-16 13:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73059?
CVE-2026-73059 is a medium vulnerability published on August 16, 2026. stoatchat before 0.15.0 contains a permission bypass vulnerability in the message_fetch route that checks only ViewChannel permission instead of requiring ReadMessageHistory. Attackers with ViewChannel access but ReadMessageHistory denied can retrieve individual message content by ID, bypassing the…
When was CVE-2026-73059 disclosed?
CVE-2026-73059 was first published in the National Vulnerability Database on August 16, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73059 actively exploited?
CVE-2026-73059 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 87.0% of all scored CVEs.
What is the CVSS score of CVE-2026-73059?
CVE-2026-73059 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-73059?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73059, 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-73059

Explore →

Is Your Infrastructure Affected by CVE-2026-73059?

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

Start Free Scan →Browse All CVEs