CVE-2026-26448: Stomper 5e2741e is vulnerable to Use-After-Free.
Stomper 5e2741e is vulnerable to Use-After-Free. When a client sends multiple CONNECT frames on the same TCP connection, and subsequently another client (or a later connection) sends SEND frames to a destination previously subscribed on that connection, the broker may dereference a pointer to a StompStreamSocket object that has already been freed. This results in a heap use-after-free and process crash. Because the protocol does not authenticate or restrict such sequences by default.
Security readout for executives and security teams
Plain-English summary
A remotely reachable Stomper broker at revision 5e2741e can crash after specially sequenced STOMP connections leave it referencing freed memory. No authentication or user interaction is reportedly required. This creates serious availability risk, but the supplied evidence does not demonstrate data theft, data modification, or code execution.
Executive priority
Treat internet-facing or broadly reachable deployments as urgent. Immediately reduce untrusted access and determine whether revision 5e2741e is present. Prioritize service resilience because a remote unauthenticated crash is described. Do not assume confidentiality or integrity compromise without further evidence.
Technical view
Multiple CONNECT frames on one TCP connection can leave a subscribed destination associated with a freed StompStreamSocket. A later SEND to that destination may dereference the stale pointer, causing a heap use-after-free and broker process crash. The record assigns CVSS 3.1 score 9.8 and CWE-416.
Likely exposure
Exposure is likely where Stomper revision 5e2741e is deployed and untrusted clients can reach its STOMP TCP listener. The bundle provides no product inventory, CPE, deployment prevalence, or broader affected-version range, so organizations must verify revision and reachability directly.
Exploitation context
The described condition is remotely triggerable with low complexity, no privileges, and no user interaction. CVE-2026-26448 is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation. A public technical bug report exists, increasing awareness, but exploitation prevalence remains unknown.
Researcher notes
The concrete documented impact is heap use-after-free leading to process termination. Although the supplied CVSS vector rates confidentiality, integrity, and availability high, the narrative does not substantiate memory disclosure, state modification, or code execution. Affected-version boundaries and a fixed revision are not provided.
Mitigation direction
Identify and prioritize every deployment built from Stomper revision 5e2741e.
Restrict STOMP listener access to trusted clients using available network controls.
Check the upstream repository and CVE record for confirmed patches or updated guidance.
Reduce untrusted protocol access until a vendor-supported remediation is available.
Monitor broker crashes and restart safely to limit availability impact.
Validation and detection
Confirm deployed Stomper source revisions and dependencies against revision 5e2741e.
Map every reachable STOMP TCP listener and its permitted client populations.
Review broker logs and crash records for unexplained failures involving repeated connections or destinations.
Verify network controls prevent unauthorised clients from reaching affected listeners.
Confirm remediation against updated upstream guidance before restoring broader access.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.