WolfStack v25.21.3
v25.21.3: a bare cluster secret can no longer run commands, open consoles or touch files through any endpoint
25.9.3 fixed GHSA-r3mw-2wmq-j6jg on five endpoints by name; the same
capability was still reachable through /api/wolfflow/exec and ~40 other
exec/console/file handlers with nothing but a valid cluster secret. Every
shell-class handler now takes the operator gate, legitimate forwarding
callers stamp attribution, and the AI action filter catches curl x | bash.
Reported by @baeseungwon1010.
Co-Authored-By: CodeWolf paul@wolf.uk.com
Co-Authored-By: Wolf Software Systems Ltd paul@wolf.uk.com
Claude-Session: https://claude.ai/code/session_01Y3XvLuAXChuooji253ujcy
Verifying this release
Each binary is signed via cosign keyless OIDC (no key distribution — signing identity is the GitHub Actions workflow itself, anchored to the Sigstore Fulcio CA and the Rekor transparency log) and ships with a SLSA build provenance attestation.
Verify the cosign signature:
cosign verify-blob \
--bundle wolfstack-x86_64.cosign.bundle \
--certificate-identity-regexp 'https://github.com/wolfsoftwaresystemsltd/WolfStack/\.github/workflows/release\.yml@.*' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
wolfstack-x86_64
Verify the build provenance:
gh attestation verify wolfstack-x86_64 --repo wolfsoftwaresystemsltd/WolfStack
Verify the SHA-256 checksum:
sha256sum -c SHA256SUMS
Artifacts
wolfstack-x86_64/wolfstack-aarch64/wolfstack-armv7— static musl binaries (Linux x86_64, ARM64 / Raspberry Pi 4+, and 32-bit ARM).wolfstack-<arch>.cosign.bundle— cosign signature bundle (cert + signature + Rekor entry).SHA256SUMS— checksums for both binaries.
For per-version history see CHANGELOG.md.