Skip to content

fix(deps): update dependency org.apache.logging.log4j:log4j-1.2-api to v2.25.4 [security] - #370

Merged
mgaffigan merged 1 commit into
mainfrom
renovate/maven-org.apache.logging.log4j-log4j-1.2-api-vulnerability
Jul 24, 2026
Merged

fix(deps): update dependency org.apache.logging.log4j:log4j-1.2-api to v2.25.4 [security]#370
mgaffigan merged 1 commit into
mainfrom
renovate/maven-org.apache.logging.log4j-log4j-1.2-api-vulnerability

Conversation

@renovate

@renovaterenovateBot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeConfidence
org.apache.logging.log4j:log4j-1.2-api (source)2.25.32.25.4ageconfidence

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

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


Configuration

📅 Schedule: (in timezone America/New_York)

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

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

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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


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

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

@renovaterenovateBot added the dependencies Dependency updates label Jul 24, 2026
@renovate
renovateBot requested a review from a teamJuly 24, 2026 13:09
@renovaterenovateBot added java Java / Gradle dependencies dependencies Dependency updates labels Jul 24, 2026
@renovate
renovateBot requested review from gibson9583 and kayyagariJuly 24, 2026 13:09
@renovaterenovateBot added the java Java / Gradle dependencies label Jul 24, 2026
@github-actions

Copy link
Copy Markdown

Test Results

654 tests ±0 654 ✅ ±0 3m 37s ⏱️ + 1m 1s
108 suites ±0 0 💤 ±0 
108 files ±0 0 ❌ ±0 

Results for commit 9809ccc. ± Comparison against base commit e72e766.

@mgaffigan
mgaffiganforce-pushed the renovate/maven-org.apache.logging.log4j-log4j-1.2-api-vulnerability branch from 9809ccc to 9bb28a7CompareJuly 24, 2026 23:02
@mgaffigan
mgaffigan merged commit b73bcb6 into mainJul 24, 2026
3 checks passed
@mgaffigan
mgaffigan deleted the renovate/maven-org.apache.logging.log4j-log4j-1.2-api-vulnerability branch July 24, 2026 23:03
@mgaffiganmgaffigan mentioned this pull request Jul 25, 2026
@tonygermanotonygermano added this to the Next Release milestone Jul 31, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesDependency updatesjavaJava / Gradle dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@jonbartels@mgaffigan@NicoPiel@tonygermano