CVE-2026-34478

Apache Log4j Core's Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly: * The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output. * The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping. Users of the SyslogAppender are not affected, as its configuration attributes were not modified. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.

Apache Log4j Core's [`Rfc5424Layout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout), in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly: * The `newLineEscape` attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output. * The `useTlsMessageFormat` attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping. Users of the `SyslogAppender` are not affected, as its configuration attributes were not modified. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.

Apache Log4j Core's [`Rfc5424Layout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout), in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly: * The `newLineEscape` attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output. * The `useTlsMessageFormat` attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping. Users of the `SyslogAppender` are not affected, as its configuration attributes were not modified. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.

El Rfc5424Layout de Apache Log4j Core https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , en las versiones 2.21.0 a 2.25.3, es vulnerable a la inyección de registros a través de secuencias CRLF debido a cambios de nombre no documentados de atributos de configuración relevantes para la seguridad. Dos problemas distintos afectan a los usuarios de servicios syslog basados en flujo que configuran Rfc5424Layout directamente: * El atributo newLineEscape fue renombrado silenciosamente, lo que provocó que el escape de nueva línea dejara de funcionar para los usuarios de tramas TCP (RFC 6587), exponiéndolos a la inyección de CRLF en la salida de registros. * El atributo useTlsMessageFormat fue renombrado silenciosamente, lo que provocó que los usuarios de tramas TLS (RFC 5425) fueran degradados silenciosamente a TCP sin tramas (RFC 6587), sin escape de nueva línea. Los usuarios del SyslogAppender no se ven afectados, ya que sus atributos de configuración no fueron modificados. Se aconseja a los usuarios actualizar a Apache Log4j Core 2.25.4, que corrige este problema.