UNCLASSIFIED - NO CUI

chore(findings): opensource/keycloak/keycloak (arm64)

Summary

opensource/keycloak/keycloak (arm64) has 4 new findings discovered during continuous monitoring.

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/keycloak/keycloak&tag=26.1.1-arm64&branch=master

id source severity package impact workaround
CVE-2025-1247 Twistlock CVE High io.quarkus_quarkus-rest-deployment-3.15.3
CVE-2025-1247 Twistlock CVE High io.quarkus_quarkus-rest-3.15.3
GHSA-phg3-gv66-q38x Anchore CVE High quarkus-rest-3.15.3
GHSA-phg3-gv66-q38x Anchore CVE High quarkus-rest-deployment-3.15.3

More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/keycloak/keycloak&tag=26.1.1-arm64&branch=master

Novel Tidelift Findings (Experimental)

opensource/keycloak/keycloak (arm64) has 5 novel Tidelift findings discovered during continuous monitoring.

NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.

id cvss score package impact workaround
CVE-2025-0736 5.5 pkg:maven/org.infinispan/infinispan-core@15.0.11.Final
CVE-2025-1247 8.3 pkg:maven/io.quarkus/quarkus-rest@3.15.3
CVE-2025-1247 8.3 pkg:maven/io.quarkus/quarkus-rest-deployment@3.15.3
CVE-2025-24970 7.5 pkg:maven/io.netty/netty-handler@4.1.115.Final This is a critical vulnerability that can crash your application very easily, just by sending a crafted packet. Upgrade or workaround is highly recommended. First option Disable native TLS support by removing the nettytcnative dependency or explicitly telling Netty not to use native TLS support. This may degrade your applications TLS performance.Second option Change the code fromSslContext context ...SslHandler handler context.newHandler....toSslContext context ...SSLEngine engine context.newEngine....SslHandler handler new SslHandlerengine, ....
CVE-2025-25193 5.5 pkg:maven/io.netty/netty-common@4.1.115.Final This vulnerability can be triggered only when an attacker already has the write access to the filesystem. In addition, an attacker must create the offending file in the filesystem before the application is started. Therefore, Id say the risk is fairly low.

Tasks

Contributor:

  • Provide justifications for findings in the VAT (docs)
  • Apply the StatusVerification label to this issue and wait for feedback

Iron Bank:

  • Review findings and justifications

Note: If the above process is rejected for any reason, the Verification label will be removed and the issue will be sent back to Open. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add the Verification label.

Questions?

Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding.

Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.