Skip to content

[Snyk] Security upgrade io.undertow:undertow-servlet from 1.4.18.Final to 2.3.21.Final#5256

Open
bogarin wants to merge 1 commit intomasterfrom
snyk-fix-c37a22554abb69c8352ee942957d826d
Open

[Snyk] Security upgrade io.undertow:undertow-servlet from 1.4.18.Final to 2.3.21.Final#5256
bogarin wants to merge 1 commit intomasterfrom
snyk-fix-c37a22554abb69c8352ee942957d826d

Conversation

@bogarin
Copy link
Copy Markdown
Owner

@bogarin bogarin commented Feb 5, 2026

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):

  • undertow/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
high severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-IOUNDERTOW-15166617
  721   io.undertow:undertow-servlet:
1.4.18.Final -> 2.3.21.Final
Major version upgrade 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:

🦉 Allocation of Resources Without Limits or Throttling

Copilot AI review requested due to automatic review settings February 5, 2026 05:05
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This is a Snyk-generated security PR that upgrades the undertow-servlet dependency from version 1.4.18.Final to 2.3.21.Final to fix a high severity vulnerability (Allocation of Resources Without Limits or Throttling, CVSS score 721). This represents a major version upgrade from Undertow 1.x to 2.x.

Changes:

  • Upgrade undertow-servlet dependency from 1.4.18.Final to 2.3.21.Final in pom.xml

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread undertow/pom.xml

<properties>
<undertow-servlet.version>1.4.18.Final</undertow-servlet.version>
<undertow-servlet.version>2.3.21.Final</undertow-servlet.version>
Copy link

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

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

This is a major version upgrade from Undertow 1.x to 2.x, which introduces breaking changes. Key concerns:

  1. Java version requirement: Undertow 2.x requires Java 11 as minimum, but the parent pom.xml specifies Java 1.8 (line 1454 in pom.xml). This upgrade will likely cause compilation failures.

  2. Security API changes: The code in SecureServer.java and CustomIdentityManager.java uses Undertow's security APIs (IdentityManager, AuthenticationMechanism, SecurityContext), which have undergone significant changes between versions 1.x and 2.x. These may require code modifications.

  3. WebSocket API changes: SocketServer.java uses WebSocket APIs that may have changed in the major version upgrade.

  4. No test coverage: There are no test files to verify that the application still works correctly after the upgrade.

  5. Historical context: The undertow module is currently commented out in the parent pom.xml (line 716) due to build issues since 2019, suggesting this module may not be actively maintained.

Before merging this security fix, the code should be tested to ensure it compiles and runs correctly with Undertow 2.3.21.Final. Consider reviewing the Undertow migration guide and updating any deprecated or changed APIs.

Copilot uses AI. Check for mistakes.
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.

3 participants