[AutoPR- Security] Patch vitess for CVE-2026-27969, CVE-2026-27965 [CRITICAL]

[azurelinux-security]

Auto Patch vitess for CVE-2026-27969, CVE-2026-27965.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1057874&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-27969 (CRITICAL), CVE-2026-27965 (HIGH).

Change Log

• CVE-2026-27969
• CVE-2026-27965

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-27969
• https://nvd.nist.gov/vuln/detail/CVE-2026-27965

Test Methodology

• Pipeline build id: Buddy Build URL

[akhila-guruju]

Backported patch details:
CVE-2026-27969:
Added new files go/fileutil/join.go and go/fileutil/join_test.go as fileutil.SafePathJoin is used in the upstream patch. The func SafePathJoin() is defined in go/fileutil/join.go

[Kanishk-Bansal]

Buddy Build

[jslobodzian]

pTest fails, but this should be easy to fix.

time="2026-02-27T13:54:37Z" level=debug msg="go check: unknown command"
time="2026-02-27T13:54:37Z" level=debug msg="Run 'go help' for usage."
time="2026-02-27T13:54:37Z" level=debug msg="====== CHECK DONE vitess. EXIT STATUS 2"

[jslobodzian]

I think we want "go test" not "go check"

[Kanishk-Bansal]

After ptest fix -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1060876&view=results

[Kanishk-Bansal]

Root cause: All 17 test failures are infrastructure-dependent integration tests — none are code bugs. They need MySQL, consul, etcd, zookeeper, timezone data, or the /usr/local/vitess/ directory tree, none of which exist in the RPM build chroot.

Fix: Replaced broad ./path/... patterns with explicit lists of the 47 packages that actually pass as pure unit tests. Every failing sub-package is excluded with documented reasons in the spec comments.

[Kanishk-Bansal]

./go/mysql/... → 14 specific passing sub-packages (excludes root, datetime, endtoend, collations/integration)
./go/vt/mysqlctl/... → 5 specific passing sub-packages (excludes root)
./go/vt/topo/... → 6 specific entries (excludes consultopo, etcd2topo, zk2topo)
./go/vt/vttablet/tabletserver/... → 13 specific entries (excludes vstreamer)
./go/vt/wrangler/... → just ./go/vt/wrangler (excludes testlib)
Removed entirely: go/vt/hook, go/vt/vtgate/evalengine, go/vt/vttablet/tabletmanager, go/vt/zkctl