# AIStor Memory (aimem) RELEASE.2026-11-08T05-19-47Z Released: 2026-11-08 This AIStor Memory (aimem) release rebuilds both container images on a patched brotli library, fixing a critical vulnerability (CVE-2026-111497). It also stops an older annotation from overwriting a newer one, and corrects the agent skill's guidance on when a write is durable. --- ## Downloads ### Binaries | Platform | Architecture | Download | | -------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------- | | Linux | amd64 | [aimem.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem.RELEASE.2026-11-08T05-19-47Z) | | Linux | arm64 | [aimem.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem.RELEASE.2026-11-08T05-19-47Z) | The setuid `aimem-fusermount` mount helper, the `aimem-bio` binary that `aimem bio` runs, and the Kubernetes CSI node driver are published beside it: | Binary | Architecture | Download | | ------------------ | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | `aimem-fusermount` | amd64 | [aimem-fusermount.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-fusermount.RELEASE.2026-11-08T05-19-47Z) | | `aimem-fusermount` | arm64 | [aimem-fusermount.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-fusermount.RELEASE.2026-11-08T05-19-47Z) | | `aimem-bio` | amd64 | [aimem-bio.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-bio.RELEASE.2026-11-08T05-19-47Z) | | `aimem-bio` | arm64 | [aimem-bio.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-bio.RELEASE.2026-11-08T05-19-47Z) | | `aimem-csi-driver` | amd64 | [aimem-csi-driver.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-csi-driver.RELEASE.2026-11-08T05-19-47Z) | | `aimem-csi-driver` | arm64 | [aimem-csi-driver.RELEASE.2026-11-08T05-19-47Z](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-csi-driver.RELEASE.2026-11-08T05-19-47Z) | Each binary has `.sha256sum`, `.minisig`, and `.asc` files at the same path. These links point into `archive/`, where a release's files stay after a newer release ships, so they always serve this build. The unversioned `…/linux-{arch}/aimem` path serves whatever release is newest. ### Packages `.deb`, `.rpm`, and `.apk` install the `aimem` client, the setuid `aimem-fusermount` mount helper (`/usr/bin/aimem-fusermount`, mode 4755), and `aimem-bio`. They also install a disabled example `mnt-aimem.mount` systemd unit and the `/sbin/mount.aimem` helper it needs. | Format | Architecture | Download | | ------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | | DEB | amd64 | [aimem_20261108051947.0.0_amd64.deb](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem_20261108051947.0.0_amd64.deb) | | DEB | arm64 | [aimem_20261108051947.0.0_arm64.deb](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem_20261108051947.0.0_arm64.deb) | | RPM | amd64 | [aimem-20261108051947.0.0-1.x86_64.rpm](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem-20261108051947.0.0-1.x86_64.rpm) | | RPM | arm64 | [aimem-20261108051947.0.0-1.aarch64.rpm](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem-20261108051947.0.0-1.aarch64.rpm) | | APK | amd64 | [aimem_20261108051947.0.0_x86_64.apk](https://dl.min.io/aistor/aimem/release/linux-amd64/archive/aimem_20261108051947.0.0_x86_64.apk) | | APK | arm64 | [aimem_20261108051947.0.0_aarch64.apk](https://dl.min.io/aistor/aimem/release/linux-arm64/archive/aimem_20261108051947.0.0_aarch64.apk) | The packages depend only on libc (`libc-bin` / `glibc-common`); no `libfuse` is needed. ### Container Images ```bash # The aimem client, pinned to this release: docker pull quay.io/minio/aistor/aimem:RELEASE.2026-11-08T05-19-47Z # The Kubernetes CSI node driver, pinned to this release: docker pull quay.io/minio/aistor/aimem-csi-driver:RELEASE.2026-11-08T05-19-47Z ``` The `latest` tag of each image also points at this release, but moves when the next one ships. To verify a build, pin the release tag or a `@sha256:` digest, never `latest`. Mounting from a container needs `/dev/fuse`. As root, it also needs `CAP_SYS_ADMIN` (or `--privileged`). As a non-root user, the container needs `SYS_ADMIN` added to its capabilities and `allowPrivilegeEscalation: true`, so the setuid helper can run. ### Verification Each binary is signed with minisign (preferred) and GPG, and has a sha256sum file. ```bash BASE=https://dl.min.io/aistor/aimem/release/linux-amd64/archive curl -fsSLO $BASE/aimem.RELEASE.2026-11-08T05-19-47Z curl -fsSLO $BASE/aimem.RELEASE.2026-11-08T05-19-47Z.minisig curl -fsSLO $BASE/aimem.RELEASE.2026-11-08T05-19-47Z.sha256sum # minisign minisign -Vm aimem.RELEASE.2026-11-08T05-19-47Z \ -P RWTx5Zr1tiHQLwG9keckT0c45M3AGeHD6IvimQHpyRywVWGbP1aVSGav # sha256: the checksum file names the versioned binary, so keep that file name sha256sum -c aimem.RELEASE.2026-11-08T05-19-47Z.sha256sum ``` The minisign public key above is the MinIO release-signing key, used across the AIStor product line. --- ## Changes since RELEASE.2026-11-04T23-12-53Z ### Bug Fixes #### Annotations (tech preview) - When two programs saved the same annotation note one after the other, the first program's close could upload its older text again and replace the newer note. A note now holds the text that was saved last. (#291) #### Agent skill and workspace preamble - The aimem skill told agents that `fsync()` makes a write durable. For ordinary files it does not: a write reaches the bucket only when `close()` returns. Agents that relied on `fsync` as a checkpoint could lose work when the sandbox ended. The skill and the preamble on `CLAUDE.md` / `AGENTS.md` now say so, and tell agents to open, write and close a file in one process. (#289) - The skill also corrects other claims: `rename()` needs the server's `RenameObject` and has no copy-then-delete fallback, empty directories survive a remount, and two writers on one mount share the file while writers on separate mounts overwrite each other. (#289) ### Security Updates - Both container images (`aimem` and `aimem-csi-driver`) now ship brotli 1.2.1, fixing [CVE-2026-111497](https://www.cve.org/CVERecord?id=CVE-2026-111497) (critical), an out-of-bounds write in the brotli decoder. Earlier images, including RELEASE.2026-11-04T23-12-53Z, carried brotli 1.2.0: the image build did not pick up Wolfi package fixes released after the pinned base image. Release images now take those fixes at build time. Only the container images are affected; the binaries and the deb/rpm/apk packages do not contain this library. (#286) ### Platform / Compatibility - Linux amd64 and arm64, glibc 2.34 or later. - Mounting needs `/dev/fuse`. As root, or with `CAP_SYS_ADMIN`, aimem mounts directly; any other user mounts through the setuid `aimem-fusermount` helper. FUSE passthrough also needs `CAP_SYS_ADMIN`; without it, a mount serves ordinary FUSE reads. --- ## Security & Compliance Software bills of materials (SBOMs) for this release, generated from the `Cargo.lock` files at the release tag. | Component | SPDX | CycloneDX | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | `aimem` | [aimem-RELEASE.2026-11-08T05-19-47Z.spdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-11-08T05-19-47Z.spdx.json) | [aimem-RELEASE.2026-11-08T05-19-47Z.cdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-11-08T05-19-47Z.cdx.json) | | `aimem-bio` | [aimem-bio-RELEASE.2026-11-08T05-19-47Z.spdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-bio-RELEASE.2026-11-08T05-19-47Z.spdx.json) | [aimem-bio-RELEASE.2026-11-08T05-19-47Z.cdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-bio-RELEASE.2026-11-08T05-19-47Z.cdx.json) | | `aimem-csi-driver` | [aimem-csi-RELEASE.2026-11-08T05-19-47Z.spdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-csi-RELEASE.2026-11-08T05-19-47Z.spdx.json) | [aimem-csi-RELEASE.2026-11-08T05-19-47Z.cdx.json](https://dl.min.io/aistor/aimem/release/notes/aimem-csi-RELEASE.2026-11-08T05-19-47Z.cdx.json) | For `aimem`, also the [crate list](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-11-08T05-19-47Z.crates.txt) and [dependency tree](https://dl.min.io/aistor/aimem/release/notes/aimem-RELEASE.2026-11-08T05-19-47Z.cargo-tree.txt). --- ## Upgrade Instructions - **Container images:** pull `quay.io/minio/aistor/aimem:RELEASE.2026-11-08T05-19-47Z` and `quay.io/minio/aistor/aimem-csi-driver:RELEASE.2026-11-08T05-19-47Z`. If your scanner flagged CVE-2026-111497 in an earlier image, this release clears it. - **Kubernetes:** pin both image references in the DaemonSet to `quay.io/minio/aistor/aimem-csi-driver:RELEASE.2026-11-08T05-19-47Z`. Mounts survive a driver upgrade, so a running mounter pod keeps its earlier image, and the vulnerable brotli, until the workload pod that uses the volume is deleted and recreated. - **Agent skill on long-lived hosts:** each mount installs the skill into `~/.claude/skills/aimem/` and `~/.agents/skills/aimem/` only when no `SKILL.md` is there yet, so an earlier copy is never replaced. To get the corrected guidance on a host that kept an earlier install, remove those two directories before the next mount. Fresh sandboxes need no action. The preamble on `CLAUDE.md` / `AGENTS.md` updates on its own. - **Upgrading from a release before RELEASE.2026-10-30T18-15-12Z:** read the [RELEASE.2026-10-30T18-15-12Z notes](https://dl.min.io/aistor/aimem/release/notes/release-notes-RELEASE.2026-10-30T18-15-12Z.md) first. They reserve six bucket names for the new top-level commands and make `aimem delete` ask for confirmation. ## Documentation - Hosted docs: ## Support - Security disclosures: security@min.io - Licensed customers and contributors: contact MinIO support.