Quick answers
- Is CVE-2026-26449 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-26449 being exploited in the wild.
- How severe is CVE-2026-26449?
- High severity, with a CVSS score of 7.5, published 26 August 2026.
- Which products and versions are affected?
- Mdoi Stomper commit 5e2741e.
- Is there a fix for CVE-2026-26449?
- 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-26449 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-26449?
- 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
The vulnerability is a null pointer dereference in the StompSend class. The Dest member variable is not initialized in the constructor and is only set via set_header() when a destination header is present in the SEND frame. An attacker can send a SEND frame with a missing destination header; the uninitialized Dest pointer then contains garbage values, and when execute() attempts to dereference it with Dest->name(), the process crashes. Attack vector is network; the attacker must first complete a STOMP CONNECT handshake, but no additional authentication bypass is required. The fix is to initialize Dest to NULL in the constructor and add proper null checks before dereferencing.
Affected products
- mdoi Stomper commit 5e2741e
Timeline
- 2026-08-26: disclosed