Repository navigation
fix(security): backport Brotli mitigation to latest - #278
Open
Dima Birenbaum (DimaBir) wants to merge 2 commits into
Open
Dima Birenbaum (DimaBir) wants to merge 2 commits into
Dima Birenbaum (DimaBir) wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The customer-facing latest branch still ships the older NuGet decoder path for CVE-2026-111497. This targeted backport adopts the behavior merged in toolkit PR #24 without promoting the 81 unrelated commits on main.
What
How
Base directly on latest at
d0736c546281e0632667b8e0046ae3d7bba0bf67. The only production change is inside the vendored toolkit'srequestJson. Native dynamic import retains ESM decompressor compatibility on Node 20.13.1. Do not import main's unrelated proxy, runtime or action-layout changes.No package/version/lockfile changes, runtime guard, npm publication, tag creation or release-ref movement are included. Merging into latest would affect consumers of that branch and needs release review; this PR does not authorize an automatic merge.
Tests
Existing baseline limitations
The legacy Mocha suite has 7 pre-existing failures (missing run/sendReport exports and invalid stub cleanup), reproduced before and after this change on Node 20.13.1. Those tests are neither modified nor skipped. This is not an all-green full-suite claim.
The new matrix and restored scan-verification workflow still need hosted CI evidence. Review the baseline failures and complete legitimate Windows/Linux scan/SARIF verification before release/incident closure.