A unauthenticated remote peer may lead rsyslogd to crash due to a flaw in the optional imptcp module. A crafted input sequence during oversize-frame recovery can cause an invalid internal message length and terminate rsyslogd. No confidentiality or integrity impact, privilege escalation, or code execution has been identified. imtcp and the default imptcp framing modes are not affected.
References
Configurations
Configuration 1 (hide)
|
History
30 Oct 2026, 18:17
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
21 Oct 2026, 21:17
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
20 Oct 2026, 22:19
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
19 Oct 2026, 11:17
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
19 Oct 2026, 05:17
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
12 Oct 2026, 20:17
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
24 Sep 2026, 17:17
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Information
Published : 2026-08-12 21:17
Updated : 2026-10-30 18:17
NVD link : CVE-2026-19654
Mitre link : CVE-2026-19654
CVE.ORG link : CVE-2026-19654
JSON object : View
Products Affected
rsyslog
- rsyslog
redhat
- enterprise_linux
CWE
CWE-125
Out-of-bounds Read
