[
https://issues.apache.org/jira/browse/FLINK-40053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser resolved FLINK-40053.
------------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
Fixed in apache/flink:master e9e0d1a189625fe04ba6175fe9eb6b7a9805bdac
> Log4j 2.26.1 bump
> -----------------
>
> Key: FLINK-40053
> URL: https://issues.apache.org/jira/browse/FLINK-40053
> Project: Flink
> Issue Type: Technical Debt
> Components: Build System
> Reporter: Martijn Visser
> Assignee: Martijn Visser
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> Flink master is on Log4j 2.25.4 (FLINK-39580). Log4j has since released
> 2.26.0 (2026-05-07) and 2.26.1 (2026-07-02). No CVEs are involved; this keeps
> Flink on the latest 2.x line and picks up upstream bug fixes ([2.26.0 release
> notes|https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.26.0],
> [2.26.1 release
> notes|https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.26.1]).
> Besides the version property, the FLINK-39580 bump missed two spots that are
> still on 2.25.3 and should be updated as part of this ticket:
> * the Gradle example in {{docs/content/docs/dev/configuration/overview.md}}
> and its Chinese translation
> * a hardcoded {{log4j.version}} in the {{flink-walkthrough-table-java}}
> archetype, which should use the {{@log4j.version@}} filtered placeholder like
> the other archetypes so it cannot go stale again
--
This message was sent by Atlassian Jira
(v8.20.10#820010)