Skip to content
Heist/ feed
Back to feed
Medium

Apache Log4j Core: Log injection in Rfc5424Layout due to silent configuration incompatibility

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-34478
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 03:06 UTC · Revision 1

Source evidence

Apache Log4j Core: Log injection in Rfc5424Layout due to silent configuration incompatibility

core-osv · Original source

Published 10 Apr 2026, 15:40 UTC

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.

osv:CVE-2026-34478
Complete source record
{
  "id": "5a6b575aee9b7e237fd0d45b3f890353d7ea118c8d69f93920cd857957d3d402",
  "url": "https://osv.dev/vulnerability/CVE-2026-34478",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Apache Log4j Core: Log injection in Rfc5424Layout due to silent configuration incompatibility",
    "summary": "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.",
    "evidence": "osv:CVE-2026-34478",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2026-34478",
      "aliases": [
        "CVE-2026-34478",
        "GHSA-445c-vh5m-36rj"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/apache/logging-log4j2",
              "type": "GIT",
              "events": [
                {
                  "introduced": "3333493d9a9daabc72d10582c4682538baa93a2a"
                },
                {
                  "fixed": "0628e53b25a33e496b509c40a39f2d7c64f2aa6c"
                },
                {
                  "introduced": "416cd4dcf419b59c88054d2001d34c7fec010560"
                },
                {
                  "last_affected": "28117e55f69892d3454672f9399e53fb7b74a321"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "2.21.0"
                      },
                      {
                        "fixed": "2.25.4"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "cpe": "cpe:2.3:a:apache:log4j:3.0.0:beta1:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "3.0.0-beta1"
                      },
                      {
                        "last_affected": "3.0.0-beta1"
                      }
                    ],
                    "source": "CPE_STRING"
                  },
                  {
                    "cpe": "cpe:2.3:a:apache:log4j:3.0.0:beta2:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "3.0.0-beta2"
                      },
                      {
                        "last_affected": "3.0.0-beta2"
                      }
                    ],
                    "source": "CPE_STRING"
                  },
                  {
                    "cpe": "cpe:2.3:a:apache:log4j:3.0.0:beta3:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "3.0.0-beta3"
                      },
                      {
                        "last_affected": "3.0.0-beta3"
                      }
                    ],
                    "source": "CPE_STRING"
                  }
                ]
              }
            }
          ],
          "versions": [
            "3.0.0-beta1",
            "3.0.0-beta2",
            "3.0.0-beta3"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-34478.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:32.707410497Z",
      "provider": "osv",
      "references": [
        "https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout",
        "https://repo.maven.apache.org/maven2",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34478.json",
        "https://lists.apache.org/thread/3k1clr2l6vkdnl4cbhjrnt1nyjvb5gwt",
        "https://logging.apache.org/cyclonedx/vdr.xml",
        "https://logging.apache.org/security.html#CVE-2026-34478",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-34478",
        "https://github.com/apache/logging-log4j2/pull/4074"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-117",
          "CWE-684"
        ],
        "cna_assigner": "apache",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34478.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-34478",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 499902,
  "published_at": "2026-04-10T15:40:17.713+00:00"
}