fix(deps): bump netty 4.2.17 & logback 1.5.34 to clear report-fatjar CVEs - #20
Merged
saurabh-prakash merged 1 commit intoAug 19, 2026
Conversation
…CVEs The karate-reports fatjar (com.lambdatest:karate-reports, built from the karate-core shaded jar) bundles vulnerable transitive deps flagged by the hyperexecute-job-artefacts image vulnerability scan: netty-codec-http 4.2.16.Final -> CVE-2026-59903 (medium, CVSS 6.5) logback-core 1.5.25 -> CVE-2026-10532, CVE-2026-9828 (low) The fatjar profile shades *:* without relocation, so these land in the published jar under their original coordinates and the scanner sees them. Bump the netty-bom pin to 4.2.17.Final and logback-classic to 1.5.34 (1.5.34 covers both logback advisories; 1.5.33 fixes only CVE-2026-9828). slf4j-api and jcl-over-slf4j move 2.0.12 -> 2.0.17 alongside them: both carry a "this is tied to logback-classic" comment, and 2.0.17 is what logback 1.5.34 is built and tested against. Bump lt.patch.version 2 -> 3 so lt-reports-cd republishes as 1.5.3.3. Downstream: hyperexecute-job-artefacts must bump KARATE_REPORTS_VERSION 1.5.3.2 -> 1.5.3.3 after this publishes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
saurabh-prakash
approved these changes
Aug 19, 2026
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
2 participants
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.
What
Bumps the
karate-coredependency pins that feed the publishedcom.lambdatest:karate-reportsfatjar:io.netty:netty-bomnetty-codec-http, medium, CVSS 6.5)ch.qos.logback:logback-classiclogback-core, low)org.slf4j:slf4j-api,org.slf4j:jcl-over-slf4jthis is tied to logback-classiccomment); 2.0.17 is what logback 1.5.34 is built againstlt.patch.version1.5.3.3Why
The
hyperexecute-job-artefactsimage vulnerability scan flags these three CVEs. They come from this fatjar: thefatjarprofile shades*:*without relocation, so netty and logback land in the published jar under their original coordinates and the scanner resolves them there.1.5.34 rather than 1.5.33 for logback — 1.5.33 fixes only CVE-2026-9828; CVE-2026-10532 needs 1.5.34.
Follow-up
Once
lt-reports-cdpublishes1.5.3.3,hyperexecute-job-artefactsbumpsKARATE_REPORTS_VERSION1.5.3.2->1.5.3.3inDockerfileandDockerfileSecure.Testing
Pom-only change; no source touched. Relying on
lt-reports-cito build the fatjar — I have no JDK/Maven available locally to verify the build.🤖 Generated with Claude Code