[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
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-IOUNDERTOW-15053841	125	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:

🦉 Allocation of Resources Without Limits or Throttling

---

CodeAnt-AI Description

Update test container dependency to remove a high-severity resource-allocation vulnerability

What Changed

• The Arquillian WildFly managed container dependency used by the integration test suite was upgraded from 3.0.1.Final to 5.1.0.Final
• This upgrade removes a high-severity Undertow resource-allocation vulnerability that affected tests run with the managed WildFly container

Impact

✅ Fewer test-suite security vulnerabilities
✅ Lower security risk when running integration tests with the managed container
✅ Faster remediation of a known high-severity vulnerability

💡 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

[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/​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

[amplify-security]

🔍 Amplify code check status:  

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

Last updated by commit 669edc3 at 2026-01-23 10:11:31 UTC.

[codeant-ai]

Nitpicks 🔍

🔒 No security issues identified

⚡ Recommended areas for review Compatibility Risk Bumping arquillian-wildfly-container.version from 3.x to 5.x can introduce breaking changes (API/behaviour or Jakarta vs Javax namespace changes). Verify that tests and any code interacting with WildFly Arquillian containers remain compatible. Dependency/BOM Mismatch The new property may not be aligned with the versions provided by the existing arquillian-bom or other WildFly BOMs. This can lead to transitive version conflicts for org.wildfly.arquillian modules; consider importing a WildFly Arquillian BOM or ensuring all WildFly Arquillian artifacts are managed consistently. Test / CI Impact Changing the container version affects integration tests. Ensure CI runs full integration suite and that any container-specific scripts, configuration or Docker images are compatible with the upgraded container version.

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[zeropath-ai]

✅ No security or compliance issues detected. Reviewed everything up to 669edc3.

Security Overview

• 🔎 Scanned files: 1 changed file(s)
• 🔗 Scan Link: https://zeropath.com/app/repositories/0e111b51-ae74-4faa-8067-84c4c8db1568?scanId=b4693b5c-7d61-481e-b342-1357f3b37785&codeScanTypes=PrScan&tab=issues

Detected Code Changes

Change Type	Relevant files
Configuration changes	► pom.xml     Update Arquillian WildFly container version

[openhands-ai]

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

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

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

@OpenHands please fix the failing actions on PR #544 at branch `snyk-fix-c8f9a28ec8af4916dc2ab2d59f2e24fa`

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

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