Repository navigation
build: bump the pkgs locked_commit for the October security fixes - #2637
Merged
Merged
Conversation
Moves the pkgs locked_commit from bd62e6e2 (2026-10-04) to bd1feab5 (pkgs main, 2026-10-26). The guest image this pin materializes picks up the emSign ECC Root CA - G3 distrust (CVE-2026-111943, pkgs#947), musl 1.2.6-r3 (CVE-2026-107891, pkgs#993), and OpenSSL 3.5.9, expat 2.9.0, nghttp2 1.70.0 and pcre2 10.49 (pkgs#933). The guest kernel moves from 6.12.111 to 6.12.114, and libkrun moves to 1.19.7 with libkrunfw 5.6.2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
2 tasks done
Contributor
|
Approved: no findings at Nothing to do. Clobber: none. |
evanspearman
approved these changes
Oct 26, 2026
bryan-minimal
enabled auto-merge
October 26, 2026 20:25
bryan-minimal
added a commit
that referenced
this pull request
Oct 26, 2026
) Moves the pkgs locked_commit from bd62e6e2 (2026-10-04) to bd1feab5 (pkgs main, 2026-10-26), the same pin as the main PR #2637, so 0.7.2 ships the current guest image. That image picks up the emSign ECC Root CA - G3 distrust (CVE-2026-111943, pkgs#947), musl 1.2.6-r3 (CVE-2026-107891, pkgs#993), and OpenSSL 3.5.9, expat 2.9.0, nghttp2 1.70.0 and pcre2 10.49 (pkgs#933). The guest kernel moves from 6.12.111 to 6.12.114, and libkrun moves to 1.19.7 with libkrunfw 5.6.2. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
Moves the pkgs
locked_commitfrom bd62e6e2 (2026-10-04, #1962) to bd1feab5, the pkgsmainHEAD as of 2026-10-26 18:10Z. Both nightlies and stable 0.7.1 still ship the guest image from the 10-04 pkgs commit. That image still trusts the distrusted emSign ECC Root CA - G3, and it carries musl 1.2.6-r2 and OpenSSL 3.5.8.The range is 257 pkgs commits, all first-parent. I generated this changelog from
git log bd62e6e2..bd1feab5in a clean pkgs worktree and from the merged PR bodies. It names 83 CVE, 41 GHSA and 4 RUSTSEC ids.Follow-up bump coming: a further guest-rootfs fix is in flight in pkgs. It moves microvm-rootfs's Alpine pin
brotli-libs1.2.0-r1 → 1.2.1-r0 (CVE-2026-111497; the guest's libcurl links brotli) and adds libcurl 8.23.0-r0. bd1feab5 does not contain it. A second pin bump follows once that pkgs PR merges.What minimal itself ships (guest image, kernel, libkrun)
These are the packages that
release.ymlmaterializes from this pin:minvmd-rootfs=microvm-rootfs,virtio-kernel=virtio-kernel-raw, andlibkrun.ca-certificates-bundle20260611-r0 → 20261020-r0. This drops emSign ECC Root CA - G3.musl,musl-utils1.2.6-r2 → 1.2.6-r3 (regcomp overflows)libcrypto3/libssl33.5.8 → 3.5.9,libexpat2.8.4 → 2.9.0,nghttp2-libs1.69.0 → 1.70.0,pcre210.48 → 10.49just kernel-review 6.12.111 6.12.114reports 7 core-subtree commits. The tool flags two of them, both indrivers/virtio:1eaa83fd94ed"virtio: break and reset virtio devices on device_shutdown()" and8e360ffa4aa6"virtio-mmio: Remove virtqueue list from mmio device". The vsock changes are a vmci leak fix andvsock/virtio: account only unread bytes in read_skb(). There are no changes tovirtio_console. The KVM and macOS lanes on this PR boot the new kernel.emSign / eMudhra distrust across pkgs (CVE-2026-111943)
ca-certificatesrebuilt from the curl 2026-10-20 bundle (#948). Five more packages now declare it: ruby, typst, atuin, gws and skopeo (#957).Other security fixes
>= 3.6.0, < 3.6.5ranges, including CVE-2026-54873 (#816)latest(#879).Toolchain bumps
rust 1.98.1 → 1.99.0 (#810) · go 1.27.1 → 1.27.3 (#935, #945) · python 3.14.7 → 3.14.9 · node 26.12.1 / node-lts 24.22.1 · ocaml 5.5.1 → 5.5.2 (#1100) · cmake 4.4.2 → 4.4.4 · git 2.55.0 → 2.56.0 · new jdk-21, jdk-25 and jdk-27 (Temurin, #897, #898)
Not in this range: harfbuzz 15.0.0 (GHSA-r62p-jr5f-3mjm, pkgs#1001) is still open.
Stdlib compatibility
The newest pkgs stdlib feature in range is
[stdlib] minimum_version = "0.0.18"in pkgsminimal.toml(bd1feab5). minimal's stdlib is 0.0.22 onmainand 0.0.21 on 0.7.1. Everyattrskey used across pkgs (upstream_version,license_spdx,source_provenance,build_cost_multiple,repology_project,binary_from,env_*,redistributable,closed_source,needed_for_internet) already exists in 0.7.1'sattr_classes.ncl. No package declaresrevisionorpatchesyet (#1277).Testing
minimal build,minimal-check×2,aggregate×2,dispatchand CodeRabbit all pass.https://cache.minimal.farm/github.com/gominimal/pkgs/bd1feab5….map.jsonexists.microvm-rootfs,virtio-kernel-raw,libkrunandlibkrunfweach return HTTP 200 for amd64 and arm64, so materialize is a cache fetch, not a rebuild. So do the session packages this file declares.dogfoodandminimal-checkevaluate it with the unstable channel.native-daemon-e2e(scripts/session-e2e.sh) seeds the repo's[upstream]pin into the binary this PR builds.ci-linux-kvmandci-macosboot the new kernel and rootfs.Merge timing: a push to
.minimal/minimal.tomldrops every in-flight coder's worktree (agent-runtime#273). Merge this only in a drain window, with no coder job running (same as #1962).Checklist
BREAKING CHANGE:footer present if this is a breaking change (not breaking)🤖 Generated with Claude Code