The one you can feel is in Files. Extracting a zip archive could write files outside the folder you
extracted into: the archive creates a symlink inside the extraction directory, and a later entry is
"under" that symlink, so it lands anywhere the archive chooses. Files now refuses such entries
(cosmic-patches/cosmic-files/0002).
Everything else in this release is a dependency pass. COSMIC's lockfiles take the semver-compatible
fix for every crate OSV flags: quinn-proto 0.11.19, rustls 0.23.46, rustls-webpki 0.103.16, plus
webpki-roots, time, tokio, bytes, serde_with and zstd, across 12 components. Three fixes, zip,
quick-xml and lru, need new major versions and upstream code changes, so they stay open. Go 1.27.2
carries two go1.27 release-branch fixes as patches: crypto/x509 distrusts a set of compromised
intermediates (CVE-2026-111943), and an HTTP/1 server crash from a MaxBytesReader header race
(CVE-2026-97054). Every Go binary in the image is rebuilt with them: podman, fzf, ipp-usb and
nvidia-container-toolkit. Buildroot does not rebuild Go packages when the host Go changes, so the
toolchain and every Go package were cleaned first. Core is not in this release: no Go packages, no
COSMIC, image unchanged since 26.11.14.
The other change is about seeing the problem in the first place. The SBOM (pengyos-sbom 0.2.0) now lists the Rust crates and Go modules each package compiles in, read from the lockfiles cargo and Go actually built from: about 6,500 entries on a Desktop image, across COSMIC, Pengy, podman, uv and 18 more packages. Each of those packages used to be one line in the SBOM, and nothing scanned what was inside it. The nightly (pengyos-nightly 0.17.0) checks every entry against osv.dev (RustSec, the Go vulnerability database, GHSA) and reports new critical and high advisories. The first run found 14 critical and 57 high on Desktop. 24 packages that had no CPE identifier got one, 13 PengyOS recipes (flatpak, xdg-desktop-portal, uutils coreutils, uv, nvidia-container-toolkit) and 11 stock packages (nftables, libva, mosh, intel-microcode). Without a CPE, pkg-stats cannot match a CVE to the package. None of the 24 has an open CVE today: uutils alone has 44 in NVD, all fixed before the version shipped.
Two release-process defects are fixed in the same window. A failed CVE scan had marked every tracked
CVE as resolved; pengyos-nightly 0.16.1 makes a failed scan resolve nothing and say so in the subject.
And the GitHub gate had been red since 10-28 without anyone noticing: a renamed Buildroot fixture, a
test matching a script line that had grown, and a runner without user namespaces, PipeWire headers or
CPU for the fan simulator. All six suites pass now, 173/173, and the same gate runs in the nightly and
before every release.sh --publish, which refuses to build while it is red.