Skip to content

Bump java-jwt to 4.6.0 and pin Jackson 2.22.1 to fix CVEs#146

Merged
andy317fe301f8c7 merged 1 commit into
masterfrom
fix/jackson-cve-bump
Jul 23, 2026
Merged

Bump java-jwt to 4.6.0 and pin Jackson 2.22.1 to fix CVEs#146
andy317fe301f8c7 merged 1 commit into
masterfrom
fix/jackson-cve-bump

Conversation

@andy317fe301f8c7

Copy link
Copy Markdown
Contributor

Summary

The transitive Jackson dependency pulled in via com.auth0:java-jwt is flagged with multiple security advisories (HIGH severity in both jackson-databind and jackson-core). The current master (0.11.0) uses java-jwt:4.5.1, which pulls Jackson 2.21.0 — still vulnerable.

This bumps java-jwt to 4.6.0 and pins jackson-bom:2.22.1 so both jackson-core and jackson-databind resolve to the fully patched 2.22.1.

Why the BOM pin is needed

Config Jackson Open advisories (per OSV)
java-jwt:4.5.1 (current master / 0.11.0) 2.21.0 ❌ 12
java-jwt:4.6.0 alone 2.22.0 ❌ 3 (incl. HIGH GHSA-r7wm-3cxj-wff9)
java-jwt:4.6.0 + jackson-bom:2.22.1 2.22.1 ✅ 0

Verification

  • ./gradlew :guardian:dependencies confirms jackson-core and jackson-databind both resolve to 2.22.1.
  • ./gradlew :guardian:test passes (28 tasks).

🤖 Generated with Claude Code

The transitive Jackson pulled in via com.auth0:java-jwt was flagged with
multiple advisories (HIGH severity in jackson-databind and jackson-core).
java-jwt 4.5.1 pulls Jackson 2.21.0 (still vulnerable); 4.6.0 pulls 2.22.0
(still 3 open advisories). Pinning jackson-bom to 2.22.1 resolves all known
CVEs. Verified: jackson-core and jackson-databind both resolve to 2.22.1;
guardian unit tests pass.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@andy317fe301f8c7
andy317fe301f8c7 marked this pull request as ready for review July 23, 2026 16:03
@andy317fe301f8c7
andy317fe301f8c7 merged commit c994035 into master Jul 23, 2026
3 checks passed
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.

2 participants