[AutoPR- Security] Patch vitess for CVE-2026-55969, CVE-2026-43871 [HIGH]

[azurelinux-security]

Auto Patch vitess for CVE-2026-55969, CVE-2026-43871.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1174627&view=results

CVE-2026-55969 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1174635&view=results
CVE-2026-43871 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1174634&view=results

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

• Auto Patch vitess for CVE-2026-55969 (HIGH), CVE-2026-43871 (HIGH).

Change Log

• CVE-2026-55969
• CVE-2026-43871

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-55969
• https://nvd.nist.gov/vuln/detail/CVE-2026-43871

Test Methodology

• Pipeline build id: Buddy Build URL

[v-aaditya]

CVE-2026-43871

1. The AI patch completely matches with upstream patch.
2. Only go module or file changes are included as other variations are not present.

CVE-2026-55969

1. The changes in files vendor/github.com/uber/jaeger-client-go/thrift/json_protocol.go and vendor/github.com/uber/jaeger-client-go/thrift/protocol_test.go are not included in the patch as they are not present in current thrift source.
2. The AI patch has been modified to match with upstream patch.
3. Modification details -
   1. getMinSerializedSize() function has been added as it is used in upstream fix and was not present in current thrift source. Also upstream has case UUID: return 16; and the backport substitutes case UTF8/UTF16: return 4, because jaeger-client-go vendors a pre-UUID Thrift where UUID doesn't exist as a TType but UTF8/UTF16 do.
   2. The backport drops upstream's standalone if size > 0. math.MaxInt32 guard, to match it with upstream.

Buddy Build has been re-triggered. Kindly note the Buddy Build has failed during "Verify Test Results" phase as ptest has been failing and it is unrelated to this PR as it is a known issue and a PR #16642 is already open for the same.

Peer-review completed by Jyoti Kanase.

[v-aaditya]

Re-triggered Buddy Build after fixing ptest failures and it has passed.
This PR also fixes workitem - https://dev.azure.com/mariner-org/mariner/_workitems/edit/18490
Referred PR - #16642