[AutoPR- Security] Patch fluent-bit for CVE-2025-63657 [HIGH]

[azurelinux-security]

Auto Patch fluent-bit for CVE-2025-63657.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093411&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 fluent-bit for CVE-2025-63657 (HIGH).

Change Log

• CVE-2025-63657

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

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

Test Methodology

• Pipeline build id: Buddy Build URL

[v-aaditya]

CVE-2025-63657

1. The CVE does affect our version 1.4.0 of monkey package in fluent-bit. The affected versions are < 1.8.5 and the affected code is also present in the fluent-bit source and is being built while compilation.
2. The developer has stated that this CVE along with few others should not be treated as distinct security vulnerability and hence the fix includes other CVE fixes as well.
   Reference -
   • Potential vulnerabilities · Issue #426 · monkey/monkey
   • PR #434 fixes this CVE along with many others.
3. Upstream patch has patched the affected code in mk_server/mk_mimetype.c but it is not clear if this is the only change which corresponds to this CVE, as CVE specific changes are not clearly mentioned by the developer.
4. The AI patch also contain many other changes as the upstream PR/patch includes changes for other CVEs as well.
5. The Buddy build has failed due to compilation error, as the AI patch has included changes in other files which does not correspond to this CVE. AI patch has included some part of upstream patch which fixes the affected code for other CVE which is not present in our version and therefore the compilation error.

Final analysis: The AI patch is not correct as it includes other changes as well and these changes correspond to other CVEs. After analyzing the CVE and affected source for this CVE, I believe, only the changes made in mk_server/mk_mimetype.c are needed, rest of the changes can be ignored.