Skip to content

Force brotli to 1.2.1 - #6640

Merged
JohnMcPMS merged 1 commit into
microsoft:masterfrom
JohnMcPMS:brotli
Oct 30, 2026
Merged

JohnMcPMS merged 1 commit into
microsoft:masterfrom
JohnMcPMS:brotli

Conversation

@JohnMcPMS

@JohnMcPMS JohnMcPMS commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

📖 Description

Force brotli (used by cpprestsdk) to 1.2.1 for https://nvd.nist.gov/vuln/detail/cve-2026-111497

This only affects the Store by default, and with certificate pinning happening before any HTTP protocol transfer, it should be a non-issue for most (assuming that the Store endpoints are not compromised of course, but that is a MUCH larger issue if it happens).

Beyond that, when you add a custom REST source you are placing a large amount of trust in the other party as any install or update runs effectively arbitrary code. This vulnerability could let that REST source potentially run arbitrary code because you contacted it at all. You should never add a source that you don't trust.

Microsoft Reviewers: Open in CodeFlow

@JohnMcPMS
JohnMcPMS requested a review from a team as a code owner October 30, 2026 17:47
@JohnMcPMS
JohnMcPMS merged commit 6c37079 into microsoft:master Oct 30, 2026
9 checks passed
@JohnMcPMS
JohnMcPMS deleted the brotli branch October 30, 2026 21:36
JohnMcPMS added a commit that referenced this pull request Oct 30, 2026
## 📖 Description
CP of  #6640 

Force brotli (used by cpprestsdk) to 1.2.1 for
https://nvd.nist.gov/vuln/detail/cve-2026-111497

This only affects the Store by default, and with certificate pinning
happening before any HTTP protocol transfer, it should be a non-issue
for most (assuming that the Store endpoints are not compromised of
course, but that is a ***MUCH*** larger issue if it happens).

Beyond that, when you add a custom REST source you are placing a large
amount of trust in the other party as any install or update runs
effectively arbitrary code. This vulnerability could let that REST
source potentially run arbitrary code because you contacted it at all.
You should never add a source that you don't trust.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants