Skip to content

[AutoPR- Security] Patch rubygem-faraday for CVE-2026-25765 [MEDIUM]#16430

Open
azurelinux-security wants to merge 2 commits intomicrosoft:3.0-devfrom
azurelinux-security:azure-autosec/rubygem-faraday/3.0/1085444
Open

[AutoPR- Security] Patch rubygem-faraday for CVE-2026-25765 [MEDIUM]#16430
azurelinux-security wants to merge 2 commits intomicrosoft:3.0-devfrom
azurelinux-security:azure-autosec/rubygem-faraday/3.0/1085444

Conversation

@azurelinux-security
Copy link
Copy Markdown
Contributor

@azurelinux-security azurelinux-security commented Apr 2, 2026

Auto Patch rubygem-faraday for CVE-2026-25765.

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

Replaced manual setup and patch commands with autosetup.
@Kanishk-Bansal
Copy link
Copy Markdown
Contributor

Buddy Build

Copy link
Copy Markdown
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 (Core Security fix logic matches upstream, minor changes done by AI)

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

@Kanishk-Bansal Kanishk-Bansal added the ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review label Apr 7, 2026
Copy link
Copy Markdown
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.

Please fix the incorrectly placed the end statement. Also, please ensure to check the backport as well for proper functionality as the upstream reference was raised against different version.

+ expect(uri.path).to eq('/safe/path')
+ end
+ end
end
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The AI has incorrectly misplaced the end, actually this end should be above the newly added block, context 'with protocol-relative URL (GHSA-33mh-2634-fwr2)' do as done in upstream patch.

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.

3 participants