Quick answers
- Is CVE-2026-19654 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19654 being exploited in the wild.
- How severe is CVE-2026-19654?
- High severity, with a CVSS score of 7.5, published 12 August 2026.
- Which products and versions are affected?
- rsyslog rsyslog.
- Is there a fix for CVE-2026-19654?
- 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-19654 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19654?
- Check whether you run Rsyslog. 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 vulnerability is a denial-of-service (DoS) flaw in rsyslog's optional imptcp (improved TCP input) module. The vulnerability stems from improper handling of oversize-frame recovery, where a crafted input sequence can trigger an invalid internal message length calculation. An unauthenticated remote peer can exploit this via network connectivity to the imptcp listener to cause rsyslogd to terminate abnormally. The vulnerability does not affect the default imptcp framing modes, imtcp module, or allow for code execution, privilege escalation, or data compromise. The fix/patch status should be confirmed with the rsyslog maintainers.
Affected products
- rsyslog rsyslog
Timeline
- 2026-08-12: disclosed