[Snyk] Security upgrade org.wildfly.arquillian:wildfly-arquillian-container-managed from 3.0.1.Final to 5.1.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):

• testsuite/integration-arquillian/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Improper Validation of Syntactic Correctness of Input SNYK-JAVA-IOUNDERTOW-14908846	161	org.wildfly.arquillian:wildfly-arquillian-container-managed: 3.0.1.Final -> 5.1.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:

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

---

CodeAnt-AI Description

Upgrade wildfly-arquillian-container to 5.1.0.Final to fix Undertow input-validation vulnerability

What Changed

• The integration-arquillian test suite now uses org.wildfly.arquillian:wildfly-arquillian-container 5.1.0.Final instead of 3.0.1.Final
• This upgrade resolves a known Undertow input-validation vulnerability (SNYK-JAVA-IOUNDERTOW-14908846) in the test dependencies
• No functional changes to production behavior; change affects test/integration runtime only

Impact

✅ Fewer security vulnerabilities in test dependencies
✅ Safer integration test execution
✅ Reduced risk from Undertow input-validation exploit

💡 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   ❇️ 2 lines of code   🛠️ using Opengrep

Last updated by commit 6802c28 at 2026-01-16 14:58:35 UTC.

[codeant-ai]

Sequence Diagram

The PR updates the arquillian WildFly container version in the integration-arquillian pom from 3.0.1.Final to 5.1.0.Final to address a reported Undertow validation vulnerability; diagram shows the minimal change and its effect on the build/vulnerability resolution.

sequenceDiagram
    participant Snyk
    participant Repository
    participant MavenBuild
    participant VulnerabilityDB

    Snyk->>Repository: Open PR updating pom.xml property arquillian-wildfly-container.version 3.0.1.Final -> 5.1.0.Final
    Repository-->>MavenBuild: Use updated pom on next build
    MavenBuild->>VulnerabilityDB: Resolve dependencies (wildfly-arquillian-container 5.1.0.Final)
    VulnerabilityDB-->>MavenBuild: No longer reports SNYK-JAVA-IOUNDERTOW-14908846
    MavenBuild-->>Repository: Build/tests continue with upgraded container

Loading

---

Generated by CodeAnt AI

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​eslint-config-prettier@​9.1.0
	npm/​vite-plugin-checker@​0.8.0
	npm/​es6-promise@​4.2.8
	npm/​file-saver@​2.0.5
	npm/​file-selector@​0.6.0
	npm/​eslint-plugin-react@​7.36.1
	npm/​eslint-plugin-lodash@​8.0.0
	npm/​flat@​6.0.1
	npm/​eslint-plugin-mocha@​10.5.0
	npm/​eslint@​9.10.0
	npm/​eslint-plugin-cypress@​3.5.0
	npm/​eslint-plugin-playwright@​1.6.2
	npm/​eslint-plugin-react-hooks@​4.6.2
	npm/​eslint-plugin-prettier@​5.2.1

View full report

[codeant-ai]

Nitpicks 🔍

🔒 No security issues identified

⚡ Recommended areas for review Transitive dependency conflicts Upgrading the WildFly Arquillian container may pull different transitive dependencies (undertow, xnio, jakarta vs javax artifacts). Check for Jakarta namespace vs Javax clashes and ensure no older/duplicate versions are introduced into the test classpath. Compatibility This is a major-version bump of the WildFly Arquillian container property. Verify that Arquillian Core (and other plugins/BOMs used in this POM) are compatible with 5.1.0.Final. A mismatch can break deployment/test lifecycle, SPI usage, or Arquillian extensions. CI / test breakage risk Tests (especially integration tests and Docker-based profiles) may fail due to container behaviour changes. Run full integration suite on CI and validate test profiles (db-*, migration profiles) after the upgrade.

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • Keycloak Operator CI
  • Automatic Dependency Submission (Maven)
  • Keycloak CI
  • Automatic Dependency Submission (Maven)
  • Keycloak Documentation
  • Keycloak JavaScript CI
  • CodeQL
  • Keycloak Operator CI
  • Keycloak CI

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #538 at branch `snyk-fix-d5380a781d8323b9e77852ba3d978e56`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}