fix(deps): update log4j.version to v2.25.4 [security]

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
org.apache.logging.log4j:log4j-core (source)	2.25.3 → 2.25.4
org.apache.logging.log4j:log4j-1.2-api (source)	2.25.3 → 2.25.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

CVE-2026-34480 / GHSA-3pxv-7cmr-fjr4

More information

Details

Apache Log4j Core's XmlLayout, in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification, producing invalid XML output whenever a log message or MDC value contains such characters.

The impact depends on the StAX implementation in use:

• JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records.
• Alternative StAX implementations (e.g., Woodstox, a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger.

Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: 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

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-34480
• https://github.com/apache/logging-log4j2/pull/4077
• https://lists.apache.org/thread/5x0hcnng0chhghp6jgjdp3qmbbhfjzhb
• https://logging.apache.org/cyclonedx/vdr.xml
• https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout
• https://logging.apache.org/security.html#CVE-2026-34480
• http://www.openwall.com/lists/oss-security/2026/04/10/9
• https://github.com/advisories/GHSA-3pxv-7cmr-fjr4

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

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

CVE-2026-34478 / GHSA-445c-vh5m-36rj

More information

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 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.

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: 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

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-34478
• https://github.com/apache/logging-log4j2/pull/4074
• https://lists.apache.org/thread/3k1clr2l6vkdnl4cbhjrnt1nyjvb5gwt
• https://logging.apache.org/cyclonedx/vdr.xml
• https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout
• https://logging.apache.org/security.html#CVE-2026-34478
• http://www.openwall.com/lists/oss-security/2026/04/10/7
• https://github.com/advisories/GHSA-445c-vh5m-36rj

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Apache Log4j Core: verifyHostName attribute silently ignored in TLS configuration

CVE-2026-34477 / GHSA-6hg6-v5c8-fphq

More information

Details

The fix for CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the log4j2.sslVerifyHostName system property, but not when configured through the verifyHostName attribute of the <Ssl> element.

Although the verifyHostName configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value.

A network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met:

• An SMTP, Socket, or Syslog appender is in use.
• TLS is configured via a nested element.
• The attacker can present a certificate issued by a CA trusted by the appender's configured trust store, or by the default Java trust store if none is configured.

This issue does not affect users of the HTTP appender, which uses a separate verifyHostname attribute that was not subject to this bug and verifies host names by default.

Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.

Severity

• CVSS Score: 6.3 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-34477
• https://github.com/apache/logging-log4j2/pull/4075
• https://lists.apache.org/thread/lkx8cl46t2bvkcwfcb2pd43ygc097lq4
• https://logging.apache.org/cyclonedx/vdr.xml
• https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName
• https://logging.apache.org/security.html#CVE-2026-34477
• https://github.com/advisories/GHSA-6hg6-v5c8-fphq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters

CVE-2026-34479 / GHSA-h383-gmxw-35v2

More information

Details

The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.

Two groups of users are affected:

• Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file.
• Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class.

Users are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue.

[!NOTE]
The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the
Log4j 1 to Log4j 2 migration guide, and specifically the section on eliminating reliance on the bridge.

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: 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

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-34479
• https://github.com/apache/logging-log4j2/pull/4078
• https://lists.apache.org/thread/gd0hp6mj17rn3kj279vgy4p7kd4zz5on
• https://logging.apache.org/cyclonedx/vdr.xml
• https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html
• https://logging.apache.org/security.html#CVE-2026-34479
• http://www.openwall.com/lists/oss-security/2026/04/10/8
• https://github.com/advisories/GHSA-h383-gmxw-35v2

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.