Skip to content

[Snyk] Security upgrade org.apache.logging.log4j:log4j-core from 2.14.1 to 2.25.3 #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DavidThomas-coder wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade org.apache.logging.log4j:log4j-core from 2.14.1 to 2.25.3 #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion log4shell-goof/log4shell-client/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.14.1</version>
<version>2.25.3</version>
Copy link
Copy Markdown

@cursor cursor Bot Dec 28, 2025

Choose a reason for hiding this comment

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

Log4j version mismatch causes potential runtime failures

This security upgrade only updates log4j-core to 2.25.3 but leaves log4j-api at 2.14.1. Log4j requires both artifacts to be at the same version for binary compatibility. This mismatch will likely cause NoSuchMethodError or NoClassDefFoundError at runtime when log4j-core 2.25.3 attempts to call APIs that don't exist in the older log4j-api 2.14.1. The log4j-api dependency also needs to be upgraded to 2.25.3.

Additional Locations (1)

Fix in Cursor Fix in Web

</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
Expand Down