fix: upgrade Log4j from 2.25.3 to 2.25.4 (CVE-2026-34480)#1637
Open
stephenmcconnachie wants to merge 1 commit into
Open
fix: upgrade Log4j from 2.25.3 to 2.25.4 (CVE-2026-34480)#1637stephenmcconnachie wants to merge 1 commit into
stephenmcconnachie wants to merge 1 commit into
Conversation
Apache Log4j Core 2.25.3 and earlier are vulnerable to CVE-2026-34480 (CVSS 7.5 HIGH): XmlLayout fails to sanitize characters forbidden by the XML 1.0 spec, producing malformed XML or throwing exceptions (depending on StAX implementation), causing silent log event loss. Upgrade to 2.25.4 which sanitises forbidden characters before output. See: https://nvd.nist.gov/vuln/detail/CVE-2026-34480
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades Log4j from
2.25.3to2.25.4to address CVE-2026-34480 (CVSS 3.1: 7.5 HIGH).The vulnerability
Apache Log4j Core's
XmlLayoutfails to sanitize characters forbidden by the XML 1.0 specification. When log messages or MDC values contain these characters:jackson-dataformat-xml) — an exception is thrown during the logging call and the log event is never delivered to its intended appender; it only reaches Log4j's internal status logger, resulting in silent data loss.Fix
Apache released Log4j 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.
Scope of change
Minimal — a single property bump in
droid-parent/pom.xml:All Log4j module references (
log4j-api,log4j-core,log4j-slf4j2-impl) use ${log4j2.version}, so the change propagates correctly to all sub-modules.References