Patch doxygen for CVE-2025-6140 [Medium]

[suneelyadava]

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?
Patch doxygen for CVE-2025-6140
Patch Modified - No
Astrolabe Patch Reference: gabime/spdlog@1032018

Change Log

• new: SPECS/doxygen/CVE-2025-6140.patch
• modified: SPECS/doxygen/doxygen.spec

Does this affect the toolchain?

NO

Links to CVEs

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

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=863100&view=results

[suneelyadava]

@microsoft-github-policy-service agree company="Microsoft"

[kgodara912]

Buddy build✅

[mayankfz]

Please update the PR summary.

[kgodara912]

Package builds and installs fine with patch applied. LGTM.

[suneelyadava]

Following checks are known failure and not related to this PR. Build pipeline is successful on this PR.

[suneelyadava]

Here are the logs from build pipeline.

[Kanishk-Bansal]

• Buddy Build passed
• patch applied during the build (check rpm.log)
• patch include an upstream reference
• PR has security tag

libmicrohttpd is failure is not related to this PR as it has been failing from a long time.