CVE-2026-26447

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

Stomper 5e2741e is vulnerable to Use-After-Free. When a single client repeatedly issues SUBSCRIBE commands for the same destination over one connection and then closes that connection, the broker performs incorrect cleanup of its internal subscription structures. This results in a heap use-after-free during StompClient destruction, causing the broker process to crash. An unauthenticated client can exploit this to reliably trigger a denial of service.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

bug_report/Stomp/stomper_vuln3.md at master · songxpu/bug_report · GitHub

https://github.com/songxpu/bug_report/blob/master/Stomp/stomper_vuln3.md
generic

GitHub - mdoi/stomper: An implementation of message broker of the Streaming Text Orientated Messaging Protocol · GitHub

https://github.com/mdoi/stomper

Vendor Advisories for CVE-2026-26447(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 17× in last 7d / 17× 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:59 UTCGHSA enrichment
  3. 2026-08-29 10:53 UTCGHSA enrichment
  4. 2026-08-28 21:41 UTCEG score recompute
  5. 2026-08-28 21:41 UTCGHSA enrichment
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-28 09:40 UTCEG score recompute
  8. 2026-08-28 09:40 UTCGHSA enrichment
  9. 2026-08-27 20:28 UTCEG score recompute
  10. 2026-08-27 20:28 UTCGHSA enrichment
  11. 2026-08-27 20:17 UTCEG score recompute▲ 7.50
  12. 2026-08-27 20:16 UTCGHSA enrichment
  13. 2026-08-27 20:13 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 20:24 UTCNVD update
  16. 2026-08-26 20:07 UTCEG score recompute
  17. 2026-08-26 20:06 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-26447?
CVE-2026-26447 is a high vulnerability published on August 26, 2026. Stomper 5e2741e is vulnerable to Use-After-Free. When a single client repeatedly issues SUBSCRIBE commands for the same destination over one connection and then closes that connection, the broker performs incorrect cleanup of its internal subscription structures. This results in a heap…
When was CVE-2026-26447 disclosed?
CVE-2026-26447 was first published in the National Vulnerability Database on August 26, 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-26447 actively exploited?
CVE-2026-26447 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 73.0% of all scored CVEs.
What is the CVSS score of CVE-2026-26447?
CVE-2026-26447 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-26447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26447, 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-26447

Explore →

Is Your Infrastructure Affected by CVE-2026-26447?

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

Start Free Scan →Browse All CVEs