[Snyk] Security upgrade org.wildfly.core:wildfly-server from 21.1.0.Final to 31.0.0.Final

[ISGA]

User description

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

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-IOUNDERTOW-15166617	124	org.wildfly.core:wildfly-server: 21.1.0.Final -> 31.0.0.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

---

CodeAnt-AI Description

Upgrade WildFly core to 31.0.0.Final to fix a high-severity resource allocation vulnerability

What Changed

• Upgraded the WildFly core dependency to 31.0.0.Final in adapter build profiles, replacing the previous variable-based versions
• Simplified the POM contributors element to a self-closing tag (cosmetic POM cleanup)

Impact

✅ Fixes high-severity resource-allocation vulnerability (IOUNDERTOW-15166617)
✅ Fewer security alerts from dependency scans
✅ Adapter builds now use WildFly 31.0.0.Final

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[amplify-security]

🔍 Amplify code check status:  

⚠️ 0 issues detected in   📄 1 file and   ❇️ 6 lines of code   🛠️ using Opengrep

Last updated by commit 8705efa at 2026-02-08 09:35:46 UTC.

[codeant-ai]

Sequence Diagram

The PR updates pom.xml to bump wildfly.core.version to 31.0.0.Final (in two profiles), replacing the vulnerable wildfly-server 21.1.0.Final. The diagram shows the automated Snyk PR, the repository change, a Maven build resolving the upgraded artifact, and the vulnerability being addressed.

sequenceDiagram
    participant Snyk
    participant Repo
    participant CI
    participant Maven
    participant ArtifactRepo

    Snyk->>Repo: Create PR updating pom.xml (wildfly.core.version -> 31.0.0.Final)
    Repo-->>CI: PR merged / change present
    CI->>Maven: Run build (resolve dependencies)
    Maven->>ArtifactRepo: Fetch org.wildfly.core:wildfly-server:31.0.0.Final
    ArtifactRepo-->>Maven: Return upgraded artifact
    Maven-->>CI: Build succeeds with upgraded dependency (vulnerability mitigated)

Loading

---

Generated by CodeAnt AI

[codeant-ai]

Nitpicks 🔍

🔒 No security issues identified

⚡ Recommended areas for review Version Pinning The PR adds literal WildFly core version pins inside two profiles (<wildfly.core.version>31.0.0.Final</wildfly.core.version>) instead of referencing existing top-level properties. This can cause inconsistency with the central properties (e.g. upstream.wildfly.core.version and eap8.wildfly.core.version) and lead to unpredictable dependency resolution depending on which profile is active. Confirm whether the intent is a global upgrade or a profile-only override and align with the central properties to avoid duplicated version sources.

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[zeropath-ai]

✅ No security or compliance issues detected. Reviewed everything up to 8705efa.

Security Overview

• 🔎 Scanned files: 1 changed file(s)
• 🔗 Scan Link: https://zeropath.com/app/repositories/0e111b51-ae74-4faa-8067-84c4c8db1568?scanId=0d9c1159-0926-4e83-a160-2cc7e9539812&codeScanTypes=PrScan&tab=issues

Detected Code Changes

Change Type	Relevant files
Configuration changes	► pom.xml     Update contributors element     Update wildfly.core.version property for EAP 8 profile     Update wildfly.core.version property for upstream WildFly profile