[AutoPR- Security] Patch moby-engine for CVE-2026-39882 [MEDIUM]

[azurelinux-security]

Auto Patch moby-engine for CVE-2026-39882.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1095458&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 moby-engine for CVE-2026-39882 (MEDIUM).

Change Log

• CVE-2026-39882

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

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

Test Methodology

• Pipeline build id: Buddy Build URL

[azure-pipelines]

Azure Pipelines:
3 pipeline(s) require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.

[Kanishk-Bansal]

Patch Analysis (Backported - The upstream fix spans 3 exporters (trace/metric/log), but moby-engine v25.0.3 only vendors otlptracehttp which is patched, other files are not present in our source code. Hence not patched by AI)
Fixed the changelog along with this fix.

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

[kgodara912]

Patch update is needed.

[kgodara912]

It seems to be a partial fix. The upstream has two places where io.Copy is replaced with the updated signature, success and Error cases. Downstream also has the same but in switch case instead of handling it with if else. Following is the snippet,

         switch sc := resp.StatusCode; {
         case sc >= 200 && sc <= 299:
             // Success, do not retry.
             // Read the partial success message, if any.
             var respData bytes.Buffer
             if _, err := io.Copy(&respData, http.MaxBytesReader(nil, resp.Body, maxResponseBodySize)); err != nil 
...
         case sc == http.StatusTooManyRequests, sc == http.StatusServiceUnavailable:
             // Retry-able failures.  Drain the body to reuse the connection.
             if _, err := io.Copy(io.Discard, resp.Body); err != nil {
                 otel.Handle(err)
             }
             return newResponseError(resp.Header)

The io.Copy in error case also, we should put the same bound checking even though we are discarding it but read may still consume same high memory.

[Kanishk-Bansal]

Build

[kgodara912]

Patch almost matches with upstream reference except the switch vs if/else and other files not present. Buddy build is successful. LGTM.