Repository navigation
fix: select patched runtimes for CVE-2026-111497 - #13
Merged
Merged
Conversation
commit: |
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.
Summary
Select patched Bun 1.4.4 in all three workflows and package metadata; pin the publishing job to fixed Node 22.23.4.
Application dependency versions and dependency lockfiles are unchanged.
Evidence
Bun1.4.4 security release, Bun's Brotli fix, and Node's fixed runtime releases.
Verification
Changed JSON/YAML parsed. Local frozen install with lifecycle scripts disabled and full web/server build passed using Bun 1.4.4 and Node 24.22.1. Both GitHub Actions preview checks passed for this head. Dependency lockfile remained unchanged.
Remaining rollout and limits
The published bundle targets Node but does not embed Node. Every CLI consumer must update its own Node/Bun; the outbound RPC fetch paths remain dependent on that runtime.
No exploit probes were run. A runtime selection fix is not production deployment verification. This remains a draft for review; nothing was merged or deployed manually.