Skip to content

[AutoPR- Security] Patch libsoup for CVE-2026-1801, CVE-2026-1761, CVE-2026-1467 [HIGH]#15765

Open
azurelinux-security wants to merge 6 commits intomicrosoft:fasttrack/2.0from
azurelinux-security:azure-autosec/libsoup/2.0/1045497
Open

[AutoPR- Security] Patch libsoup for CVE-2026-1801, CVE-2026-1761, CVE-2026-1467 [HIGH]#15765
azurelinux-security wants to merge 6 commits intomicrosoft:fasttrack/2.0from
azurelinux-security:azure-autosec/libsoup/2.0/1045497

Conversation

@azurelinux-security
Copy link
Contributor

@azurelinux-security azurelinux-security commented Feb 9, 2026

Auto Patch libsoup for CVE-2026-1801, CVE-2026-1761, CVE-2026-1467.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1045497&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 fasttrack/2.0 PRs Destined for Azure Linux 2.0 labels Feb 9, 2026
@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review February 11, 2026 18:51
@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner February 11, 2026 18:51
@Kanishk-Bansal
Copy link
Contributor

/azurepipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jykanase jykanase force-pushed the azure-autosec/libsoup/2.0/1045497 branch from fa73507 to d5426aa Compare February 16, 2026 04:31
Copilot AI added a commit that referenced this pull request Feb 20, 2026
The original patch from PR #15765 was written for libsoup 3.0.4 where
the TRAILERS case uses `buffer, count`. This branch uses libsoup 3.4.4
where the same code already uses `metabuf, sizeof(metabuf)`.

Updated context lines:
- Old: `fstream, buffer, count, blocking,`
- New: `fstream, metabuf, sizeof (metabuf), blocking,`
- Old strncmp: `strncmp (buffer, ...)`
- New strncmp: `strncmp (metabuf, ...)`

Without this fix, the patch would fail to apply during package build.

Co-authored-by: realsdx <30264618+realsdx@users.noreply.github.com>
- fstream, buffer, count, blocking,
+ nread = soup_filter_input_stream_read_until (
+ fstream, buffer, sizeof (metabuf),
+ "\r\n", 2, blocking, TRUE,
Copy link
Contributor

@realsdx realsdx Feb 20, 2026

Choose a reason for hiding this comment

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

Taking buffer as input but it's taking size of the metabuf, this could cause overflow/underflow issues

return nread;

- if (strncmp (buffer, "\r\n", nread) || strncmp (buffer, "\n", nread)) {
+ if (nread == 2 && strncmp (metabuf, "\r\n", nread) == 0) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Same, nread is from the buffer read, but comparing against metabuf

@jykanase jykanase force-pushed the azure-autosec/libsoup/2.0/1045497 branch from d5a7ebc to 5ed5f55 Compare February 24, 2026 05:54
@realsdx
Copy link
Contributor

realsdx commented Feb 24, 2026

/azurepipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@realsdx
Copy link
Contributor

realsdx commented Feb 24, 2026

New Buddy Build

@Kanishk-Bansal Kanishk-Bansal added the CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review label Feb 25, 2026
Copy link
Contributor

@realsdx realsdx left a comment

Choose a reason for hiding this comment

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

  • Patch applies cleanly
Image
  • Security tag exists
  • Release bump & Changelog
  • Buddy Build
  • No new ptest regression (ostree & gpupg2 are unrelated to this PR)
    Signed-off-by: @realsdx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI Backport AutoPR-Security CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review fasttrack/2.0 PRs Destined for Azure Linux 2.0 Packaging security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants