Repository navigation
fix(image): patch brotli decoder (CVE-2026-111497) in sandbox, bump t… - #1617
Merged
Merged
Conversation
…ag 1.3.0 -> 1.3.1 kali-rolling still ships libbrotli 1.2.0-4; node, curl and python3 in the sandbox all load the shared libbrotlidec, so a malicious Content-Encoding: br response would hit the vulnerable decoder. Install Debian's fixed 1.2.0-4.1 packages over Kali's and fail the build if the version is not applied.
Contributor
 [Medium impact] The PR appears safe to merge; no actionable defects were found. SummaryPatches the sandbox’s Brotli packages and switches the default image to
No actionable issues were found. The container build was not run. Reviews (1) · Last reviewed commit: "fix(image): patch brotli decoder (CVE-20..." · Reviewed by Greptile |
samirhvbr
added a commit
to samirhvbr/strix
that referenced
this pull request
Oct 29, 2026
…box image delivery blocker Second pass over the review branch, with both remotes fetched. Upstream main did not move (still 6b7ae2e, the synchronized base), so no code checkpoint advances. Known items: all 530 upstream ledger records and the 44 fork PRs were compared with the live API on state, updated date and head SHA. Only usestrix#1393 changed (rebased onto 6b7ae2e with four commits of its own); it is re-reviewed in depth and stays deferred, with the reasons recorded. Open inventory is unchanged at 320 PRs + 203 issues. Discovery: the 48-hour-overlap update query returned 29 items. Four closed items were not in the ledger and now are: PRs usestrix#1616, usestrix#1617 and usestrix#1603, merged upstream and already ancestors of the branch through the base synchronization, and issue usestrix#1529, a usage question. The ledger has 574 records; coverage totals are recomputed from it. Version and releases rechecked and unchanged: 1.2.43 equals the tag, the Latest Release and remote master; upstream's latest release is still v1.7.0. New delivery blocker: the synchronized source defaults to ghcr.io/usestrix/strix-sandbox:1.3.1, which is not published (manifest 404; 1.3.0 answers 200 as the control). master pins the published 1.3.0. Recorded in release-audit.json, the checkpoints, the round report, the continuity guide and version.md. No tag, release, mirror or master change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TavwVMH7PvrD68JTDfd6Hb
This was referenced Oct 30, 2026
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.
…ag 1.3.0 -> 1.3.1
kali-rolling still ships libbrotli 1.2.0-4; node, curl and python3 in the sandbox all load the shared libbrotlidec, so a malicious Content-Encoding: br response would hit the vulnerable decoder. Install Debian's fixed 1.2.0-4.1 packages over Kali's and fail the build if the version is not applied.