# CVE-2026-26446: Stomper STOMP broker denial of service from unhandled SIGPIPE

Source: https://junglewise.ai/threats/cve-2026-26446-stomper-stomp-broker-denial-of-service-from-unhandled-sigpipe  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-26. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-26446 · Severity: high · CVSS 7.5 · Published 2026-08-26

Stomper is an open-source message broker implementing the STOMP protocol. An unauthenticated attacker can crash the server process by opening a connection, sending a CONNECT frame, and immediately closing the socket. The server attempts to send a response to the closed socket and receives an unhandled SIGPIPE signal, terminating the entire broker service and causing a denial of service.

Technologies: [Mdoi Stomper](https://junglewise.ai/threats/technologies/stomper). Vendors: [Mdoi](https://junglewise.ai/threats/vendors/mdoi).

## Quick answers

**Is CVE-2026-26446 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-26446 being exploited in the wild.

**How severe is CVE-2026-26446?** High severity, with a CVSS score of 7.5, published 26 August 2026.

**Which products and versions are affected?** Mdoi Stomper 5e2741e.

**Is there a fix for CVE-2026-26446?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-26446 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-26446?** Check whether you run Mdoi Stomper at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

This is a signal handling vulnerability (CWE-390) in the StompStreamSocket::send_buf() function. The vulnerable code performs raw send() syscalls on potentially closed sockets without suppressing SIGPIPE or checking for EPIPE errors. When a client closes its TCP connection while the server is sending data (e.g., after a CONNECT frame), the kernel delivers SIGPIPE to the process, which has no handler installed and causes immediate termination. Any unauthenticated client can trigger this by connecting, sending a CONNECT frame, and closing the socket before reading the CONNECTED response. The fix is to use MSG_NOSIGNAL flag in the send() call and handle EPIPE errors gracefully to close the faulty connection rather than crashing the entire broker.

## Affected products

- mdoi Stomper 5e2741e

## Timeline

- 2026-08-26: disclosed: Published on NVD
- 2026-08-26: advisory

## References

- [https://github.com/mdoi/stomper](https://github.com/mdoi/stomper)
- [https://github.com/songxpu/bug_report/blob/master/Stomp/stomper_vuln2.md](https://github.com/songxpu/bug_report/blob/master/Stomp/stomper_vuln2.md)

## Related threats

- [Stomper STOMP message broker null pointer dereference](https://junglewise.ai/threats/cve-2026-26449-stomper-stomp-message-broker-null-pointer-dereference)
- [stomper STOMP message broker denial of service via partial frames](https://junglewise.ai/threats/cve-2026-26445-stomper-stomp-message-broker-denial-of-service-via-partial-frames)