+ "79075eccf01e1b56ed2a0ec504b626cfcaad8aa5": "[backport camel-4.22.x] Pin com.squareup.wire:wire-runtime to 6.4.7 to remediate CVE-2026-45799 (#26252)\n\nPin com.squareup.wire:wire-runtime to 6.4.7 to remediate CVE-2026-45799 (#26243)\n\namazon-kinesis-client pulls software.amazon.glue:schema-registry-serde, which\npins Square Wire at 5.2.0. skipGroup() before Wire 6.3.0 does not reject a\nnegative LENGTH_DELIMITED length, so a crafted payload makes\nProtoAdapter.decode(byte[]) throw an unchecked ArrayIndexOutOfBoundsException\ninstead of the documented IOException. schema-registry-serde 1.1.27 is the\nlatest release and is still on Wire 5.2.0, so the version is managed here.\n\nOnly wire-runtime is bumped. wire-schema, wire-compiler and the Wire code\ngenerators stay at 5.2.0 because the Glue serde binds to\ncom.squareup.wire.schema.internal.parser.ProtoFileElement, whose constructor\ngained a parameter in Wire 5.3.0 - aligning every Wire artifact breaks\nFileDescriptorUtils with a NoSuchMethodError. No Wire release has both the\n9-arg constructor and the CVE fix, so splitting the versions is the only\ncombination that satisfies both.\n\nwire-runtime is an empty Kotlin-Multiplatform metadata artifact; wire-runtime-jvm\ncarries all the classes and is the entry that applies the fix. Both are pinned\nbecause the advisory lists both coordinates.\n\nCamel itself never reaches the vulnerable code: the Glue serde uses Wire only as\na .proto schema-text parser, and the KCL consumer never enables the Glue schema\nregistry. This removes a recurring false positive for downstream consumers.\n\n\n(cherry picked from commit 76a4eef4a6ba912df31bfc1ee3a7936336b419b6)\n\nCo-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>",
0 commit comments