Skip to content

Conversation

@m1a2st
Copy link
Collaborator

@m1a2st m1a2st commented Jan 6, 2026

Updated lo4j2 version to 2.25.3 to prevent CVE. FYI:
https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-core

CVE LINK : https://nvd.nist.gov/vuln/detail/CVE-2025-68161

Reviewers: Chia-Ping Tsai [email protected]

@m1a2st m1a2st force-pushed the KAFKA-20038-4.1 branch 4 times, most recently from f51ab5e to f61bab2 Compare January 6, 2026 12:36
@chia7712 chia7712 changed the title KAFKA-20038 [CVE-2025-68161] [log4j-core] [2.17.1][Kafka] (4.1) KAFKA-20038 Upgrade Log4j to 2.25.3 to fix CVE-2025-68161 Jan 7, 2026

// visible for testing
@SuppressWarnings("deprecation")
Map<String, org.apache.logging.log4j.core.Logger> currentLoggers() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The deprecation warning is annoying. Since getLoggers has superseded getLoggerRegistry, could we make this switch?

@chia7712
Copy link
Member

chia7712 commented Jan 7, 2026

the flaky testCloseWithZeroTimeoutFromCallerThread is unrelated to this patch

@chia7712 chia7712 merged commit 25e5b26 into apache:4.1 Jan 7, 2026
16 of 18 checks passed
@chia7712
Copy link
Member

chia7712 commented Jan 7, 2026

@m1a2st could you open a PR for branch 4.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants