[High] Patch protobuf for CVE-2025-4565

[akhila-guruju]

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

Patch protobuf for CVE-2025-4565
Patch Modified: Yes

• A new parameter current_depth has been added for the files decoder.py and python_message.py from upstream v29.5 for proper application of patch.
• Apart from upstream patch, a file python_message.py was also backported to fix the build for python-tensorboard
• python/google/protobuf/internal/decoder_test.py is not present in source tarball. So, patch is not applied for that file.
• Some changes in the upstream patch are already included in the source tarball, so they won't appear in the modified patch.

Astrolabe Patch Reference: protocolbuffers/protobuf@17838be .
NIST mentions here https://nvd.nist.gov/vuln/detail/CVE-2025-4565 that it fixes this CVE.

Change Log

• new file: SPECS/protobuf/CVE-2025-4565.patch
• modified: SPECS/protobuf/protobuf.spec

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-4565

Test Methodology

• Local Build
• Patch applies cleanly

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mbykhovtsev-ms]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mbykhovtsev-ms]

Unfortunately it appears the patch is breaking python-tensorboard build. I have checked the logs and the exact change to the decoder.py breaks python-tensorboard build.

[akhila-guruju]

Yes, I attempted to fix it as well. The error encountered for python-tensorboard in pipeline was resolved after modifying the patch (by backporting another file from upstream), but now I am encountering another error. Looking into that.
Modified patch: tensor-CVE-2025-4565.patch

[akhila-guruju]

Updated the patch and waiting for the Buddy Build results

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mbykhovtsev-ms]

Looks like the updated patch is now working fine with python-tensorboard

[CBL-Mariner-Bot]

Auto cherry-pick results:

• 3.0-dev ✅ -> [AUTO-CHERRYPICK] [High] Patch protobuf for CVE-2025-4565 - branch 3.0-dev #14113

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=849770&view=results