You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Closes out the Tier 1 portion of parent epic #72. After #79 landed (13 of the 19 GAVs in the original plan) and the post-#79 state was re-checked, all 19 GAVs from the original Tier 1 plan are either closed or have to be reclassified as Tier 3 (no Java 1.8 fix exists). The 7 derby CVEs are the only remaining open items from the Tier 1 plan.
Closed: 18 of 19. Reclassified: 1 (derby, 7 CVEs).
Reclassifying derby
The original Tier 1 plan said org.apache.derby:derby 10.14.2.0 -> 10.14.2.1 (7 CVEs closed: 1 CRITICAL, 6 HIGH). That fix version does not exist on Maven Central. The actual next Derby release after 10.14.2.0 is 10.15.1.3, and it ships:
module-info.class at the root of the jar (not under META-INF/versions/9/)
Class major version 53 (Java 9 bytecode)
No multi-release jar structure
That is plain Java 9 bytecode, not Java 1.8 compatible — a real Java 8 runtime will throw UnsupportedClassVersionError. Same for 10.15.2.0, 10.16.1.1 (Java 17), and 10.17.1.0 (Java 19). Derby 10.14.2.0 is the last Java 1.8 release.
The 7 derby CVEs are therefore unfixable on the main branch as long as it targets Java 1.8. They join the Tier 3 list ("at the latest Java 1.8 line; no Java 1.8 fix exists") tracked in the parent epic #72.
How the 4 GAVs that were 'deferred' but turned out to be already done
These were already at the plan's fix version (or newer) on main before PR #79 landed — likely from a separate dependency cleanup that wasn't tagged to #72. The re-check after #79 is what surfaced this:
snakeyaml had been bumped to 2.6 (newer than the plan's 1.32/2.0).
jsoup had been bumped to 1.23.1 (the exact plan fix).
jetty-webapp was already on ${jetty.version} = 9.4.58.v20250814 (newer than the plan's 9.4.33).
protobuf-java is transitive from com.google.javascript:closure-compiler:rr2079.1 which ships it at 4.33.2 (newer than the plan's 3.25.5).
Out of scope
Migration of derby to a newer line would require moving the whole project to Java 9+ (or replacing Derby with H2/PostgreSQL embedded). Both are major workstreams, not version bumps.
Summary
Closes out the Tier 1 portion of parent epic #72. After #79 landed (13 of the 19 GAVs in the original plan) and the post-#79 state was re-checked, all 19 GAVs from the original Tier 1 plan are either closed or have to be reclassified as Tier 3 (no Java 1.8 fix exists). The 7 derby CVEs are the only remaining open items from the Tier 1 plan.
Status of the original 19 GAVs
Reclassifying derby belowcom.google.javascript:closure-compiler:rr2079.1)jetty.version)Closed: 18 of 19. Reclassified: 1 (derby, 7 CVEs).
Reclassifying derby
The original Tier 1 plan said
org.apache.derby:derby 10.14.2.0 -> 10.14.2.1(7 CVEs closed: 1 CRITICAL, 6 HIGH). That fix version does not exist on Maven Central. The actual next Derby release after 10.14.2.0 is 10.15.1.3, and it ships:module-info.classat the root of the jar (not underMETA-INF/versions/9/)That is plain Java 9 bytecode, not Java 1.8 compatible — a real Java 8 runtime will throw
UnsupportedClassVersionError. Same for 10.15.2.0, 10.16.1.1 (Java 17), and 10.17.1.0 (Java 19). Derby 10.14.2.0 is the last Java 1.8 release.The 7 derby CVEs are therefore unfixable on the
mainbranch as long as it targets Java 1.8. They join the Tier 3 list ("at the latest Java 1.8 line; no Java 1.8 fix exists") tracked in the parent epic #72.How the 4 GAVs that were 'deferred' but turned out to be already done
These were already at the plan's fix version (or newer) on main before PR #79 landed — likely from a separate dependency cleanup that wasn't tagged to #72. The re-check after #79 is what surfaced this:
${jetty.version}= 9.4.58.v20250814 (newer than the plan's 9.4.33).io.netty:netty-bomimport in chore(deps): tier1 dependency upgrades for Java 1.8 (issue #72, 13 of 19 GAVs) #79 (4.1.136.Final, newer than the plan's 4.1.135).com.google.javascript:closure-compiler:rr2079.1which ships it at 4.33.2 (newer than the plan's 3.25.5).Out of scope
References
docs/ai-generated/tasks/PR#-DependencyVulnerabilityAnalysis/main-vulnerability-report.md