Apache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility
Published 10 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected org.apache.logging.log4j:log4j-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.21.0 <2.25.4
- Fixed in
- 2.25.4
mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.25.4 -DforceVersion=true- Affected
- >=3.0.0-beta1 <=3.0.0-beta3
- Fixed in
- No fix released
Details
Apache Log4j Core's `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
newLineEscapeattribute 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
useTlsMessageFormatattribute 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.
Is GHSA-445c-vh5m-36rj in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.logging.log4j:log4j-core, and gives you the command that fixes it.
More advisories for org.apache.logging.log4j:log4j-core
- MediumCVE-2026-34479Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters · 10 Apr 2026
- MediumCVE-2026-34480Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters · 10 Apr 2026
- MediumCVE-2026-34477Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration · 10 Apr 2026
- MediumCVE-2025-68161Apache Log4j does not verify the TLS hostname in its Socket Appender · 18 Dec 2025
- HighCVE-2023-26464Apache Log4j 1.x (EOL) allows Denial of Service (DoS) · 10 Mar 2023
- MediumCVE-2021-44832Improper Input Validation and Injection in Apache Log4j2 · 4 Jan 2022
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-34478
- Linkgithub.com/apache/logging-log4j2/pull/4074
- Packagegithub.com/apache/logging-log4j2
- Linklists.apache.org/thread/3k1clr2l6vkdnl4cbhjrnt1nyjvb5gwt
- Linklogging.apache.org/cyclonedx/vdr.xml
- Linklogging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout
- Linklogging.apache.org/security.html#CVE-2026-34478
- Linkwww.openwall.com/lists/oss-security/2026/04/10/7
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.