High [CVE-2026-26446] Denial of Service due to improper handling of closed TCP connections
This high-severity Red Hat Linux advisory covers CVE-2026-26446.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Stomper 5e2741e is vulnerable to Denial of Service. When a broker sends data to a client whose TCP connection was already closed by the peer, the server process receives SIGPIPE and immediately terminates, resulting in a denial of service.
Any unauthenticated client can trigger the crash by closing the socket at specific points. A flaw was found in Stomper.
This action causes the server process to receive a SIGPIPE signal, leading to its immediate termination and a denial of service for legitimate users. Because the process fails to ignore or handle SIGPIPE during active write operations, the daemon terminates abruptly.
Red Hat default security controls (such as process isolation and systemd service auto-restart directives) restrict the failure strictly to an availability impact on the message broker service, without allowing privilege escalation or memory corruption. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Weakness: CWE-248.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- Configure network firewalls or ingress access controls to limit access to the STOMP server port strictly to trusted IP addresses. Alternatively, run the broker within a process manager or container platform configured to automatically restart the service upon abrupt termination.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.