Repository navigation
fix(backend): Quarkus 3.40 LTS, so netty-handler leaves CVE-2026-75595 - #559
Merged
Merged
Conversation
The v1.33.0 release gate failed the kates JVM image on CVE-2026-75595 (netty-handler 4.1.130, CRITICAL): the .trivyignore.yaml entry for it expired on 2026-10-30, and no Quarkus 3.20.x patch moves Netty. Quarkus 3.20.6 -> 3.40.1.1 (#284). Its BOM ships Netty 4.1.139 with the matching brotli4j and tcnative, so the native image builds again with no OpenSSL substitution errors, and kafka-clients 4.2.1. - pom: the kafka-clients and Netty codec overrides go, the BOM is newer; lz4-java stays (BOM 1.11.4 < 1.12.1). quarkus update renamed quarkus-junit5 -> quarkus-junit, the Testcontainers 2 modules, and set surefire/failsafe argLine. - Dockerfile.native: Mandrel builder jdk-21 -> jdk-25; 3.40 refuses 23.1. - Config: database.generation -> schema-management.strategy, and log.console.json -> log.console.json.enabled. - Tests: Kafka 4 dropped MockProducer(boolean, Serializer, Serializer); the four-argument constructor with a null partitioner is the same. - .trivyignore.yaml: the CVE-2026-75595 entry is removed. - MCP caveat refs re-pointed: application.properties lost three lines. - appendix D: Quarkus 3.40.1.1. Verified locally: mvnw verify (1768 unit, 93 IT, 0 failures), native and JVM images built from the real Dockerfiles, scripts/native-smoke-test.sh passes on both, Trivy 0.67.2 with the gate's flags finds no CRITICAL in either, spotless, TestMCPCaveatRefAnchors, gen-version-matrix --check.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v1.33.0 release run (41062193181) failed Kates image / Verify Published Images (jvm) on CVE-2026-75595 (netty-handler 4.1.130, CRITICAL). The
.trivyignore.yamlentry expired on 2026-10-30, and no Quarkus 3.20.x patch moves Netty. This is the upgrade #284 tracks.Quarkus 3.20.6 → 3.40.1.1: Netty 4.1.139 (with matching brotli4j/tcnative, so the native image builds with no OpenSSL errors), kafka-clients 4.2.1, Flyway 12.
quarkus-junit,testcontainers-postgresql/-kafka, surefire/failsafeargLinequarkus updaterecipesDockerfile.native: Mandreljdk-21→jdk-25schema-management.strategy,log.console.json.enabledMockProducer(autoComplete, null, ser, ser).trivyignore.yamlentry removedVerified locally
./mvnw verify: 1768 unit + 93 IT, 0 failures, no unrecognized config keysscripts/native-smoke-test.shpasses on bothCRITICAL, ignore-unfixed), empty ignore file: 0 on both imagesTestMCPCaveatRefAnchors,gen-version-matrix.sh --checkNot done from #284: a baseline run on each side of the upgrade (load generator moves from Kafka clients 3.9.2 to 4.2.1); needs a live cluster. Refs #284.
Not in scope: Kafka 4 deprecations of
listConsumerGroups/ConsumerGroupListing(still compile); guava 33.6.0 HIGH CVE-2026-102554 (release gate is CRITICAL-only).Connect image fix for the same CVE: #558.