Skip to content

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

Open
DavidThomas-coder wants to merge 1 commit intomainfrom
snyk-fix-ac6de3b4ea61bd12b0a6507a5aa6fda4
Open

[Snyk] Security upgrade org.apache.logging.log4j:log4j-core from 2.7 to 2.25.3#19
DavidThomas-coder wants to merge 1 commit intomainfrom
snyk-fix-ac6de3b4ea61bd12b0a6507a5aa6fda4

Conversation

@DavidThomas-coder
Copy link
Copy Markdown
Owner

@DavidThomas-coder DavidThomas-coder commented Dec 23, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • todolist-goof/todolist-web-struts/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
medium severity Improper Validation of Certificate with Host Mismatch
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-14532782
  515   org.apache.logging.log4j:log4j-core:
2.7 -> 2.25.3
No Path Found No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


Note

Updates dependency to address security and maintenance concerns.

  • Bumps org.apache.logging.log4j:log4j-core from 2.7 to 2.25.3 in todolist-goof/todolist-web-struts/pom.xml
  • No application code changes; other dependencies (e.g., log4j-api) remain unchanged

Written by Cursor Bugbot for commit 1ec0f13. This will update automatically on new commits. Configure here.

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on January 25

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.7</version>
<version>2.25.3</version>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Log4j version mismatch will cause runtime errors

The log4j-core dependency was upgraded to version 2.25.3 while log4j-api remains at version 2.7. These components must have matching versions to work correctly. This 18-minor-version mismatch will cause NoSuchMethodError or ClassNotFoundException at runtime when the newer log4j-core tries to call methods that don't exist in the older log4j-api. The log4j-api version needs to be upgraded to 2.25.3 as well.

Fix in Cursor Fix in Web

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