Skip to content

Conversation

@azurelinux-security
Copy link
Contributor

@azurelinux-security azurelinux-security commented Sep 29, 2025

Auto Patch python-pip for CVE-2025-8869.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner-chatbot/_build/results?buildId=940384&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?

Change Log
Does this affect the toolchain?

YES/NO

Associated issues
  • N/A
Links to CVEs
Test Methodology

@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Sep 29, 2025
@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review September 29, 2025 06:38
@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner September 29, 2025 06:38
@bhagyapathak
Copy link
Contributor

bhagyapathak commented Sep 29, 2025

Full Build [Successful]

@Kanishk-Bansal
Copy link
Contributor

Upstream Reference Link - pypa/pip#13550

Copy link
Contributor

@bhagyapathak bhagyapathak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bhagyapathak bhagyapathak added the ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review label Sep 30, 2025
Copy link
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Patch Analysis (the patch applies cleanly)

image
  • Buddy Build & Full Build
  • Toolchain manifest bump 
  • patch applied during the build (check rpm.log)
  • patch include an upstream reference
  • PR has security tag

Copy link
Contributor

@kgodara912 kgodara912 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As such patch looks ok when seen in diff mode. Full build as it is a toolchain package.

Copy link
Contributor

@kgodara912 kgodara912 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Full build is successful except nodejs in AMD64-GoldenContainerTests-DEV which also passed on re-run. This test has some history of inconsistency. LGTM.

@kgodara912 kgodara912 merged commit fbb2526 into microsoft:3.0-dev Oct 16, 2025
17 checks passed
jykanase pushed a commit to jykanase/azurelinux that referenced this pull request Oct 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 AutoPR-Security Packaging ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants