Skip to content

Update Tomcat, HttpCore5, Jackson for OWASP CVE remediation#1437

Closed
labkey-willm wants to merge 1 commit into
developfrom
fb_owasp_cves_20260707
Closed

Update Tomcat, HttpCore5, Jackson for OWASP CVE remediation#1437
labkey-willm wants to merge 1 commit into
developfrom
fb_owasp_cves_20260707

Conversation

@labkey-willm

@labkey-willm labkey-willm commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Rationale

LabKey Server's OWASP Dependency Check build is failing on develop with 124 findings, the bulk of them from a handful of vulnerable third-party dependencies. This PR clears the findings that can be resolved by version bumps/forces and suppresses two verified false positives.

Related Pull Requests

Changes

  • Tomcat 11.0.22 -> 11.0.23: CVE-2026-53434 and CVE-2026-55276 (CRITICAL 9.1), plus CVE-2026-53404, CVE-2026-55955, CVE-2026-55956, CVE-2026-50229
  • httpcore5 5.4.2 -> 5.4.3, and a new httpcore5-h2 force at 5.4.3 (previously transitive at 5.3.6): CVE-2026-54399
  • Jackson 2.21.4 -> 2.21.5 (jacksonVersion, jacksonDatabindVersion, jacksonJaxrsBaseVersion): CVE-2026-54515
  • Suppress classic httpcore 4.x for CVE-2026-54399 (the CVE is scoped to HttpComponents Core 5.x; the 4.x line is EOL and unaffected)
  • Suppress Kotlin runtime jars for CVE-2026-53914 (a Kotlin build-cache-metadata deserialization flaw scored 6.7 MEDIUM by JetBrains, not applicable to the shipped stdlib/reflect runtime jars)
  • Update comments to document that apacheTomcatVersion is intentionally held ahead of Spring Boot's managed Tomcat

Not included

  • The two labkey-api-jdbc shaded httpcore5 5.2.4 findings: the vulnerable httpcore5 is shaded inside the published labkey-api-jdbc-3.1.0-all.jar and cannot be overridden via resolutionStrategy. These clear once the release chain lands (labkey-api-java 7.3.0 -> labkey-api-jdbc 3.2.0 -> bump labkeyJdbcVersion here).

Bump Tomcat 11.0.22 -> 11.0.23 (CVE-2026-53434 and CVE-2026-55276 CRITICAL, plus CVE-2026-53404, CVE-2026-55955, CVE-2026-55956, CVE-2026-50229), httpcore5 5.4.2 -> 5.4.3 with a new httpcore5-h2 force at the same version (CVE-2026-54399), and Jackson 2.21.4 -> 2.21.5 (CVE-2026-54515). These clear the corresponding OWASP Dependency Check findings on develop.

Suppress two false positives: classic httpcore 4.x (CVE-2026-54399 is scoped to HttpComponents Core 5.x; the 4.x line is EOL and unaffected) and the Kotlin runtime jars (CVE-2026-53914 is a build-cache-metadata deserialization flaw in Kotlin build tooling, scored 6.7 MEDIUM by JetBrains, not applicable to the shipped stdlib/reflect jars).

The Tomcat pin is intentionally held ahead of Spring Boot's managed Tomcat (SB 4.0.6 -> 11.0.21, 4.0.7 -> 11.0.22, both affected); comments updated so it is not synced back down. ActiveMQ is handled in a companion platform PR, and the two labkey-api-jdbc shaded httpcore5 findings are left until the labkey-api-java -> jdbc release chain lands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant